Network Working Group M. Rose Internet-Draft Dover Beach Consulting, Inc. Obsoletes: 3340 3341 3342 3343 May 31, 2007 (if approved) Intended status: Informational Expires: December 2, 2007 Reclassification of the APEX RFCs to Historic draft-mrose-apex-historic-02 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on December 2, 2007. Copyright Notice Copyright (C) The IETF Trust (2007). Rose Expires December 2, 2007 [Page 1] Internet-Draft APEX RFCs to Historic May 2007 Abstract This memo reclassifies the APEX RFCs (RFCs 3340-3343) from PROPOSED STANDARD to HISTORIC. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 3. Normative References . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Intellectual Property and Copyright Statements . . . . . . . . . . 7 Rose Expires December 2, 2007 [Page 2] Internet-Draft APEX RFCs to Historic May 2007 1. Introduction The Application Exchange (APEX) service is defined in four RFCs: [RFC3340], [RFC3341], [RFC3342], and [RFC3343]. To the author's knowledge, no implementations of these RFCs were ever deployed. To the author's knowledge, all of APEX's functionality is currently provided by XMPP ([RFC3920], and [RFC3921], and [RFC3923]), which enjoys extrodinarily robust deployment. Accordingly, the APEX RFCs are reclassified to Historic status. Rose Expires December 2, 2007 [Page 3] Internet-Draft APEX RFCs to Historic May 2007 2. Security Considerations The Security Considerations section of the XMPP documents are considerably more detailed than those of the APEX documents, and are believed to provide security at least as strong as APEX. Accordingly, no decrease in security is envisioned. Rose Expires December 2, 2007 [Page 4] Internet-Draft APEX RFCs to Historic May 2007 3. Normative References [RFC3340] Rose, M., Klyne, G., and D. Crocker, "The Application Exchange Core", RFC 3340, July 2002. [RFC3341] Rose, M., Klyne, G., and D. Crocker, "The Application Exchange (APEX) Access Service", RFC 3341, July 2002. [RFC3342] Klyne, G., Rose, M., Schwartz, M., Dixon, E., Franklin, H., Kint, J., New, D., and S. Pead, "The Application Exchange (APEX) Option Party Pack, Part Deux!", RFC 3342, July 2002. [RFC3343] Rose, M., Klyne, G., and D. Crocker, "The Application Exchange (APEX) Presence Service", RFC 3343, April 2003. [RFC3920] Saint-Andre, P., Ed., "Extensible Messaging and Presence Protocol (XMPP): Core", RFC 3920, October 2004. [RFC3921] Saint-Andre, P., Ed., "Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence", RFC 3921, October 2004. [RFC3923] Saint-Andre, P., "End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)", RFC 3923, October 2004. Rose Expires December 2, 2007 [Page 5] Internet-Draft APEX RFCs to Historic May 2007 Author's Address Marshall T. Rose Dover Beach Consulting, Inc. POB 255268 Sacramento, CA 95865-5268 US Phone: +1 916 483 8878 Email: mrose@dbc.mtview.ca.us Rose Expires December 2, 2007 [Page 6] Internet-Draft APEX RFCs to Historic May 2007 Full Copyright Statement Copyright (C) The IETF Trust (2007). 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, THE IETF TRUST 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. Intellectual Property 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 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. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Rose Expires December 2, 2007 [Page 7]