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

Re: Protocol Information Syntax



I believe that Steven's reason for bringing up this issue is that fixing
up this incompleteness in 2252's successor would require adding the
Protocol Information syntax that does not appear in 2252, and we have set
in this WG a policy of not adding new items to our core documents.  If we
remove these items from the ldapbis documents, and your clients need these
them specified in an RFC, a separate RFC can be written to do this.
This is our approach with the X.509-related elements.

 - RL "Bob"

On Mon, 9 Dec 2002, Kathy Dally wrote:

> Hi All!
>
> Although the protocolInformation attribute is not used in any of the
> object classes in RFC 2256 or X.521, it is used in the MHS standards.
> My client uses the MHS object classes.  Also, they are used by NATO.
> These directories use LDAP and need the support of the RFCs for their
> requirements.  So, I would not like to see the attribute, matching rule,
> and syntax removed.
>
> Thanks,
> Kathy Dally
>
>
>
> Steven Legg wrote:
> >
> > RFC 2252 defines a protocolInformationMatch matching rule that
> > references an undefined Protocol Information syntax. RFC 2256
> > defines a protocolInformation attribute that uses
> > protocolInformationMatch. Nothing else seems to depend on
> > protocolInformation so I propose removing all mention of
> > the syntax and matching rule from the syntaxes I-D, and for
> > Kathy to remove the attribute from the user schema I-D.
> >
> > Any objections ?
> >
> > Regards,
> > Steven
>
>