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

Re: DN formatting

To: Christopher Oliva <Chris.Oliva@entrust.com>
Subject: Re: DN formatting
From: Scott Seligman <Scott.Seligman@Eng.Sun.COM>
Date: Thu, 22 Apr 1999 13:18:54 -0700
Cc: 'LDAP EXT' <ietf-ldapext@netscape.com>
In-reply-to: "Your message of Thu, 22 Apr 1999 13:42:45 EDT." <01E1D01C12D7D211AFC70090273D20B107305C@sothmxs06>
Resent-date: Thu, 22 Apr 1999 13:19:25 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"oFMPl.0.dp4.9Hu7t"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

>From what I understand the [hexstring] form of attribute value is only 
>allowed if the corresponding attribute type name is of the dotted decimal
>form.

RFC 2253 says:
   If the AttributeValue is of a type which does not have a string
   representation defined for it, then it is simply encoded as an
   octothorpe character ('#' ASCII 35) followed by ...

It also says that if the type is of the dotted-decimal form then the
hexstring value form should be used, but it does not add "and vice-versa".


>should the application always assume that a leading "#" character always
>designates a hexstring escaped BER encoding?

Yes.  The RFC seems unambiguous regarding leading "#" characters.  As you
note, the RFC is self-contradictory on the question of non-leading "#"
characters.


Scott Seligman
Java Software Engineering
Sun Microsystems

References:
- DN formatting
  - From: Christopher Oliva <Chris.Oliva@entrust.com>

Prev by Date: new internet-drafts
Next by Date: Re: Display name attribute
Index(es):
- Chronological
- Thread