idnits 2.17.1 draft-mrose-apex-historic-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 17. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 127. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 138. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 145. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 151. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) -- The draft header indicates that this document obsoletes RFC3343, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC3340, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC3341, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document obsoletes RFC3342, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 31, 2007) is 6174 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3920 (Obsoleted by RFC 6120) ** Obsolete normative reference: RFC 3921 (Obsoleted by RFC 6121) Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Rose 3 Internet-Draft Dover Beach Consulting, Inc. 4 Obsoletes: 3340 3341 3342 3343 May 31, 2007 5 (if approved) 6 Intended status: Informational 7 Expires: December 2, 2007 9 Reclassification of the APEX RFCs to Historic 10 draft-mrose-apex-historic-02 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that any 15 applicable patent or other IPR claims of which he or she is aware 16 have been or will be disclosed, and any of which he or she becomes 17 aware will be disclosed, in accordance with Section 6 of BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt. 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 This Internet-Draft will expire on December 2, 2007. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2007). 41 Abstract 43 This memo reclassifies the APEX RFCs (RFCs 3340-3343) from PROPOSED 44 STANDARD to HISTORIC. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 50 3. Normative References . . . . . . . . . . . . . . . . . . . . . 5 51 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 52 Intellectual Property and Copyright Statements . . . . . . . . . . 7 54 1. Introduction 56 The Application Exchange (APEX) service is defined in four RFCs: 57 [RFC3340], [RFC3341], [RFC3342], and [RFC3343]. 59 To the author's knowledge, no implementations of these RFCs were ever 60 deployed. 62 To the author's knowledge, all of APEX's functionality is currently 63 provided by XMPP ([RFC3920], and [RFC3921], and [RFC3923]), which 64 enjoys extrodinarily robust deployment. 66 Accordingly, the APEX RFCs are reclassified to Historic status. 68 2. Security Considerations 70 The Security Considerations section of the XMPP documents are 71 considerably more detailed than those of the APEX documents, and are 72 believed to provide security at least as strong as APEX. 73 Accordingly, no decrease in security is envisioned. 75 3. Normative References 77 [RFC3340] Rose, M., Klyne, G., and D. Crocker, "The Application 78 Exchange Core", RFC 3340, July 2002. 80 [RFC3341] Rose, M., Klyne, G., and D. Crocker, "The Application 81 Exchange (APEX) Access Service", RFC 3341, July 2002. 83 [RFC3342] Klyne, G., Rose, M., Schwartz, M., Dixon, E., Franklin, 84 H., Kint, J., New, D., and S. Pead, "The Application 85 Exchange (APEX) Option Party Pack, Part Deux!", RFC 3342, 86 July 2002. 88 [RFC3343] Rose, M., Klyne, G., and D. Crocker, "The Application 89 Exchange (APEX) Presence Service", RFC 3343, April 2003. 91 [RFC3920] Saint-Andre, P., Ed., "Extensible Messaging and Presence 92 Protocol (XMPP): Core", RFC 3920, October 2004. 94 [RFC3921] Saint-Andre, P., Ed., "Extensible Messaging and Presence 95 Protocol (XMPP): Instant Messaging and Presence", 96 RFC 3921, October 2004. 98 [RFC3923] Saint-Andre, P., "End-to-End Signing and Object Encryption 99 for the Extensible Messaging and Presence Protocol 100 (XMPP)", RFC 3923, October 2004. 102 Author's Address 104 Marshall T. Rose 105 Dover Beach Consulting, Inc. 106 POB 255268 107 Sacramento, CA 95865-5268 108 US 110 Phone: +1 916 483 8878 111 Email: mrose@dbc.mtview.ca.us 113 Full Copyright Statement 115 Copyright (C) The IETF Trust (2007). 117 This document is subject to the rights, licenses and restrictions 118 contained in BCP 78, and except as set forth therein, the authors 119 retain all their rights. 121 This document and the information contained herein are provided on an 122 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 123 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 124 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 125 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 126 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 127 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 129 Intellectual Property 131 The IETF takes no position regarding the validity or scope of any 132 Intellectual Property Rights or other rights that might be claimed to 133 pertain to the implementation or use of the technology described in 134 this document or the extent to which any license under such rights 135 might or might not be available; nor does it represent that it has 136 made any independent effort to identify any such rights. Information 137 on the procedures with respect to rights in RFC documents can be 138 found in BCP 78 and BCP 79. 140 Copies of IPR disclosures made to the IETF Secretariat and any 141 assurances of licenses to be made available, or the result of an 142 attempt made to obtain a general license or permission for the use of 143 such proprietary rights by implementers or users of this 144 specification can be obtained from the IETF on-line IPR repository at 145 http://www.ietf.org/ipr. 147 The IETF invites any interested party to bring to its attention any 148 copyrights, patents or patent applications, or other proprietary 149 rights that may cover technology that may be required to implement 150 this standard. Please address the information to the IETF at 151 ietf-ipr@ietf.org. 153 Acknowledgment 155 Funding for the RFC Editor function is provided by the IETF 156 Administrative Support Activity (IASA).