RE: numericString syntax ...

["Salter, Thomas A" <Thomas.Salter@unisys.com>]

... and the numeric string matching rule from X.520 says to ignore all the
spaces and compare the digits.

 > -----Original Message-----
 > From: Kurt D. Zeilenga [mailto:Kurt@OpenLDAP.org]
 > Sent: Wednesday, December 20, 2000 6:22 PM
 > To: sanjay.jain@openwave.com
 > Cc: ldapext
 > Subject: Re: numericString syntax ...
 > 
 > 
 > At 02:39 PM 12/20/00 -0800, Kurt D. Zeilenga wrote:
 > >At 01:41 PM 12/20/00 -0800, sanjay jain wrote:
 > >>A quick question: 
 > >>
 > >>What is the character set for numericString syntax strings ? 
 > >
 > >numericString is identical in syntax to a directoryString.
 > 
 > Upon reflection, this statement is incorrect.  numericString
 > is a ASN.1 string type...
 > 
 > >In X.500, this implies the character set is restricted by
 > >a choice of printableString (subset of IA5), teletexString
 > >(T.61), or universalString (UCS-2).
 > 
 > and hence likely has significant restrictions upon allowed
 > characters.  "ASN.1 Complete" says 0-9 and space and when
 > encoded using BER are represented using the corresponding
 > ASCII characters.
 > 
 > >>Particularly, I am interested in knowing if '+'/'-' chars are 
 > >>allowed. 
 > 
 > Per "ASN.1 Complete", no.
 > 
 > 
 > >Numeric string matching is just like that of case ignore matching
 > >with all spaces being ignored.
 > 
 > This statement, however, appears to be correct given the
 > syntax restricts.
 > 
 > >As noted in LDAPbis WG
 > >discussions, more specific references to X.500 specifications
 > >are needed.
 > 
 > This is an example of why more specific references are needed.
 > 
 > Now it's to go look at my numeric string syntax validation
 > function... :-)
 > 
 > Kurt
 > 
 >