3/26 UNLINK news: RFP going out this week for uclink replacement, aiming
at clustered solution--implementation of new service, probably to be
run by a different group, is planned for this summer.
\_ Might we finally get a decent email hostname? <DEAD>cal.edu<DEAD> or <DEAD>ucb.edu<DEAD>.
C'mon, everybody, pray with me.
\_ what's wrong with <DEAD>uclink.berkeley.edu<DEAD>?
\_ if you have to ask...
\_ There is zero chance we'll change our primary domain name.
However, it is reasonably likely that we'll have top-level
"@Berkeley.EDU" names instead of "@uclink.berkeley.edu"
names. "Berkeley" is a name with international recognition,
unlike "cal" or "ucb". -tom
\_ Ah callous youth... No respect for the past and ucbvax.
\_ there's no reason we can't have an MX alias point to
http://berkeley.edu. I agree with the name recognition thing,
and that's important, but I'm sick of spelling "berkeley"
for people and writing out a long address on forms.
<DEAD>Cal.edu<DEAD> would work well in those cases, just like http://csua.org
does (or did) for http.
\_ I hadn't realized this was available as a mail
redirect. Are we assured that http://csua.org will last as
long as the csua exists? Is http://csua.org owned by the
actual csua, and the translation occuring locally?
(e.g. not being intercepted and forwarded by another
machine?)
\_ having 2 ways of addressing the <DEAD>.berkeley.edu<DEAD>
domain would be stupid and lame. people who can't
spell Berkeley aren't worth your time.
\_ it makes a lot more sense than <DEAD>uclink.berkeley.edu<DEAD>,
but if we ditched the uclink part I wouldn't mind
so much.
\_ Ah callow youth... No respect for the past and ucbvax.
\_ you probably mean "callow".
\_ is there ever a non-callow youth?
\_ maybe not, but the other guy still fucked up the
reference.
\_ There. Fixed. Happy? |