[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RFC 4522 on Lightweight Directory Access Protocol (LDAP): The Binary Encoding Option
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 RFCFrom ietf-announce-bounces at ietf.org Thu Jun 08 21:33:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FoVpV-0007Py-M2; Thu, 08 Jun 2006 21:30:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1FoVpT-0007Pj-RN
for ietf-announce at ietf.org; Thu, 08 Jun 2006 21:30:27 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
helo=chiedprmail1.ietf.org)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoV08-0003oQ-84
for ietf-announce at ietf.org; Thu, 08 Jun 2006 20:37:24 -0400
Received: from nit.isi.edu ([128.9.160.116])
by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FoUow-0003bJ-PZ
for ietf-announce at ietf.org; Thu, 08 Jun 2006 20:25:53 -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 k590PolT002473;
Thu, 8 Jun 2006 17:25:50 -0700
Received: (from apache at localhost)
by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k590Povn002472;
Thu, 8 Jun 2006 17:25:50 -0700
Date: Thu, 8 Jun 2006 17:25:50 -0700
Message-Id: <200606090025.k590Povn002472 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: -17.6 (-----------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: rfc-editor at rfc-editor.org
Subject: RFC 4522 on Lightweight Directory Access Protocol (LDAP): The
Binary Encoding Option
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 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
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce