[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: ldapbis WG Last Call on ldapbis-syntaxes, ldapbis-strprep
> Some minor edits to draft-ietf-ldapbis-06.txt required:
That should be draft-ietf-ldapbis-syntaxes-06.txt (doh!).
Also, one more correction:
4) [ROADMAP] isn't provided in the references. It is
[ROADMAP] Zeilenga, K., "LDAP: Technical Specification Road Map",
draft-ietf-ldapbis-roadmap-xx.txt, a work in progress, March 2003.
Regards,
Steven
>
> 1) The title of RFC 3383 is incorrect in the references,
>
> 2) Section 5.2.16 omits the sentence (thanks to Hallvard for
> picking it up),
>
> "The LDAP definition for the numericStringSubstringsMatch matching
> rule is:"
>
> 3) The telephoneNumberMatch and telephoneNumberSubstringsMatch need to
> be added to the list in the first sentence of section 5.2.
> The comment
> on telephoneNumberMatch in Appendix B, case 25 needs to be
> struck out.
>
> Regards,
> Steven
>
> > -----Original Message-----
> > From: owner-ietf-ldapbis@OpenLDAP.org
> > [mailto:owner-ietf-ldapbis@OpenLDAP.org]On Behalf Of RL 'Bob' Morgan
> > Sent: Wednesday, 11 June 2003 19:23
> > To: IETF ldapbis WG
> > Subject: ldapbis WG Last Call on ldapbis-syntaxes, ldapbis-strprep
> >
> >
> >
> > This message initiates a LDAPbis Working Group Last Call on the two
> > documents:
> >
> > LDAP: Syntaxes and Matching Rules
> > draft-ietf-ldapbis-syntaxes-06.txt
> > 3 June 2003
> >
> > and
> >
> > LDAP: Internationalized String Preparation
> > draft-ietf-ldapbis-strprep-00.txt
> > 26 May 2003
> >
> > The purpose of this WG Last Call it to ensure that the
> > Working Group has
> > achieved consensus that these documents are suitable for
> > publication as
> > IETF Standards Track RFCs.
> >
> > Please review the documents for both technical and
> editorial problems.
> > Technical issues should be discussed on this list. Editorial
> > issues may
> > be sent to the document editors.
> >
> > The Last Call period will end on Wednesday, June 25, 2003.
> >
> > Upon completion of the Last Call, the WG chair(s) will take
> > action based
> > upon the consensus of the WG. Possible actions include:
> >
> > 1) recommending to the IETF Application Area Directors that the
> > documents, after possible editorial or other minor changes, be
> > considered by the IESG for publication as Standards Track RFCs
> > (which generally involves an IETF-wide Last Call); or
> >
> > 2) requiring that outstanding issues be adequately addressed prior
> > to further action (including, possibly, another Last Call).
> >
> > Remember that it is our responsibility as Working Group members to
> > ensure the quality of our documents and of the Internet Standards
> > process. So, please read and comment!
> >
> > - RL "Bob" Morgan
> > LDAPbis co-chair
> >
> >
> >
> >
> >
>
>