RE: Last Call: LDAP & X.500 Component Matching Rules to Proposed Standard

["Steven Legg" <steven.legg@adacel.com.au>]

Folks of the IESG,

Now that the last call period for draft-legg-ldapext-component-matching
has expired I've updated and resubmitted the draft in light of the
comments received. There were enough fiddly editorial changes to make
a revision advisable. Here are the changes in
draft-legg-ldapext-component-matching-11.txt:

  - changed UTF8 to UTF-8 throughout,

  - expanded the acronyms ASN.1 BER, LDAP, ABNF, DER on first use,

  - changed my mind on the referencing style and made all the references
    consistent, e.g.

      ... Clause 11.3 of [8] ...  -->  Clause 11.3 of X.680 [8]

  - added an IANA Considerations section,

  - added an IPR section,

  - replaced the references to the 1997 version of ASN.1 with
    references to the 2002 version,

  - removed OPTIONAL from the list of RFC 2119 keywords; it clashes
    with the ASN.1 keyword,

  - downgraded some MAYs to "may" because they did not state an
implementation
    imperative.

Regards,
Steven


> -----Original Message-----
> From: owner-ietf-announce@ietf.org
> [mailto:owner-ietf-announce@ietf.org]On Behalf Of The IESG
> Sent: Thursday, 8 May 2003 5:09
> To: IETF-Announce: ;
> Subject: Last Call: LDAP & X.500 Component Matching Rules to Proposed
> Standard
>
>
>
> The IESG has received a request to consider LDAP & X.500 Component
> Matching Rules <draft-legg-ldapext-component-matching-10.txt> as a
> Proposed Standard.  This has been reviewed in the IETF but is not the
> product of an IETF Working Group.
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-7.
>
> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-legg-ldapext-compone
> nt-matching-10.txt
>
>
>
>
>