idnits 2.17.1 draft-ietf-idr-bgp4-stdreport1-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == 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 Abstract section. ** The document seems to lack a Security Considerations 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. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 13, 1996) is 10202 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1264 (ref. '1') (Obsoleted by RFC 4794) == Outdated reference: A later version (-26) exists of draft-ietf-idr-bgp4-02 ** Obsolete normative reference: RFC 1657 (ref. '3') (Obsoleted by RFC 4273) ** Downref: Normative reference to an Informational RFC: RFC 1773 (ref. '5') ** Downref: Normative reference to an Informational RFC: RFC 1774 (ref. '6') ** Obsolete normative reference: RFC 1656 (ref. '7') (Obsoleted by RFC 1773) Summary: 15 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing Working Group Paul Traina 3 INTERNET DRAFT cisco Systems 4 May 13, 1996 6 BGP-4 Requirement Satisfaction Report 8 Status of this Memo 10 This memo provides information for the Internet community. It does 11 not specify an Internet standard. Distribution of this memo is 12 unlimited. 14 This document is an Internet Draft. Internet Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, 16 and its Working Groups. Note that other groups may also distribute 17 working documents as Internet Drafts. 19 Internet Drafts are draft documents valid for a maximum of six 20 months. Internet Drafts may be updated, replaced, or obsoleted by 21 other documents at any time. It is not appropriate to use Internet 22 Drafts as reference material or to cite them other than as a "working 23 draft" or "work in progress". 25 Introduction 27 The purpose of this memo is to document how the requirements for 28 advancing a routing protocol to Full Standard have been satisfied by 29 Border Gateway Protocol version 4 (BGP-4) (and create needless 30 busywork). This report provides a roadmap to all information 31 necessary to move BGP-4 to Standard. This is the first of two final 32 reports on the BGP protocol. As required by the Internet Activities 33 Board (IAB) and the Internet Engineering Steering Group (IESG), the 34 second report will present additional knowledge and understanding 35 gained in the time when the protocol was mada a Draft standard and 36 when it was submitted for Standard. 38 The remaining sections of this memo document how BGP satisfies 39 General Requirements specified in Section 3.0, as well as 40 Requirements for Standard specified in Section 6.0 of the "Internet 41 Routing Protocol Standardization Criteria" document [1]. 43 Please send comments to bgp@ans.net. 45 Documentation 47 BGP is an inter-autonomous system routing protocol designed for 48 TCP/IP internets. 50 Version 4 of the BGP protocol (BGP-4) specification has been 51 submitted as [2]. 53 The MIB specification for BGP-4 has been submitted as [3]. 55 The applicability document for BGP-4 has been submitted as [4]. 57 Implementation experience, operational experience, compatibility, 58 migration and testing issues are documented in [5], [6], and [7]. 60 Implementations 62 There are multiple independantly written interoperable 63 implementations of BGP-4 currently available. This section gives a 64 brief overview of the implementations that are currently used in the 65 operational Internet. They are: 67 - cisco Systems, Inc. 68 - gated consortium 69 - 3COM 70 - Bay Networks (Wellfleet) 71 - Proteon 72 - Rainbow-Bridge 73 - Telebit (DK) 75 Acknowledgments 77 The BGP protocol has been developed by the IDR (formerly BGP) Working 78 Group of the Internet Engineering Task Force. The group would like 79 to express deepest thanks to Yakov Rekhter and Sue Hares, co-chairs 80 of the IDR working group. I'd also like to explicitly thank Yakov 81 Rekhter for the review of this document as well as constructive and 82 valuable comments. 84 This report is in part based on the initial work of Peter Lothberg 85 (Ebone), Andrew Partan (Alternet), Sean Doran (Sprint), Tony Bates 86 (MCI), and several others. Details of their work were presented at 87 the Twenti-fifth and Twenti-seventh IETF meetings and are available 88 from the IETF proceedings. 90 Author's Address: 92 Paul Traina 93 cisco Systems, Inc. 94 170 W. Tasman Dr. 95 San Jose, CA 95134 96 pst@cisco.com 98 References 100 [1] RFC1264 101 Hinden, R., "Internet Routing Protocol Standardization Criteria", 102 October 1991. 104 [2] draft-ietf-idr-bgp4-02.txt 105 Rekhter, Y., and Li, T., "A Border Gateway Protocol 4 (BGP-4)", 106 January 1996. 108 [3] RFC1657 109 S. Willis, J. Burruss, J. Chu, "Definitions of Managed Objects for 110 the Fourth Version of the Border Gateway Protocol (BGP-4) using 111 SMIv2", July 1994. 113 [4] RFC1772 114 Rekhter, Y., and P. Gross, Editors, "Application of the Border 115 Gateway Protocol in the Internet", March 1995. 117 [5] RFC1773 118 Traina P., "Experience with the BGP-4 protocol", March 1995. 120 [6] RFC1774 121 Traina P., "BGP-4 Protocol Analysis", March 1995. 123 [7] RFC1656 124 Traina P., "BGP-4 Implementation Expereience", July 1994.