headers
Internet-Drafts | 3 Jun 2005 21:55
Picon
Favicon

I-D ACTION:draft-ietf-ldapbis-protocol-31.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.

	Title		: LDAP: The Protocol
	Author(s)	: J. Sermersheim
	Filename	: draft-ietf-ldapbis-protocol-31.txt
	Pages		: 64
	Date		: 2005-6-3
	
This document describes the protocol elements, along with their 
   semantics and encodings, of the Lightweight Directory Access Protocol 
   (LDAP). LDAP provides access to distributed directory services that 
   act in accordance with X.500 data and service models. These protocol 
   elements are based on those described in the X.500 Directory Access 
   Protocol (DAP).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-protocol-31.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ldapbis-protocol-31.txt".

A list of Internet-Drafts directories can be found in
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kurt D. Zeilenga | 22 Jun 2005 02:10

IETF ldapbis WG Last Call: draft-ietf-ldapbis-user-schema-05.txt

This message initiates a LDAPbis Working Group Last Call on the
document:

          LDAP: Schema for User Applications
          <draft-ietf-ldapbis-user-schema-09.txt>

The purpose of this WG Last Call it to ensure that the Working Group
has achieved consensus that the document is suitable for publication
as an IETF Draft Standard.

Please review the document for both technical and editorial problems.
Technical issues should be discussed on this list.  Editorial issues
may be sent to the document editor.

The Last Call period will end on Wednesday, June 6, 2005.

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
     document, after possible editorial or other minor changes, be
     considered by the IESG for publication as a Draft Standard
     (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!
(Continue reading)

Permalink | Reply | 3 comments |
headers
Andrew Sciberras | 22 Jun 2005 04:13

Re: IETF ldapbis WG Last Call: draft-ietf-ldapbis-user-schema-05.txt

Hi,

I would just like to note that there are some issues with this draft 
that I am currently aware of.

* The X.500 reference should reference the X.500 recommendation instead 
of X.501-X.525
* The Example in 2.13 requires the text: "a the"  to be replaced with "the"
* The mis-spelt word "attributer" appears in the Security Consideration.
* The security considerations contains the following text:
in RFC 2377 by A. Grimstad, R. Huber, S, Sataluri and M. Smith.
Where "S," needs to be changed to "S."

Also, note that the current version that should be reviewed is -09 and 
that the last call period will end July 6.

Thanks,
Andrew Sciberras
Permalink | Reply | 1 comment |
headers
Kurt D. Zeilenga | 22 Jun 2005 05:01

Re: IETF ldapbis WG Last Call: draft-ietf-ldapbis-user-schema-05.txt

At 07:13 PM 6/21/2005, Andrew Sciberras wrote:
>Also, note that the current version that should be reviewed is -09 and that the last call period will end
July 6. 

Yes!  Thanks, Kurt
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 23 Jun 2005 21:50
Picon
Favicon

I-D ACTION:draft-ietf-ldapbis-syntaxes-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.

	Title		: Lightweight Directory Access Protocol (LDAP):
                          Syntaxes and Matching Rules
	Author(s)	: S. Legg
	Filename	: draft-ietf-ldapbis-syntaxes-11.txt
	Pages		: 54
	Date		: 2005-6-23
	
Each attribute stored in a Lightweight Directory Access Protocol
   (LDAP) directory, and whose values may be transfered in the LDAP
   protocol, has a defined syntax which constrains the structure and
   format of its values.  The comparison semantics for values of a
   syntax are not part of the syntax definition but are instead provided
   through separately defined matching rules.  Matching rules specify an
   argument, an assertion value, which also has a defined syntax.  This
   document defines a base set of syntaxes and matching rules for use in
   defining attributes for LDAP directories.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-syntaxes-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Steven Legg | 24 Jun 2005 01:12

Re: I-D ACTION:draft-ietf-ldapbis-syntaxes-11.txt


The latest changes to the syntaxes draft are purely editorial.

- A missing reference to ISO 8601 has been added.

- Text clarifying the <fraction> part of a GeneralizedTime has
  been added:

   If <minute> is omitted then <fraction> represents a fraction of an
   hour, otherwise if <second> and <leap-second> are omitted then
   <fraction> represents a fraction of a minute, otherwise <fraction>
   represents a fraction of a second.

- The reference for ABNF has been changed to rfc2234bis.

- The boilerplate has been updated to the current requirements.

- Kathy's contribution is recognized in the Acknowledgements rather
  than the list of authors.

Regards,
Steven

Internet-Drafts <at> ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
> 
> 	Title		: Lightweight Directory Access Protocol (LDAP):
>                           Syntaxes and Matching Rules
> 	Author(s)	: S. Legg
(Continue reading)

Permalink | Reply | 0 comments |
headers
RL 'Bob' Morgan | 27 Jun 2005 09:02
Favicon

ldapbis WG Last Call on draft-ietf-ldapbis-bcp64-05.txt


This message initiates a LDAPbis Working Group Last Call on the 
document:

                       IANA Considerations for LDAP
                    <draft-ietf-ldapbis-bcp64-05.txt>
                             21 February 2005

The purpose of this WG Last Call is to ensure that the Working Group has 
achieved consensus that this document is suitable for publication as an 
IETF Best Current Practice (BCP) RFC (replacing RFC 3383, the current BCP 
64; see Appendix B for changes this document makes to RFC 3383).

Please review the document for both technical and editorial problems.
Technical issues should be discussed on this list.  Editorial issues may
be sent to the document editor.

The Last Call period will end on Monday, July 11, 2005.

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
      document, after possible editorial or other minor changes, be
      considered by the IESG for publication as a Best Current Practice
      RFC (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).
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kurt D. Zeilenga | 1 Jul 2005 04:22

IESG ldapbis-protocol comment

Jim,

One of the IESG comments is:
>  It is recommended that ASN.1 module be named by ab object identifier
>  so that it can be unambiguously referenced from other modules.  This
>  facilitates IMPORT by other ASN.1 modules of the types defined here.
>  IANA can assign the ASN.1 module object identifier. 

We should likely do this.  Aside from the ASN.1 work, we'll
need to add an IANA Consideration to get the OID.

Comments?

Kurt
Permalink | Reply | 0 comments |

Gmane