symmetry (Was: LDAPDN problems, and changes since RFC 2253)

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

At 03:50 AM 7/23/2004, Hallvard B Furuseth wrote:
>Some of this may have been discussed before, if so feel free to declare
>the matter closed.

Most of these issues have been previously discussed.
However, there are a few points which are new.

>>    - Revised specification (in Section 2) to allow short names of any
>>      registered attribute type to appear in string representations of
>>      DNs instead of being restricted to a "published table".  Remove
>>      "as an example" language.  Added statement (in Section 3) allowing
>>      recognition of additional names but require recognization of those
>>      names in the published table.  The table is now published in
>>      Section 3.
>
>The result is that implementations need not recognize all string
>representations that they produce: They are to produce short names if
>the attribute type is in the registry (section 2.3), but need only
>recognize the short names in the table in section 3.

Technically, yes.  If a DN string encoder implementation uses
other names, then it cannot expect those DN strings to recognized
elsewhere, including by the DN string decoder(s) present in the same
client/server software (especially true if the encoders and decoders
are independently developed).  There is no symmetry requirement as
an client/server is free to use independently developed encoders
and decoders.

Kurt