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

["Paul Leach" <paulle@Exchange.Microsoft.com>]

Here's my take.

The draft-locate-05 says how to find a server that store a given DN when
the DN conforms to the rules in RFC 2247.
An example of such a DN:
	cn=John Doe,ou=accounting,dc=example,dc=net

Certain other people want a way to find a server that stores a DN when
the DN does not conform to 2247, but to some looser set of rules. An
example of such a DN might be
	cn=John Doe,ou=accounting,dc=example,dc=net,o=example
corporation,c=us

As written, draft-locate-05 says NOTHING about such DNs. It simply does
not apply, because they do not conform to 2247. There is therefore
nothing that stops such people from writing a draft that says how to
find a server that stores such DNs, without in any way conflicting with
draft-locate-05.

Whereas, if we change draft-locate-05 to incorporate rules for such DNs,
we also have to get 2247 changed.

They should therefore write such a draft. Their draft should be easy --
it can say how certain DNs that do not conform to 2247 can be morphed
into ones that do (by moving all the "dc=" components to the right side,
keeping the ordering), and then applying the rules in draft-locate-05.

Paul