idnits 2.17.1 draft-meyer-rfc1267-historic-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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 document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 17 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** There are 2 instances of lines with control characters in the document. ** The abstract seems to contain references ([RFC1267]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Historic RFC: RFC 1267 ** Obsolete normative reference: RFC 1771 (Obsoleted by RFC 4271) Summary: 10 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT David Meyer 2 draft-meyer-rfc1267-historic-00.txt 3 2003.07.28 5 Request to Move RFC1267 to Historic Status 7 Copyright (C) The Internet Society (2003). All Rights Reserved. 9 This document is an Internet-Draft and is in full conformance with 10 all provisions of Section 10 of RFC2026. 12 Internet-Drafts are working documents of the Internet Engineering 13 Task Force (IETF), its areas, and its working groups. Note that 14 other groups may also distribute working documents as Internet- 15 Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 0. Abstract 30 RFC1267 [RFC1267], "A Border Gateway Protocol 3 (BGP-3)" 31 describes a technology which is no longer commonly used. This 32 document requests that RFC 1267 be moved to historic status. 34 1. Details 36 During a review of internet standards relating to BGP, it became 37 apparent that BGP-3 as described in RFC1267, is not common 38 usage (if at all). Since this protocol has not been in use in 39 the public internet for many years (it is obsoleted by BGP-4 40 [RFC1771]), it is proposed to reclassify it to historic. 42 INTERNET-DRAFT Request to Move RFC1267 to Historic Status 2003.07.28 44 2. Security Considerations 46 Moving RFC1267 to historic has no known effect on the security of the 47 internet. 49 3. References 51 [RFC1267] K. Lougheed and Y. Rekhter, "A Border Gateway 52 Protocol 3 (BGP-3)", October, 1991. 54 [RFC1771] Y. Rekhter and T. Li (Editors) "A Border Gateway 55 Protocol 4 (BGP-4)", October, 1994. 57 4. Authors' Addresses 59 David Meyer 60 Email: dmm@maoz.com 62 5. Full Copyright Statement 64 Copyright (C) The Internet Society (2003). All Rights Reserved. 66 This document and translations of it may be copied and furnished to others, 67 and derivative works that comment on or otherwise explain it or assist in 68 its implementation may be prepared, copied, published and distributed, in 69 whole or in part, without restriction of any kind, provided that the above 70 copyright notice and this paragraph are included on all such copies and 71 derivative works. However, this document itself may not be modified in any 72 way, such as by removing the copyright notice or references to the Internet 73 Society or other Internet organizations, except as needed for the purpose of 74 developing Internet standards in which case the procedures for copyrights 75 defined in the Internet Standards process must be followed, or as required 76 to translate it into languages other than English. 78 The limited permissions granted above are perpetual and will not be revoked 79 by the Internet Society or its successors or assigns. 81 This document and the information contained herein is provided on an "AS IS" 82 basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 83 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO 84 ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 86 INTERNET-DRAFT Request to Move RFC1267 to Historic Status 2003.07.28 88 RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 89 PARTICULAR PURPOSE.