draft-ietf-idr-deprecate-30-31-129-00.txt   draft-ietf-idr-deprecate-30-31-129-01.txt 
IDR J. Snijders IDR J. Snijders
Internet-Draft NTT Internet-Draft NTT
Intended status: Standards Track November 14, 2016 Intended status: Standards Track December 17, 2016
Expires: May 18, 2017 Expires: June 20, 2017
Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and 234 Deprecation of BGP Path Attribute values 30, 31, 129, 241, 242, and 234
draft-ietf-idr-deprecate-30-31-129-00 draft-ietf-idr-deprecate-30-31-129-01
Abstract Abstract
This document requests IANA to mark BGP path attribute values 30, 31, This document requests IANA to mark BGP path attribute values 30, 31,
129, 241, 242, and 243 as "deprecated". 129, 241, 242, and 243 as "deprecated".
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 18, 2017. This Internet-Draft will expire on June 20, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 10 skipping to change at page 2, line 10
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2
4. Informative References . . . . . . . . . . . . . . . . . . . 2 4. Informative References . . . . . . . . . . . . . . . . . . . 3
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction 1. Introduction
It has been discovered that certain BGP Path Attribute values have It has been discovered that certain BGP Path Attribute values have
been used in BGP implementations which have been deployed in the wild been used in BGP implementations which have been deployed in the wild
while not being assigned by the IANA for such usage. This has led to while not being assigned by the IANA for such usage. Unregistered
deployment problems for new technologies such as Large BGP usage of BGP Path Attribute values can lead to deployment problems
Communities [I-D.ietf-idr-large-community]. for new technologies.
The use of these unregistered values was noticed when BGP Large
Communities attribute [I-D.ietf-idr-large-community] was initially
assigned value 30 by IANA. It was subsequently discovered that a
widely-deployed BGP-4 [RFC4271] implementation had released code
which used path attribute 30 and which applied a "Treat-as-withdraw"
[RFC7606] strategy to routes containing a valid Large Community
attribute, since it was expecting a different data structure.
Because these routes were dropped, early adopters of Large
Communities were unreachable from parts of the Internet. As a
workaround, a new Early IANA Allocation was requested.
The squatting of values 30, 31, 129, 241, 242 and 243 has been The squatting of values 30, 31, 129, 241, 242 and 243 has been
confirmed by the involved vendors or through source code review. confirmed by the involved vendors or through source code review.
2. IANA Considerations 2. IANA Considerations
Per this document, IANA is requested to mark values 30, 31, 129, 241, Per this document, IANA is requested to mark values 30, 31, 129, 241,
242, and 243 as "deprecated" in the "BGP Path Attributes" registry 242, and 243 as "deprecated" in the "BGP Path Attributes" registry
under the "Border Gateway Protocol (BGP) Parameters" group. The under the "Border Gateway Protocol (BGP) Parameters" group. The
marking "deprecated" meaning "use is not recommended" marking "deprecated" meaning "use is not recommended"
([I-D.leiba-cotton-iana-5226bis]). ([I-D.leiba-cotton-iana-5226bis]).
3. Security Considerations 3. Security Considerations
There are no meaningful security consequences arising from this There are no meaningful security consequences arising from this
registry update. registry update.
4. Informative References 4. Informative References
[I-D.ietf-idr-large-community] [I-D.ietf-idr-large-community]
Heitz, J., Snijders, J., Patel, K., Bagdonas, I., Simpson, Heitz, J., Snijders, J., Patel, K., Bagdonas, I., and N.
A., and N. Hilliard, "Large BGP Communities", draft-ietf- Hilliard, "BGP Large Communities", draft-ietf-idr-large-
idr-large-community-05 (work in progress), October 2016. community-08 (work in progress), November 2016.
[I-D.leiba-cotton-iana-5226bis] [I-D.leiba-cotton-iana-5226bis]
Cotton, M., Leiba, B., and T. Narten, "Guidelines for Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", draft- Writing an IANA Considerations Section in RFCs", draft-
leiba-cotton-iana-5226bis-18 (work in progress), September leiba-cotton-iana-5226bis-18 (work in progress), September
2016. 2016.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<http://www.rfc-editor.org/info/rfc4271>.
[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
Patel, "Revised Error Handling for BGP UPDATE Messages",
RFC 7606, DOI 10.17487/RFC7606, August 2015,
<http://www.rfc-editor.org/info/rfc7606>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The author would like to gratefully acknowledge Marlien Vijfhuizen The author would like to gratefully acknowledge Marlien Vijfhuizen
who helped discover the squatting of value 30. who helped discover the squatting of value 30, and Nick Hilliard for
editorial feedback.
Author's Address Author's Address
Job Snijders Job Snijders
NTT Communications NTT Communications
Theodorus Majofskistraat 100 Theodorus Majofskistraat 100
Amsterdam 1065 SZ Amsterdam 1065 SZ
NL NL
Email: job@ntt.net Email: job@ntt.net
 End of changes. 8 change blocks. 
12 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/