INTERNET-DRAFT Kurt D. Zeilenga Intended Category: Informational OpenLDAP Foundation Expires in six months 23 October 2004 Obsoletes: Old X.500/LDAP RFCs to Historic Status of Memo This document is intended to be, after appropriate review and revision, submitted to the RFC Editor as an Informational document. Distribution of this memo is unlimited. Technical discussion of this document will take place on the IETF Directory Interest mailing list . Please send editorial comments directly to the document editor . By submitting this Internet-Draft, I accept the provisions of Section 4 of RFC 3667. By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at . The list of Internet-Draft Shadow Directories can be accessed at . Copyright (C) The Internet Society (2004). All Rights Reserved. Please see the Full Copyright section near the end of this document for more information. Abstract Zeilenga Old X.500 RFCs to Historic Status [Page 1] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 This document recommends the retirement of various early X.500 and LDAP RFCs documents which are no longer relevant to the Internet community, except for historical purposes. 1. Introduction This document recommends the following old X.500 and LDAP related RFCs be moved to Historic status: - "Directory Assistance Service" [RFC1202], - "DIXIE Protocol Specification" [RFC1249], - "Replication Requirements to provide an Internet Directory using X.500" [RFC1275], - "Replication and Distributed Operations extensions to provide an Internet using X.500" [RFC1276], - "X.500 and Domains" [RFC1279] - "Portable DUAs" [RFC1373] - "DUA Metrics" [RFC1431] - "A Survey of Advanced Usages of X.500" [RFC1491] (also FYI 21) - "DSA Metrics" [RFC1564] - "Schema Publishing in X.500 Directory" [RFC1804] - "The LDAP Application Program Interface" [RFC1823] - "A Revised Catalog of Available X.500 Implementations" [RFC2116] (also FYI 11) These documents are no longer relevant to the Internet community, except for historical purposes. Section 2 discusses the rationale for moving each of these documents to Historic status. In many cases, these documents are superceded by more recently published RFCs as noted. 2. Rationale 2.1. RFC 1202 RFC 1202 describes the Directory Assistance Service, a protocol designed to provide access to the X.500 directory service through a Directory User Agent serving as a gateway. This protocol is not believed to be in use on the Internet. The protocol is deprecated in favor of LDAP. RFC 1202 is only of historic interest. RFC 1202 was published in 1991 as Informational. 2.2. RFC 1249 Zeilenga Old X.500 RFCs to Historic Status [Page 2] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 RFC 1249 describes the DIXIE protocol, a protocol designed to provide access to the X.500 Directory Service. The protocol is not believed to be in use on the Internet. DIXIE was deprecated in favor of LDAP. RFC 1249 is now only of historical interest. RFC 1249 was published in 1991 as Informational. 2.3. RFC 1275 RFC 1275 discussed deficiencies of the X.500(1998) standard in the areas of distributed operations and replication. These deficiences were addressed in subsequent editions of X.500, specifically by [X.525] and [X.518]. Readers should read later documents, such as RFC 3384, to better understand the community requirements in these areas. RFC 1275 was published in 1991 as Informational. 2.4. RFC 1276 RFC 1276 describes "INTERIM" replication and distributed operations extensions to X.500(88). Subsequent editions of X.500 provides standard replication [X.525] and distributed operation [X.518] mechanisms which are technically superior. X.500(88) is now obsolete. RFC 1276 was published in 1991 as Proposed Standard. 2.5. RFC 1279 RFC 1279 discusses the relationship between X.500 distinguished names and Internet domain names. This information is superseded by [RFC2164] and [RFC2247], both Proposed Standards. RFC 1279 was published in 1991 as Experimental. 2.6. RFC 1373 RFC 1373 comes in two parts. The first part provides brief notes on the use of some circa-1992 Directory User Agents (DUAs): "WHOIS interface to X.500", ISODE "de", DIXIE/UD, and "doog". These DUAs are defunct, as is the version of X.500 in use in 1992. The second part provides instructions to ISODE-maintainers wishing to Zeilenga Old X.500 RFCs to Historic Status [Page 3] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 provide DUAs to users. The software referred to as "ISODE" here is defunct, as is the version of X.500 that software implemented. RFC 1373 was published in 1992 as Informational. 2.7. RFC 1431 RFC 1431 purpose was to "define some metrics by which DUA products can be measured." RFC 1431 defined "a set of criteria by which a DUA implementation [...] may be judged" in the form of a questionaire. While this document may have been useful to those judging DUA implementations available in the early 1990s, the questionaire's usefulness for judging modern DUA implementations is limited. (Some questions, of course, transend time.) RFC 1432 was published in 1992 as Informational. 2.8. RFC 1564 RFC 1564 purpose was to "define some metrics by which DSA products can be measured." RFC 1564 defined "a set of criteria by which a DSA implementation [...] may be judged" in the form of a questionaire. While this document may have been useful to those judging DUA implementations available in the early 1990s, the questionaire's usefulness for judging modern DSA implementations limited. (Some questions, of course, transend time.) RFC 1564 was published in 1994 as Informational. 2.9. RFC 1804 RFC 1804 described an experimental mechanism for publishing and distributing schema for information in the Directory. Modern versions of X.500 and LDAP provide standardized mechanisms for publishing and distributing schema information. RFC 1804 was published in 1995 as Experimental. 2.10. RFC 1823 RFC 1823 defined a C language application programming interface (API) to for use in implementing LDAPv2 clients [RFC1777][RFC3494]. While LDAP client libaries of yesterday and today provide similar APIs, the provided APIs do significantly differ. Hence, developers needing Zeilenga Old X.500 RFCs to Historic Status [Page 4] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 information about the API provided by their library of choice, must reply on the library's documentation, not this definition. This is especially true for modern clients using modern libraries. RFC 1823 was published in 1995 as Informational. 2.11. RFC 2116 RFC 2116 provided a catalog of available X.500 implementations. This purpose of publishing this catalog was "to provide an easily accessible source of information on X.500 implementations for those who wish to consider X.500 technology for deploying a Directory service." However, as this the catalog was compiled prior to the introduction of LDAPv3 and currently in-force editions of X.500, it no longer a suitable source of information about currently available X.500 implementations. Those wishing to consider X.500 technology for deploying a Directory service should consider modern implementations. RFC 2116 was published in 1997 as Informational, and as FYI 11. 3. Security Considerations The security of the Internet will not be impacted by the retirement of these specifications. 4. IANA Considerations The port number (96) allocated to the DIXIE protocol should be returned to the pool of available port numbers. 5. Acknowledgment The author would like to thank the developers of these specifications for their contribution to the Internet community. 6. Author's Address Kurt D. Zeilenga OpenLDAP Foundation Email: Kurt@OpenLDAP.org 7. Normative References Zeilenga Old X.500 RFCs to Historic Status [Page 5] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 [RFC1202] Rose, M., "Directory Assistance service", RFC 1202, February 1991. [RFC1249] Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol Specification", RFC 1249, August 1991. [RFC1275] Hardcastle-Kille, S., "Replication Requirements to provide an Internet Directory using X.500", RFC 1275, November 1991. [RFC1276] Hardcastle-Kille, S., "Replication and Distributed Operations extensions to provide an Internet Directory using X.500", RFC 1276, November 1991. [RFC1279] Hardcastle-Kille, S., "X.500 and Domains", RFC 1279, November 1991. [RFC1373] Tignor, T., "Portable DUAs", RFC 1373, October 1992. [RFC1431] Barker, P., "DUA Metrics (OSI-DS 33 (v2))", RFC 1431, February 1993. [RFC1491] Weider, C. and R. Wright, "A Survey of Advanced Usages of X.500", RFC 1491, July 1993. [RFC1564] Barker, P. and R. Hedberg, "DSA Metrics (OSI-DS 34 (v3))", RFC 1564, January 1994. [RFC1804] Mansfield, G., Rajeev, P., Raghavan, S., and T. Howes, "Schema Publishing in X.500 Directory", RFC 1804, June 1995. [RFC1823] Howes, T. and M. Smith, "The LDAP Application Program Interface", RFC 1823, August 1995. [RFC2116] Apple, C. and K. Rossen, "X.500 Implementations Catalog-96", RFC 2116, April 1997. 8. Informative References [RFC1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory Access Protocol", RFC 1777, March 1995. [RFC2164] Kille, S., "Use of an X.500/LDAP directory to support MIXER address mapping", RFC 2164, January 1998. [RFC2247] Kille, S., M. Wahl, A. Grimstad, R. Huber and S. Zeilenga Old X.500 RFCs to Historic Status [Page 6] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 Sataluri, "Using Domains in LDAP/X.500 Distinguished Names", January 1998. [RFC3494] Zeilenga, K., "Lightweight Directory Access Protocol version 2 (LDAPv2) to Historic Status", RFC 3494, March 2003. [Roadmap] Zeilenga, K. (editor), "LDAP: Technical Specification Road Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in progress. [X.500] International Telecommunication Union - Telecommunication Standardization Sector, "The Directory -- Overview of concepts, models and services," X.500(1993) (also ISO/IEC 9594-1:1994). [X.525] International Telecommunication Union - Telecommunication Standardization Sector, "The Directory: Replication", X.525(1993) (also ISO/IEC 9594-9:1993). [X.518] International Telecommunication Union - Telecommunication Standardization Sector, "The Directory -- Procedures for distributed operation," X.518(1993) (also ISO/IEC 9594-4:1994). Intellectual Property Rights The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any Zeilenga Old X.500 RFCs to Historic Status [Page 7] INTERNET-DRAFT draft-zeilenga-x500-historic-01.txt 23 October 2004 copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Full Copyright Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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. Zeilenga Old X.500 RFCs to Historic Status [Page 8]