RFC 4530 on Lightweight Directory Access Protocol (LDAP) entryUUID Operational Attribute

[rfc-editor at rfc-editor.org]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4530

        Title:      Lightweight Directory Access Protocol (LDAP) 
                    entryUUID Operational Attribute 
        Author:     K. Zeilenga
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    Kurt at OpenLDAP.org
        Pages:      8
        Characters: 15191
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-zeilenga-ldap-uuid-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4530.txt

This document describes the LDAP/X.500 'entryUUID' operational
attribute and associated matching rules and syntax.  The attribute
holds a server-assigned Universally Unique Identifier (UUID) for the
object.  Directory clients may use this attribute to distinguish
objects identified by a distinguished name or to locate an object
after renaming.  [STANDARDS TRACK]

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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds aFrom ietf-announce-bounces at ietf.org Thu Jun 08 21:00:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FoVK2-0001ZM-B8; Thu, 08 Jun 2006 20:57:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FoVK0-0001WD-Py
	for ietf-announce at ietf.org; Thu, 08 Jun 2006 20:57:56 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoVJz-0006lC-17
	for ietf-announce at ietf.org; Thu, 08 Jun 2006 20:57:56 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k590vsg6002612; 
	Thu, 8 Jun 2006 17:57:54 -0700
Received: (from apache at localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k590vsFZ002611;
	Thu, 8 Jun 2006 17:57:54 -0700
Date: Thu, 8 Jun 2006 17:57:54 -0700
Message-Id: <200606090057.k590vsFZ002611 at nit.isi.edu>
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
From: rfc-editor at rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: rfc-editor at rfc-editor.org
Subject: RFC 4531 on Lightweight Directory Access Protocol (LDAP) Turn
	Operation
X-BeenThere: ietf-announce at ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce at ietf.org>
List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
	<mailto:ietf-announce-request at ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces at ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4531

        Title:      Lightweight Directory Access Protocol (LDAP) 
                    Turn Operation 
        Author:     K. Zeilenga
        Status:     Experimental
        Date:       June 2006
        Mailbox:    Kurt at OpenLDAP.org
        Pages:      9
        Characters: 18986
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-zeilenga-ldap-turn-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4531.txt

This specification describes a Lightweight Directory Access Protocol
(LDAP) extended operation to reverse (or "turn") the roles of client
and server for subsequent protocol exchanges in the session, or to
enable each peer to act as both client and server with respect to the
other.  This memo defines an Experimental Protocol for the Internet community.

EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet 
community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announcend Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce