The ability for the mapping process to be bidirectional is important as it
allows 2247 to indicate exactly where an object that is DNS-named is
located in the directory. If one were to introduce the ability for the DNs
to have additional components, there is no field currently defined in DNS
for encoding the set of AVAs that would be needed to complete this mapping.
There would be local tables, which seems to violate the spirit of DNS.
> > Distinguished names in which there are one or more RDNs, all
> > containing only the attribute type DC, can be mapped back into domain
> > names. Note that this document does not define a domain name
> > equivalence for any other distinguished names.
>
> My understanding of this sentence is that it says a DN which has only DC
> attributes can be mapped into a host name. It doesn't say that an RDN
that
> contains a DC attribute as well as another attribute cannot be mapped into
> a domain name.
It can't be done by RFC 2247. Another RFC perhaps, but that other RFC would
need to show how the other AVAs are represented in DNS.
Mark Wahl, Directory Architect, Service Provider/Infrastructure
Sun Microsystems, Inc. iPlanet Alliance