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

Re: Attribute names not Internationalized ?

To: ietf-ldapext@netscape.com, sanjay.jain@software.com
Subject: Re: Attribute names not Internationalized ?
From: Jim Sermersheim <JIMSE@novell.com>
Date: Thu, 07 Oct 1999 12:20:22 -0600
Content-disposition: inline
Resent-date: Thu, 07 Oct 1999 11:20:46 -0700 (PDT)
Resent-from: ietf-ldapext@netscape.com
Resent-message-id: <"zsgmB.A.c0E.xRO_3"@glacier>
Resent-sender: ietf-ldapext-request@netscape.com

When I looked into this I decided it was becasue of an X.409 restriction on the allowable characters in names. It said something about only ascii digits and letters, and a dash.  I also remember It went further to say the dash could not end a name, nor could there be two dashes together (-- is an ASN.1 comment).  So LDAP servers which front-end X.500 directories could concievebly run into problems if the restriction on allowable characters was relaxed.  I'm not sure that's the real reason, and I don't have a copy of x.409 handy to verify these memories.

Jim

>>> sanjay jain <sanjay.jain@software.com> 10/7/99 11:42:54 AM >>>

attribute names have not been internationalized. 
Does anybody know what's the reason ? 

thanks 
sanjay

Prev by Date: Attribute names not Internationalized ?
Next by Date: draft-ietf-ldapext-ldap=java-api-07 - LDAPAttribute.removeValue
Index(es):
- Chronological
- Thread