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

Network Working Group                                        K. Zeilenga
Request for Comments: 3352                           OpenLDAP Foundation
Obsoletes: <a href="./rfc1798">1798</a>                                               March 2003
Category: Informational


     <span class="h1">Connection-less Lightweight Directory Access Protocol (CLDAP)</span>
                           <span class="h1">to Historic Status</span>


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, <a href="./rfc1798">RFC 1798</a>, 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 <a href="./rfc1798">RFC 1798</a> be moved to Historic status.

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Background</span>

   Connection-less Lightweight Directory Access Protocol (CLDAP)
   [<a href="./rfc1798">RFC1798</a>] 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) [<a href="./rfc1777" title=""Lightweight Directory Access Protocol"">RFC1777</a>], now
   Historic [<a href="#ref-HISTORIC" title=""Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status"">HISTORIC</a>].

   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



<span class="grey">Zeilenga                     Informational                      [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc3352">RFC 3352</a>                CLDAP to Historic Status              March 2003</span>


   - 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), <a href="./rfc1487">RFC 1487</a> (the predecessor to <a href="./rfc1777">RFC 1777</a>, 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
   updated.  In response to this, the IETF chartered the LDAP Extensions
   Working Group (LDAPext WG) in 1997 to undertake this update.  The
   LDAPext WG is concluding without producing an update to CLDAP.
   Currently, there is no standardization effort to update CLDAP.

   It should be noted that the community still has interest in
   developing a "connection-less" directory access protocol.  However,
   based on operational experience, has determined that further
   experimentation is necessary to address outstanding technical issues.
   In particular, security considerations associated with
   "connection-less" services need to be addressed.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Recommendation</span>

   As there is no viable standardization effort to update CLDAP as
   necessary to keep it on the standards track and the community
   currently considers this an area requiring further experimentation,
   <a href="./rfc1798">RFC 1798</a> must be moved to Historic status.

   It is recommended that those interested in connection-less access to
   X.500-based directory services experiment with [<a href="#ref-LDAPUDP" title=""Lightweight Directory Access Protocol over UDP/IP,"">LDAPUDP</a>] and other
   alternatives which might become available.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>

   The security of the Internet will not be impacted by the retirement
   of CLDAP.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Acknowledgment</span>

   The author would like to thank the designers of CLDAP for their
   contribution to the Internet community.




<span class="grey">Zeilenga                     Informational                      [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc3352">RFC 3352</a>                CLDAP to Historic Status              March 2003</span>


<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Normative References</span>

   [<a id="ref-HISTORIC">HISTORIC</a>] Zeilenga, K., "Lightweight Directory Access Protocol
              version 2 (LDAPv2) to Historic Status", <a href="./rfc3494">RFC 3494</a>, February
              2003.

   [<a id="ref-CLDAP">CLDAP</a>]    Young, A. "Connection-less Lightweight Directory Access
              Protocol," <a href="./rfc1798">RFC 1798</a>, June 1995.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Informative References</span>

   [<a id="ref-LDAPUDP">LDAPUDP</a>]  Johansson, L. and R. Hedberg, "Lightweight Directory
              Access Protocol over UDP/IP," Work in Progress.

   [<a id="ref-RFC1777">RFC1777</a>]  Yeong, W., Howes, T. and S. Kille, "Lightweight Directory
              Access Protocol", <a href="./rfc1777">RFC 1777</a>, March 1995.

   [<a id="ref-RFC3377">RFC3377</a>]  Hodges, J. and R. Morgan, "Lightweight Directory Access
              Protocol (v3): Technical Specification", <a href="./rfc3377">RFC 3377</a>,
              September 2002.

   [<a id="ref-X501">X501</a>]     The Directory: Models.  CCITT Recommendation X.501 ISO/IEC
              JTC 1/SC21; International Standard 9594-2, 1988.

   [<a id="ref-X511">X511</a>]     The Directory: Abstract Service Definition.  CCITT
              Recommendation X.511, ISO/IEC JTC 1/SC21; International
              Standard 9594-3, 1988.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Author's Address</span>

   Kurt D. Zeilenga
   OpenLDAP Foundation

   EMail: [email protected]

















<span class="grey">Zeilenga                     Informational                      [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc3352">RFC 3352</a>                CLDAP to Historic Status              March 2003</span>


<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Full Copyright Statement</span>

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Zeilenga                     Informational                      [Page 4]