Browse Prior Art Database

Connection-less Lightweight Directory Access Protocol (CLDAP) to Historic Status (RFC3352)

IP.com Disclosure Number: IPCOM000011557D
Original Publication Date: 2003-Mar-01
Included in the Prior Art Database: 2003-Mar-05
Document File: 5 page(s) / 7K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Zeilenga: AUTHOR

Abstract

The Connection-less Lightweight Directory Access Protocol (CLDAP) technical specification, RFC 1798, was published in 1995 as a Proposed Standard. This document discusses the reasons why the CLDAP technical specification has not been furthered on the Standard Track. This document recommends that RFC 1798 be moved to Historic status.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 38% of the total text.

Network Working Group                                        K. Zeilenga

Request for Comments: 3352                           OpenLDAP Foundation

Obsoletes: 1798                                               March 2003

Category: Informational

     Connection-less Lightweight Directory Access Protocol (CLDAP)

                           to Historic Status

Status of this Memo

   This memo provides information for the Internet community.  It does

   not specify an Internet standard of any kind.  Distribution of this

   memo is unlimited.

Copyright Notice

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

Abstract

   The Connection-less Lightweight Directory Access Protocol (CLDAP)

   technical specification, RFC 1798, was published in 1995 as a

   Proposed Standard.  This document discusses the reasons why the CLDAP

   technical specification has not been furthered on the Standard Track.

   This document recommends that RFC 1798 be moved to Historic status.

1. Background

   Connection-less Lightweight Directory Access Protocol (CLDAP)

   [RFC1798] was published in 1995 as a Proposed Standard.  The protocol

   was targeted at applications which require lookup of small amounts of

   information held in the directory.  The protocol avoids the overhead

   of establishing (and closing) a connection and the session bind and

   unbind operations needed in connection-oriented directory access

   protocols.  The CLDAP was designed to complement version 2 of the

   Lightweight Directory Access Protocol (LDAPv2) [RFC1777], now

   Historic [HISTORIC].

   In the seven years since its publication, CLDAP has not become widely

   deployed on the Internet.  There are a number of probable reasons for

   this:

   - Limited functionality:

        + anonymous only,

        + read only,

        + small result sizes only, and

Zeilenga                     Informational                      [Page 1]

RFC 3352                CLDAP to Historic Status              March 2003

   - Insufficient security capabilities:

        + no integrity protection,

        + no confidentiality protection

   - Inadequate internationalization support;

   - Insufficient extensibility; and

   - Lack of multiple independently developed implementations.

   The CLDAP technical specification has normative references to

   multiple obsolete technical specifications including X.501(88),

   X.511(88), RFC 1487 (the predecessor to RFC 1777, the now Historic

   LDAPv2 technical specification).  Unless the technical specification

   were to be updated, CLDAP cannot remain on the standards track

   because of the Normative reference to a Historic RFC.

   The community recognized in the mid-1990s that CLDAP needed to be

   update...