| draft-ietf-idr-next-hop-capability-04.txt | draft-ietf-idr-next-hop-capability-05.txt | |||
|---|---|---|---|---|
| Network Working Group B. Decraene | Network Working Group B. Decraene | |||
| Internet-Draft Orange | Internet-Draft Orange | |||
| Updates: 6790 (if approved) K. Kompella | Updates: 6790 (if approved) K. Kompella | |||
| Intended status: Standards Track Juniper Networks, Inc. | Intended status: Standards Track Juniper Networks, Inc. | |||
| Expires: June 20, 2019 W. Henderickx | Expires: December 13, 2019 W. Henderickx | |||
| Nokia | Nokia | |||
| December 17, 2018 | June 11, 2019 | |||
| BGP Next-Hop dependent capabilities | BGP Next-Hop dependent capabilities | |||
| draft-ietf-idr-next-hop-capability-04 | draft-ietf-idr-next-hop-capability-05 | |||
| Abstract | Abstract | |||
| RFC 5492 advertises the capabilities of the BGP peer. When the BGP | RFC 5492 advertises the capabilities of the BGP peer. When the BGP | |||
| peer is not the same as the BGP Next-Hop, it is useful to also be | peer is not the same as the BGP Next-Hop, it is useful to also be | |||
| able to advertise the capability of the BGP Next-Hop, in particular | able to advertise the capability of the BGP Next-Hop, in particular | |||
| to advertise forwarding plane features. This document defines a | to advertise forwarding plane features. This document defines a | |||
| mechanism to advertise such BGP Next Hop dependent Capabilities. | mechanism to advertise such BGP Next Hop dependent Capabilities. | |||
| This document defines a new BGP non-transitive attribute to carry | This document defines a new BGP non-transitive attribute to carry | |||
| skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
| capabilities of the new BGP Next-Hop. | capabilities of the new BGP Next-Hop. | |||
| This document also defines a Next-Hop capability to advertise the | This document also defines a Next-Hop capability to advertise the | |||
| ability to process the MPLS Entropy Label as an egress LSR for all | ability to process the MPLS Entropy Label as an egress LSR for all | |||
| NLRI advertised in the BGP UPDATE. It updates RFC 6790 with regard | NLRI advertised in the BGP UPDATE. It updates RFC 6790 with regard | |||
| to this BGP signaling. | to this BGP signaling. | |||
| Requirements Language | Requirements Language | |||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and | |||
| document are to be interpreted as described in RFC 2119 [RFC2119]. | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
| 14 RFC 2119 [RFC2119] RFC 8179 [RFC8174] when, and only when, they | ||||
| appear in all capitals, as shown here. | ||||
| 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. | |||
| 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 https://datatracker.ietf.org/drafts/current/. | Drafts is at https://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 June 20, 2019. | This Internet-Draft will expire on December 13, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2019 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 | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://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 | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| 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 . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2. BGP Next-Hop dependent Capabilities Attribute . . . . . . . . 3 | 2. BGP Next-Hop dependent Capabilities Attribute . . . . . . . . 3 | |||
| 2.1. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2.1. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2.2. Attribute Operation . . . . . . . . . . . . . . . . . . . 4 | 2.2. Attribute Operation . . . . . . . . . . . . . . . . . . . 4 | |||
| 2.3. Interpreting received Capability . . . . . . . . . . . . 5 | 2.3. Interpreting received Capability . . . . . . . . . . . . 5 | |||
| 2.4. Attribute Error Handling . . . . . . . . . . . . . . . . 5 | 2.4. Attribute Error Handling . . . . . . . . . . . . . . . . 5 | |||
| 2.5. Network operation considerations . . . . . . . . . . . . 6 | 2.5. Network operation considerations . . . . . . . . . . . . 6 | |||
| 3. Entropy Label Next-Hop dependent Capability . . . . . . . . . 6 | 3. Entropy Label Next-Hop dependent Capability . . . . . . . . . 6 | |||
| 3.1. Readable Label Depth . . . . . . . . . . . . . . . . . . 7 | 3.1. Readable Label Depth . . . . . . . . . . . . . . . . . . 7 | |||
| 3.2. Entropy Label Next-Hop Capability error handling . . . . 9 | 3.2. Entropy Label Next-Hop Capability error handling . . . . 9 | |||
| 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 | 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 | |||
| skipping to change at page 9, line 31 ¶ | skipping to change at page 9, line 31 ¶ | |||
| Capabilities", type Code TBD1, from the "BGP Path Attributes" | Capabilities", type Code TBD1, from the "BGP Path Attributes" | |||
| registry. | registry. | |||
| 4.2. Next-Hop Capability registry | 4.2. Next-Hop Capability registry | |||
| The IANA is requested to create and maintain a registry entitled "BGP | The IANA is requested to create and maintain a registry entitled "BGP | |||
| Next-Hop Capabilities". | Next-Hop Capabilities". | |||
| The registration policies [RFC8126] for this registry are: | The registration policies [RFC8126] for this registry are: | |||
| 1-63 IETF Review | 0 Reserved | |||
| 1-63 IETF Review | ||||
| 64-65534 First Come First Served | 64-65534 First Come First Served | |||
| 65535 Reserved | 65535 Reserved | |||
| IANA is requested to make the following initial assignments: | IANA is requested to make the following initial assignments: | |||
| Registry Name: Next-Hop Capability. | Registry Name: Next-Hop Capability. | |||
| Value Meaning Reference | Value Meaning Reference | |||
| ---------- ---------------------------------------- --------- | ---------- ---------------------------------------- --------- | |||
| 0 Reserved (not to be allocated) This document | 0 Reserved (not to be allocated) This document | |||
| skipping to change at page 11, line 30 ¶ | skipping to change at page 11, line 30 ¶ | |||
| [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. | [RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K. | |||
| Patel, "Revised Error Handling for BGP UPDATE Messages", | Patel, "Revised Error Handling for BGP UPDATE Messages", | |||
| RFC 7606, DOI 10.17487/RFC7606, August 2015, | RFC 7606, DOI 10.17487/RFC7606, August 2015, | |||
| <https://www.rfc-editor.org/info/rfc7606>. | <https://www.rfc-editor.org/info/rfc7606>. | |||
| [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for | |||
| Writing an IANA Considerations Section in RFCs", BCP 26, | Writing an IANA Considerations Section in RFCs", BCP 26, | |||
| RFC 8126, DOI 10.17487/RFC8126, June 2017, | RFC 8126, DOI 10.17487/RFC8126, June 2017, | |||
| <https://www.rfc-editor.org/info/rfc8126>. | <https://www.rfc-editor.org/info/rfc8126>. | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | ||||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | ||||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | ||||
| 7.2. Informative References | 7.2. Informative References | |||
| [I-D.ietf-mpls-spring-entropy-label] | [I-D.ietf-mpls-spring-entropy-label] | |||
| Kini, S., Kompella, K., Sivabalan, S., Litkowski, S., | Kini, S., Kompella, K., Sivabalan, S., Litkowski, S., | |||
| Shakir, R., and J. Tantsura, "Entropy label for SPRING | Shakir, R., and J. Tantsura, "Entropy label for SPRING | |||
| tunnels", draft-ietf-mpls-spring-entropy-label-12 (work in | tunnels", draft-ietf-mpls-spring-entropy-label-12 (work in | |||
| progress), July 2018. | progress), July 2018. | |||
| [RFC4786] Abley, J. and K. Lindqvist, "Operation of Anycast | [RFC4786] Abley, J. and K. Lindqvist, "Operation of Anycast | |||
| Services", BCP 126, RFC 4786, DOI 10.17487/RFC4786, | Services", BCP 126, RFC 4786, DOI 10.17487/RFC4786, | |||
| skipping to change at page 12, line 26 ¶ | skipping to change at page 12, line 31 ¶ | |||
| o Enhanced Security consideration (capability advertised to external | o Enhanced Security consideration (capability advertised to external | |||
| ASes). | ASes). | |||
| o Editorial changes and typo corrections. | o Editorial changes and typo corrections. | |||
| Changes -02: No change. Refresh only. | Changes -02: No change. Refresh only. | |||
| Changes -03: Addition of the optional Readable Label Depth. | Changes -03: Addition of the optional Readable Label Depth. | |||
| Changes -04: No change. Refresh only. | Changes -04: Update to security section, following discussion on the | |||
| IDR mailing list. | ||||
| Changes -05: No change. Refresh only. | ||||
| Authors' Addresses | Authors' Addresses | |||
| Bruno Decraene | Bruno Decraene | |||
| Orange | Orange | |||
| Email: bruno.decraene@orange.com | Email: bruno.decraene@orange.com | |||
| Kireeti Kompella | Kireeti Kompella | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| End of changes. 10 change blocks. | ||||
| 10 lines changed or deleted | 20 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||