Tony Finch - CRSIDs and email addresses

From:	erikofviking
Date:	2009-06-02 21:41 (UTC)

(Link)

All good points. The embarrassing situation of sensitive financial information landing in an undergrad mailbox rather than with the director of finance happened up here in the North earlier in the year.

We took the potentially controversial decision to delete it directly out of the users mailbox in the end. Not something that I was overly happy at having to do.

(Reply) (Thread)

From:	Dave Holland [org.uk]
Date:	2009-06-03 09:45 (UTC)

(Link)

Interesting read, thanks. You could mention the lessons learned from the period around 1993 when long CRSIDs of the form djh1008 were issued, and the problems with people misreading 1 as l, 0 as o, etc. Presumably the 1/l problem will become more widespread when enough people have CRSIDs that abc10, abc11 etc become common - or has that point already been reached?

(Reply) (Thread)

From:	fanf
Date:	2009-06-03 11:23 (UTC)

(Link)

I made a deliberate decision not to discuss past CRSID policies in any detail, to keep the document short and focussed. I also omit things like group IDs, and advantages of CRSIDs that aren't relevant to @cam email addresses (e.g. CRSIDs are unique enough that they are often usable on public non-University services).

The current policy, in force since September 1994, is:

Personal CRSIDs are between 5 and 7 characters starting with the initials of the person (as known at the time of registration) and using at least two alphabetic characters and terminating with at least one digit.
The first digit must be >1 (this is to avoid confusion between 1 and I and 0 and O)
For those with more than 6 inititals, we chop the initials of the forenames after the fifth.
People with only one name have the initial of that name doubled.
In the case of hyphanated forenames, both are used to build the CRSid.
Single initial CRSids are used to denote courses.
Group resources are alphabetic only.

(Reply) (Parent) (Thread)

From:	fanf
Date:	2009-06-03 15:20 (UTC)

(Link)

Agreed.

The aim of the document is to discourage foolish people from advocating the use of friendly name addresses in the @cam domain. I guess a lot of the pressure for this could be relieved by supporting friendly name addresses @admin, so we're deliberately emphasizing that the current policy is not against friendly name addresses and in fact actively supports them, for example in the way the managed mail domain interface works.

I avoided a discussion of large departmental domains to keep the document short. It's a bit of a can of worms. There are questions of what categories of people you give email addresses to and what effect that has on the rate you chew through the namespace. In particular, if (like Chemistry) you exclude students, Engineering is less than a third the size of the UAS.

I expect admin will find out that they are large enough that they have significant problems with name clashes. In the past the CS would have tried to lead them away from that kind of trouble, but nowadays it's probably better to avoid seeming too obstructive.

One area in which the instigators of this make-work do not seem interested is to improve the way we use domain names. For example, if we allow large departments to have divisional subdomains (like Physics) then friendly name addresses become more feasible - though of course it has the downside of exposing more organizational complexity.

So yes, that's the kind of nuance and hedging I wanted to avoid in favour of simplified and direct language, so that non-technical senior managers can get a better idea of the considerations behind the status quo, and hopefully they'll think about more than just the surface appearance of email addresses.

(Reply) (Parent) (Thread)

Tony Finch - CRSIDs and email addresses

CRSIDs and email addresses

What does CRSID stand for.

Re: What does CRSID stand for.