Browse Prior Art Database

Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions (RFC2252) Disclosure Number: IPCOM000002811D
Original Publication Date: 1997-Dec-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 26 page(s) / 55K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Wahl: AUTHOR [+3]


The Lightweight Directory Access Protocol (LDAP) [1] requires that the contents of AttributeValue fields in protocol elements be octet strings. This document defines a set of syntaxes for LDAPv3, and the rules by which attribute values of these syntaxes are represented as octet strings for transmission in the LDAP protocol. The syntaxes defined in this document are referenced by this and other documents that define attribute types. This document also defines the set of attribute types which LDAP servers should support.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group M. Wahl

Request for Comments: 2252 Critical Angle Inc.

Category: Standards Track A. Coulbeck

Isode Inc.

T. Howes

Netscape Communications Corp.

S. Kille

Isode Limited

December 1997

Lightweight Directory Access Protocol (v3):

Attribute Syntax Definitions

1. Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (1997). All Rights Reserved.


This document describes a directory access protocol that provides

both read and update access. Update access requires secure

authentication, but this document does not mandate implementation of

any satisfactory authentication mechanisms.

In accordance with RFC 2026, section 4.4.1, this specification is

being approved by IESG as a Proposed Standard despite this

limitation, for the following reasons:

a. to encourage implementation and interoperability testing of

these protocols (with or without update access) before they

are deployed, and

b. to encourage deployment and use of these protocols in read-only

applications. (e.g. applications where LDAPv3 is used as

a query language for directories which are updated by some

secure mechanism other than LDAP), and

c. to avoid delaying the advancement and deployment of other Internet

standards-track protocols which require the ability to query, but

not update, LDAPv3 directory servers.

Readers are hereby warned that until mandatory authentication

mechanisms are standardized, clients and servers written according to

this specification which make use of update functionality are



Implementors are hereby discouraged from deploying LDAPv3 clients or

servers which implement the update functionality, until a...