RFC 4370 on Lightweight Directory Access Protocol (LDAP) Proxied Authorization Control

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

        RFC 4370

        Title:      Lightweight Directory Access Protocol
(LDAP) 
                    Proxied Authorization Control 
        Author:     R. Weltman
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    robwworldspot.com
        Pages:      5
        Characters: 10624
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-weltman-ldapv3-proxy-13.txt

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

This document defines the Lightweight Directory Access
Protocol
(LDAP) Proxy Authorization Control.  The Proxy Authorization
Control
allows a client to request that an operation be processed
under a
provided authorization identity instead of under the current
authorization identity associated with the connection.  
[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-REQUESTIETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list
should
be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

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

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

...

--ce0e7d224402ae69515dda8c94998424