Re: rfc 1778
Tim Howes (howes@netscape.com)
Tue, 14 May 1996 15:19:30 -0700
Oliva, Chris: GTIS wrote:
>
> Hi,
>
> I'd like to request that rfc1778 be updated to describe how t.61 characters
> (extended 8-bit) are handled in ldap. It's currently not documented and a
> source of much confusion to many people. Everybody who first reads the
> rfc's gets the impression that 8-bit characters are not supported in ldap.
>
> 1) rfc1777 states:
>
> LDAPString is a notational convenience to indicate that, although strings
> of LDAPString type encode as OCTET STRING types, the legal character
> set in such strings is limited to the IA5 character set.
>
> LDAPDN ::= LDAPString
>
> 2) rfc1779 sort of says that a hex escape mechanism can be used to represent
> any valid Distinguished name, but is not very specific about how. Not
> until you
> fire up the ldap server with debugging on is it clear as to what's
> happening.
>
> 3) rfc1778 states:
>
> T61 String - The encoding of a string of type t61StringSyntax is the string
> value
> itself.
>
> That hardly does the job if you ask me.
Chris, you should send your comments to the ietf-asid@umich.edu list.
Discussion is happening there right now on the design of the next
version of LDAP, LDAPv3. The ldap@umich.edu list is really just for
the U-M LDAP implementation. -- Tim