- possible abandonment of both X.500 names and ASN.1 encoding.
...
A design that might emerge from these simplifications is:
o I become "crocker(_at_)tis(_dot_)com", you are "jlowry(_at_)bbn(_dot_)com",
I completely support the proposed "Internet Friendly Naming Scheme".
Though it might be nice to replace X.500/ASN.1 that would seem to
create compatibility problems. Perhaps it is not necessary. There
is an experimental RFC for representing such an Internet Friendly Name
in X.500. There are possible problems with that RFC which have been
discussed on the OSI-DS mailing list. The following uses a slight
modification of the RFC.
We can represent "crocker(_at_)tis(_dot_)com" as
@Organization=Internet(_at_)DomainName=com@DomainName=tis(_at_)CommonName=crocker
I am not suggesting that the users need ever see this or any variant.
They will see "crocker(_at_)tis(_dot_)com". I am just suggesting that we can
use the existing X.500/ASN.1 encoding design and avoid creating an
unnecessarily incompatible change.
Bob Smart
Robert(_dot_)Smart(_at_)mel(_dot_)dit(_dot_)csiro(_dot_)au
Distributed Systems Program
CSIRO Division of Information Technology phone: +61 3 282 2625
723 Swanston St, Carlton VIC 3053, Australia fax: +61 3 282 2600