Re: Incomplete Syntaxes Referenced by RFC 2252

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

At 05:55 PM 2/22/01 -0600, Mark Wahl wrote:
>Steven Legg wrote:
>             OID: 1.3.6.1.4.1.1466.115.121.1.54
>>   RFC 2252 NAME: LDAP Syntax Description
>> STRING ENCODING: Section 4.3.3, RFC 2252
>>      ASN.1 TYPE: None
>>     CONFORMANCE: (implied MUST, ldapSyntaxes is a MUST?)
>> 
>> To legitimize the use of objectIdentifierFirstComponentMatch as the equality
>> matching rule for the ldapSyntaxes attribute I suggest this ASN.1 in the
>> successor to RFC 2252 (plus the commented out things while we're about it
>> ?):
>
>As a new feature?  I don't think there are two independent implementations of
>RFC 2252's LDAP Syntax Description which have an OBSOLETE field.

Also, LDAPsyntax don't have NAMEs.

Kurt