idnits 2.17.1 draft-ietf-idr-deprecate-30-31-129-01.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 17, 2016) is 2680 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) == Outdated reference: A later version (-12) exists of draft-ietf-idr-large-community-08 == Outdated reference: A later version (-20) exists of draft-leiba-cotton-iana-5226bis-18 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR J. Snijders 3 Internet-Draft NTT 4 Intended status: Standards Track December 17, 2016 5 Expires: June 20, 2017 7 Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and 234 8 draft-ietf-idr-deprecate-30-31-129-01 10 Abstract 12 This document requests IANA to mark BGP path attribute values 30, 31, 13 129, 241, 242, and 243 as "deprecated". 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on June 20, 2017. 32 Copyright Notice 34 Copyright (c) 2016 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 51 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 52 4. Informative References . . . . . . . . . . . . . . . . . . . 3 53 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3 54 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1. Introduction 58 It has been discovered that certain BGP Path Attribute values have 59 been used in BGP implementations which have been deployed in the wild 60 while not being assigned by the IANA for such usage. Unregistered 61 usage of BGP Path Attribute values can lead to deployment problems 62 for new technologies. 64 The use of these unregistered values was noticed when BGP Large 65 Communities attribute [I-D.ietf-idr-large-community] was initially 66 assigned value 30 by IANA. It was subsequently discovered that a 67 widely-deployed BGP-4 [RFC4271] implementation had released code 68 which used path attribute 30 and which applied a "Treat-as-withdraw" 69 [RFC7606] strategy to routes containing a valid Large Community 70 attribute, since it was expecting a different data structure. 71 Because these routes were dropped, early adopters of Large 72 Communities were unreachable from parts of the Internet. As a 73 workaround, a new Early IANA Allocation was requested. 75 The squatting of values 30, 31, 129, 241, 242 and 243 has been 76 confirmed by the involved vendors or through source code review. 78 2. IANA Considerations 80 Per this document, IANA is requested to mark values 30, 31, 129, 241, 81 242, and 243 as "deprecated" in the "BGP Path Attributes" registry 82 under the "Border Gateway Protocol (BGP) Parameters" group. The 83 marking "deprecated" meaning "use is not recommended" 84 ([I-D.leiba-cotton-iana-5226bis]). 86 3. Security Considerations 88 There are no meaningful security consequences arising from this 89 registry update. 91 4. Informative References 93 [I-D.ietf-idr-large-community] 94 Heitz, J., Snijders, J., Patel, K., Bagdonas, I., and N. 95 Hilliard, "BGP Large Communities", draft-ietf-idr-large- 96 community-08 (work in progress), November 2016. 98 [I-D.leiba-cotton-iana-5226bis] 99 Cotton, M., Leiba, B., and T. Narten, "Guidelines for 100 Writing an IANA Considerations Section in RFCs", draft- 101 leiba-cotton-iana-5226bis-18 (work in progress), September 102 2016. 104 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 105 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 106 DOI 10.17487/RFC4271, January 2006, 107 . 109 [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. 110 Patel, "Revised Error Handling for BGP UPDATE Messages", 111 RFC 7606, DOI 10.17487/RFC7606, August 2015, 112 . 114 Appendix A. Acknowledgements 116 The author would like to gratefully acknowledge Marlien Vijfhuizen 117 who helped discover the squatting of value 30, and Nick Hilliard for 118 editorial feedback. 120 Author's Address 122 Job Snijders 123 NTT Communications 124 Theodorus Majofskistraat 100 125 Amsterdam 1065 SZ 126 NL 128 Email: job@ntt.net