RE: protocol: placement of initial/final substrings

["Ramsay, Ron" <Ron.Ramsay@ca.com>]

And yet it is a SEQUENCE and so some order is implied?

-----Original Message-----
From: owner-ietf-ldapbis@OpenLDAP.org
[mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of Steven Legg
Sent: Friday, 19 December 2003 10:28
To: Jim Sermersheim; h.b.furuseth@usit.uio.no
Cc: ietf-ldapbis@OpenLDAP.org
Subject: Re: protocol: placement of initial/final substrings



The matching rules in [Syntaxes] are associated with the SubstringAssertion
ASN.1 type. The fact that the <initial> substring must come first and the
<final> substring must come last is inherent in the ABNF for the LDAP-specific
encoding of the SubstringAssertion ASN.1 type. The ABNF does not tag which
substring is <initial> and which is <final>, so the order of the substrings
has to be taken as significant.

SubstringFilter in [Protocol] is a different ASN.1 type and values of
this ASN.1 type are always encoded in BER in the protocol. The BER encoding
distinguishes the initial, any and final components with different context
specific tags, so the order doesn't matter, and no order is imposed.

Regards,
Steven

Jim Sermersheim wrote:
> I've never heard of this being a constraint in the protocol.
>  
> Jim
> 
>  >>> Hallvard B Furuseth <h.b.furuseth@usit.uio.no> 12/11/03 5:21:58 AM >>>
> Must the <initial> and <final> components be the first and last
> substrings in a SubstringFilter? I can find no general statement which
> says so, though the individual matching rules in [Syntaxes] all require
> such placement.
> 
> -- 
> Hallvard