Re: DN->DNS mapping in draft-ietf-ldapext-locate-05.txt

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

Just thought of another issue....  dc has uses outside of
the naming of the context prefix.  I believe some applications
create 'domain' and others (using dc names) entries under an
ou to manage DNS RR.  In particular, in service provider
environments where a provider using dc=example,dc=com as their
naming context, might have a container
  ou=domains,ou=consumer,ou=customers,dc=example,dc=com
and desiring to add entries under this:
  dc=consumer,dc=com,ou=domains,ou=consumer,ou=customers,dc=example,dc=com
to manage the DNS RR for that consumer.  The existing DN to
domain mapping would produce "example.com", the new mapping
would produce "consumer.com.example.com".

Defining a "loose" DN to domain mapping might limit other uses
of 'dc'.  It might be appropriate for those who are engaged in
service provider forums could look into whether the mapping
change would have a significant impact upon their current use
of 'dc'.

Kurt