[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: draft-ietf-ldapext-locate-04.txt

At 03:34 PM 9/2/2000 -0700, Kurt D. Zeilenga wrote:
At 02:36 PM 9/2/00 -0700, Bruce Greenblatt wrote:
>I have a question on Mapping Algorithm in Section 3. The second paragraph of this section has this sentence:
>
>"An RDN is able to be converted if it (1) consists of a single AttributeTypeAndValue".

This is consistent with the last paragraph of Section 2 and RFC 2247.
The locate I-D should be (and I believe is) consistent with these
statements in RFC 2247.

   [...]
   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.

Note that these statements outline a 1-to-1 relationship between
a domain and a DN of DC-only RDNs.  I believe it important to
preserve this 1-to-1 relationship between domains and DC-based DNs.

OK. I'll go with that. How does allowing for an RDN that has DC attribute as well as something else not preserve this relationship... I think that the draft is just a little restrictive in this respect for no particular gain.

Bruce

Kurt

==============================================
Bruce Greenblatt, Ph. D.
Directory Tools and Application Services, Inc.
http://www.directory-applications.com
See my new Book on Internet Directories: http://www.phptr.com/ptrbooks/ptr_0139744525.html