On Wed, 26 Jul 1995, Bill Sommerfeld wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Of course, if you have a (preexisting) "ns.mit.edu" domain and an "ns"
"map" in the mit.edu domain, things look just as messy as in the
lcs(_at_)mit(_dot_)edu vs lcs.mit.edu case.
Perhaps the magic cookie should be chosen in a way that it excludes
any chance of conflicting with existing names.
warlord(_dot_)cert(_dot_)(_at_)(_dot_)mit(_dot_)edu
(OK, "@" has special meaning in DNS bootload files, but I'm sure
there's *some* special character out there which could be used. Even
`-' might do the trick).
hyphen occurs in lots of domain names. (In fact, I think that when DNS
decreed that upper and lower case letters were the same, it should have
delcared that hyphen (-) and underscore (_) were the the same.) Modulo
whatever quirks the various version of BIND may have, DNS uses counted
strings and has a defined escape (backslash followed by up to three
decimal digits) such that all possible byte values can be expressed.
quite possibly most implementations would choke on
\255\1\(_dot_)\(_at_)(_dot_)mit(_dot_)edu
for example (a label consisting of an all ones byte, a control-A,
a period and an at-sign, .mit.edu) but it is expressable.
That's why you just plain need a separate flag to say whether a name is
a user or a host, i.e., whether the first label is an account name.
- Bill
-----BEGIN PGP SIGNATURE-----
Version: 2.6.1
iQCVAwUBMBYwnrT+rHlVUGpxAQGBIAP/S8p3E272iW8uEVeh+TRdmQtk/dNNNdYU
FdI/v1UmxmaEtNXV7mmJf6ZCL3o6dlPN8QifvjmNqjErAvFqdaNiMNTKYNEip5V4
9fgVSDwXqzpBcQIY5kwejVZsh1VEPRQF+RhMhOaToSyD6MP3lRmSXvbSAnY2mWCy
JWXVNcHiX74=
=oObS
-----END PGP SIGNATURE-----
Donald
=====================================================================
Donald E. Eastlake 3rd +1 508-287-4877(tel) dee(_at_)cybercash(_dot_)com
318 Acton Street +1 508-371-7148(fax)
dee(_at_)world(_dot_)std(_dot_)com
Carlisle, MA 01741 USA +1 703-620-4200(main office, Reston, VA)