idnits 2.17.1 draft-scudder-idr-open-registry-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 16, 2008) is 5610 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3392 (Obsoleted by RFC 5492) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Scudder 3 Internet-Draft Juniper Networks 4 Intended status: Informational December 16, 2008 5 Expires: June 19, 2009 7 Registry for BGP-4 OPEN Options 8 draft-scudder-idr-open-registry-00 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on June 19, 2009. 33 Copyright Notice 35 Copyright (c) 2008 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. 45 Abstract 47 The base BGP specification specifies a mechanism to include optional 48 parameters with the OPEN message. Optional parameters are identified 49 by a type code. However, no IANA registry exists for this type code. 50 This document requests IANA to create such a registry. 52 1. Introduction 54 The base BGP specification [RFC4271] specifies in Section 4.2 a 55 mechanism to include optional parameters with the OPEN message. 56 Optional parameters are identified by the Parameter Type, which is a 57 one-octet unsigned binary integer. 59 Two Parameter Type codes are currently defined: 61 o Parameter Type 1: Authentication (deprecated). 63 o Parameter Type 2: Capabilities ([RFC3392]) 65 This document requests that IANA create and maintain a registry for 66 OPEN message optional parameters. 68 2. Acknowledgements 70 Elwyn Davies pointed out that a registry for OPEN Options was needed. 72 3. IANA Considerations 74 This document requests that IANA create and maintain a registry for 75 "BGP OPEN Optional Parameter Type", as discussed above. Values are 76 to be allocated according to the "IETF Consensus" policy as defined 77 in [RFC5226]. 79 4. Security Considerations 81 This document introduces no security issues. 83 5. Normative References 85 [RFC3392] Chandra, R. and J. Scudder, "Capabilities Advertisement 86 with BGP-4", RFC 3392, November 2002. 88 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 89 Protocol 4 (BGP-4)", RFC 4271, January 2006. 91 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 92 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 93 May 2008. 95 Author's Address 97 John Scudder 98 Juniper Networks 99 1194 N. Mathilda Ave 100 Sunnyvale, CA 94089 101 USA 103 Email: jgs@juniper.net