[rfc-dist] RFC 4522 on Lightweight Directory Access Protocol (LDAP): The Binary Encoding Option

[rfc-editor at rfc-editor.org ([e-mail])]

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

        
        RFC 4522

        Title:      Lightweight Directory Access Protocol (LDAP): 
                    The Binary Encoding Option 
        Author:     S. Legg
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    steven.legg at eb2bcom.com
        Pages:      8
        Characters: 16276
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-legg-ldap-binary-04.txt

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

Each attribute stored in a Lightweight Directory Access Protocol (LDAP) 
directory has a defined syntax (i.e., data type).
A syntax definition specifies how attribute values
conforming to the syntax are
normally represented when transferred in LDAP operations.
This representation is referred to as the LDAP-specific encoding
to distinguish it from other methods of encoding attribute values.
This document defines an attribute option, the binary option,
that can be used to specify that the associated attribute values are
instead encoded according to the Basic Encoding Rules (BER)
used by X.500 directories.  [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 and Sandy Ginoza
USC/Information Sciences Institute

...