You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ao...@bellsouth.net> on 2006/06/09 02:57:19 UTC
New Revised LDAP RFC Replacements are DONE!
Guys,
These specs replace the old standard set of LDAP RFCs. They're updated
and clarify missing portions of the old RFCs.
Cheers,
Alex
Re: New Revised LDAP RFC Replacements are DONE!
Posted by Ersin Er <er...@gmail.com>.
Ersin Er wrote:
> Emmanuel Lecharny wrote:
>> Alex Karasulu a écrit :
>>
>>> Guys,
>>>
>>> These specs replace the old standard set of LDAP RFCs. They're updated
>>> and clarify missing portions of the old RFCs.
>>>
>>>
>> Whaou !
>>
>> These are the base for a ADS 2.0 version, no ? :-)
>
> Yeah, it will be another fantastic story.. ;-)
>
> BTW, these RFCs are really clarify things a lot. See their change logs
> for details.
>
BTW, you can access all Internet RFCs sorted by publish date here:
http://rfc.x42.com/
Kurt is going fast with LDAP RFCs. :-)
--
Ersin
Re: New Revised LDAP RFC Replacements are DONE!
Posted by Ersin Er <er...@gmail.com>.
Emmanuel Lecharny wrote:
> Alex Karasulu a écrit :
>
>> Guys,
>>
>> These specs replace the old standard set of LDAP RFCs. They're updated
>> and clarify missing portions of the old RFCs.
>>
>>
> Whaou !
>
> These are the base for a ADS 2.0 version, no ? :-)
Yeah, it will be another fantastic story.. ;-)
BTW, these RFCs are really clarify things a lot. See their change logs
for details.
--
Ersin
> Emmanuel
>
>> Cheers,
>> Alex
Re: New Revised LDAP RFC Replacements are DONE!
Posted by Emmanuel Lecharny <el...@gmail.com>.
Alex Karasulu a écrit :
>Guys,
>
>These specs replace the old standard set of LDAP RFCs. They're updated
>and clarify missing portions of the old RFCs.
>
>
Whaou !
These are the base for a ADS 2.0 version, no ? :-)
Emmanuel
>Cheers,
>Alex
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4511 on Lightweight Directory Access Protocol (LDAP): The Protocol
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:52:53 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4511
>
> Title: Lightweight Directory Access Protocol (LDAP):
> The Protocol
> Author: J. Sermersheim, Ed.
> Status: Standards Track
> Date: June 2006
> Mailbox: jimse@novell.com
> Pages: 68
> Characters: 150116
> Obsoletes: RFC2251, RFC2830, RFC3771
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-protocol-32.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4511.txt
>
>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). [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements.Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4510 on Lightweight Directory Access Protocol (LDAP): Technical
> Specification Road Map
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:53:31 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4510
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Technical Specification Road Map
> Author: K. Zeilenga
> Status: Standards Track
> Date: June 2006
> Mailbox: Kurt@OpenLDAP.org
> Pages: 7
> Characters: 12354
> Obsoletes: RFC2251, RFC2252, RFC2253, RFC2254, RFC2255, RFC2256,
> RFC2829, RFC2830, RFC3377, RFC3771
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-roadmap-08.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4510.txt
>
>The Lightweight Directory Access Protocol (LDAP) is an Internet
>protocol for accessing distributed directory services that act in
>accordance with X.500 data and service models. This document provides
>a road map of the LDAP Technical Specification. [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4513 on Lightweight Directory Access Protocol (LDAP):
> Authentication Methods and Security Mechanisms
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:54:08 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4513
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Authentication Methods and Security Mechanisms
> Author: R. Harrison, Ed.
> Status: Standards Track
> Date: June 2006
> Mailbox: roger_harrison@novell.com
> Pages: 34
> Characters: 80546
> Obsoletes: RFC2251, RFC2829, RFC2830
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-authmeth-19.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4513.txt
>
>This document describes authentication methods and security
>mechanisms of the Lightweight Directory Access Protocol (LDAP).
>This document details establishment of Transport Layer Security
>(TLS) using the StartTLS operation.
>
>This document details the simple Bind authentication method
>including anonymous, unauthenticated, and name/password mechanisms
>and the Simple Authentication and Security Layer (SASL) Bind
>authentication method including the EXTERNAL mechanism.
>
>This document discusses various authentication and authorization
>states through which a session to an LDAP server may pass and the
>actions that trigger these state changes.
>
>This document, together with other documents in the LDAP Technical
>Specification (see Section 1 of the specification's road map),
>obsoletes RFC 2251, RFC 2829, and RFC 2830. [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4514 on Lightweight Directory Access Protocol (LDAP): String
> Representation of Distinguished Names
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:54:41 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4514
>
> Title: Lightweight Directory Access Protocol (LDAP):
> String Representation of Distinguished Names
> Author: K. Zeilenga, Ed.
> Status: Standards Track
> Date: June 2006
> Mailbox: Kurt@OpenLDAP.org
> Pages: 15
> Characters: 31859
> Obsoletes: RFC2253
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-dn-16.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4514.txt
>
>The X.500 Directory uses distinguished names (DNs) as primary keys to
>entries in the directory. This document defines the string
>representation used in the Lightweight Directory Access Protocol
>(LDAP) to transfer distinguished names. The string representation is
>designed to give a clean representation of commonly used distinguished
>names, while being able to represent any distinguished name. [STANDARDS
>TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization state
>and status of this protocol. Distribution of this memo is unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4517 on Lightweight Directory Access Protocol (LDAP): Syntaxes and
> Matching Rules
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:55:16 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4517
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Syntaxes and Matching Rules
> Author: S. Legg, Ed.
> Status: Standards Track
> Date: June 2006
> Mailbox: steven.legg@eb2bcom.com
> Pages: 53
> Characters: 114285
>
>
> I-D Tag: draft-ietf-ldapbis-syntaxes-11.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4517.txt
>
>Each attribute stored in a Lightweight Directory Access Protocol
>(LDAP) directory, whose values may be transferred in the LDAP
>protocol, has a defined syntax that 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. [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4515 on Lightweight Directory Access Protocol (LDAP): String
> Representation of Search Filters
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:55:44 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4515
>
> Title: Lightweight Directory Access Protocol (LDAP):
> String Representation of Search Filters
> Author: M. Smith, Ed., T. Howes
> Status: Standards Track
> Date: June 2006
> Mailbox: mcs@pearlcrescent.com,
> howes@opsware.com
> Pages: 12
> Characters: 23885
> Obsoletes: RFC2254
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-filter-09.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4515.txt
>
>Lightweight Directory Access Protocol (LDAP) search filters are
>transmitted in the LDAP protocol using a binary representation that is
>appropriate for use on the network. This document defines a
>human-readable string representation of LDAP search filters that is
>appropriate for use in LDAP URLs (RFC 4516) and in other applications.
>[STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4516 on Lightweight Directory Access Protocol (LDAP): Uniform
> Resource Locator
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:56:08 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4516
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Uniform Resource Locator
> Author: M. Smith, Ed., T. Howes
> Status: Standards Track
> Date: June 2006
> Mailbox: mcs@pearlcrescent.com,
> howes@opsware.com
> Pages: 15
> Characters: 30562
> Obsoletes: RFC2255
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-url-09.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4516.txt
>
>This document describes a format for a Lightweight Directory Access
>Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL
>describes an LDAP search operation that is used to retrieve
>information from an LDAP directory, or, in the context of an LDAP
>referral or reference, an LDAP URL describes a service where an LDAP
>operation may be progressed. [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4518 on Lightweight Directory Access Protocol (LDAP):
> Internationalized String Preparation
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:56:35 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4518
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Internationalized String Preparation
> Author: K. Zeilenga
> Status: Standards Track
> Date: June 2006
> Mailbox: Kurt@OpenLDAP.org
> Pages: 14
> Characters: 28166
> Updates/Obsoletes/SeeAlso: None
>
> I-D Tag: draft-ietf-ldapbis-strprep-07.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4518.txt
>
>The previous Lightweight Directory Access Protocol (LDAP) technical
>specifications did not precisely define how character string matching
>is to be performed. This led to a number of usability and
>interoperability problems. This document defines string preparation
>algorithms for character-based matching rules defined for use in LDAP. [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4519 on Lightweight Directory Access Protocol (LDAP): Schema for
> User Applications
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:56:50 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4519
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Schema for User Applications
> Author: A. Sciberras, Ed.
> Status: Standards Track
> Date: June 2006
> Mailbox: andrew.sciberras@eb2bcom.com
> Pages: 35
> Characters: 64996
>
>
> I-D Tag: draft-ietf-ldapbis-user-schema-11.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4519.txt
>
>This document is an integral part of the Lightweight Directory Access
>Protocol (LDAP) technical specification. It provides a
>technical specification of attribute types and object classes
>intended for use by LDAP directory clients for many directory
>services, such as White Pages. These objects are widely used as a
>basis for the schema in many LDAP directories. This document does
>not cover attributes used for the administration of directory
>servers, nor does it include directory objects defined for specific
>uses in other documents. [STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> Sujet:
> RFC 4512 on Lightweight Directory Access Protocol (LDAP): Directory
> Information Models
> Expéditeur:
> rfc-editor@rfc-editor.org
> Date:
> Thu, 8 Jun 2006 16:57:12 -0700
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
>
> Destinataire:
> ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Copie à:
> rfc-editor@rfc-editor.org, ietf-ldapbis@OpenLDAP.org
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>
> RFC 4512
>
> Title: Lightweight Directory Access Protocol (LDAP):
> Directory Information Models
> Author: K. Zeilenga, Ed.
> Status: Standards Track
> Date: June 2006
> Mailbox: Kurt@OpenLDAP.org
> Pages: 52
> Characters: 108377
> Obsoletes: RFC2251, RFC2252, RFC2256, RFC3674
> See-Also:
>
> I-D Tag: draft-ietf-ldapbis-models-14.txt
>
> URL: http://www.rfc-editor.org/rfc/rfc4512.txt
>
>The Lightweight Directory Access Protocol (LDAP) is an Internet
>protocol for accessing distributed directory services that act in
>accordance with X.500 data and service models. This document
>describes the X.500 Directory Information Models, as used in LDAP.
>[STANDARDS TRACK]
>
>This document is a product of the LDAP (v3) Revision
>Working Group of the IETF.
>
>This is now a Proposed Standard Protocol.
>
>STANDARDS TRACK: This document specifies an Internet standards track
>protocol for the Internet community,and requests discussion and
>suggestions for improvements. Please refer to the current edition of the
>Internet Official Protocol Standards (STD 1) for the standardization
>state and status of this protocol. Distribution of this memo is
>unlimited.
>
>This announcement is sent to the IETF list and the RFC-DIST list.
>Requests to be added to or deleted from the IETF distribution list
>should be sent to IETF-REQUEST@IETF.ORG. Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
>help: ways_to_get_rfcs. For example:
>
> To: rfc-info@RFC-EDITOR.ORG
> Subject: getting rfcs
>
> help: ways_to_get_rfcs
>
>Requests for special distribution should be addressed to either the
>author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>Joyce K. Reynolds and Sandy Ginoza
>USC/Information Sciences Institute
>
>...
>
>
>
>
>
Re: New Revised LDAP RFC Replacements are DONE!
Posted by Ersin Er <er...@gmail.com>.
Alex Karasulu wrote:
> Guys,
>
> These specs replace the old standard set of LDAP RFCs. They're updated
> and clarify missing portions of the old RFCs.
>
> Cheers,
> Alex
I have been reading ldapbis RFCs since I've been involved in this
project and they were somewhat better than older ones. These updates are
great contribution to the community of directory. However lots of stuff
to read... :-) (Well, as I see they are released from final drafts which
I have already read :-) )
Alex, thanks for the news.
--
Ersin