| < draft-ietf-idr-bgp-ls-sbfd-extensions-08.txt | draft-ietf-idr-bgp-ls-sbfd-extensions-09.txt > | |||
|---|---|---|---|---|
| Inter-Domain Routing Z. Li | Inter-Domain Routing Z. Li | |||
| Internet-Draft S. Zhuang | Internet-Draft S. Zhuang | |||
| Intended status: Standards Track Huawei | Intended status: Standards Track Huawei | |||
| Expires: October 30, 2022 K. Talaulikar, Ed. | Expires: November 5, 2022 K. Talaulikar, Ed. | |||
| Arrcus Inc | Arrcus Inc | |||
| S. Aldrin | S. Aldrin | |||
| Google, Inc | Google, Inc | |||
| J. Tantsura | J. Tantsura | |||
| Microsoft | Microsoft | |||
| G. Mirsky | G. Mirsky | |||
| Ericsson | Ericsson | |||
| April 28, 2022 | May 4, 2022 | |||
| BGP Link-State Extensions for Seamless BFD | BGP Link-State Extensions for Seamless BFD | |||
| draft-ietf-idr-bgp-ls-sbfd-extensions-08 | draft-ietf-idr-bgp-ls-sbfd-extensions-09 | |||
| Abstract | Abstract | |||
| Seamless Bidirectional Forwarding Detection (S-BFD) defines a | Seamless Bidirectional Forwarding Detection (S-BFD) defines a | |||
| simplified mechanism to use Bidirectional Forwarding Detection (BFD) | simplified mechanism to use Bidirectional Forwarding Detection (BFD) | |||
| with large portions of negotiation aspects eliminated, thus providing | with large portions of negotiation aspects eliminated, thus providing | |||
| benefits such as quick provisioning as well as improved control and | benefits such as quick provisioning as well as improved control and | |||
| flexibility to network nodes initiating the path monitoring. The | flexibility to network nodes initiating the path monitoring. The | |||
| link-state routing protocols (IS-IS and OSPF) have been extended to | link-state routing protocols (IS-IS and OSPF) have been extended to | |||
| advertise the Seamless BFD (S-BFD) Discriminators. | advertise the Seamless BFD (S-BFD) Discriminators. | |||
| skipping to change at page 1, line 47 ¶ | skipping to change at page 1, line 47 ¶ | |||
| 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 October 30, 2022. | This Internet-Draft will expire on November 5, 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2022 IETF Trust and the persons identified as the | Copyright (c) 2022 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 | |||
| skipping to change at page 2, line 29 ¶ | skipping to change at page 2, line 29 ¶ | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 | |||
| 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. BGP-LS Extensions for S-BFD Discriminator . . . . . . . . . . 3 | 3. BGP-LS Extensions for S-BFD Discriminator . . . . . . . . . . 3 | |||
| 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 | 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 5. Manageability Considerations . . . . . . . . . . . . . . . . 5 | 5. Manageability Considerations . . . . . . . . . . . . . . . . 5 | |||
| 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | |||
| 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 | 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . 6 | 8.2. Informative References . . . . . . . . . . . . . . . . . 6 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 1. Introduction | 1. Introduction | |||
| Seamless Bidirectional Forwarding Detection (S-BFD) [RFC7880] defines | Seamless Bidirectional Forwarding Detection (S-BFD) [RFC7880] defines | |||
| a simplified mechanism to use Bidirectional Forwarding Detection | a simplified mechanism to use Bidirectional Forwarding Detection | |||
| (BFD) [RFC5880] with large portions of negotiation aspects | (BFD) [RFC5880] with large portions of negotiation aspects | |||
| skipping to change at page 3, line 31 ¶ | skipping to change at page 3, line 31 ¶ | |||
| "OPTIONAL" in this document are to be interpreted as described in BCP | "OPTIONAL" in this document are to be interpreted as described in BCP | |||
| 14 [RFC2119] [RFC8174] when, and only when, they appear in all | 14 [RFC2119] [RFC8174] when, and only when, they appear in all | |||
| capitals, as shown here. | capitals, as shown here. | |||
| 2. Terminology | 2. Terminology | |||
| This memo makes use of the terms defined in [RFC7880]. | This memo makes use of the terms defined in [RFC7880]. | |||
| 3. BGP-LS Extensions for S-BFD Discriminator | 3. BGP-LS Extensions for S-BFD Discriminator | |||
| BGP-LS [RFC7752] specifies the Node NLRI for the advertisement of | BGP-LS [RFC7752] specifies the Node Network Layer Reachability | |||
| nodes and their attributes using the BGP-LS Attribute. The S-BFD | Information (NLRI) for the advertisement of nodes and their | |||
| discriminators of a node are considered a node-level attribute and | attributes using the BGP-LS Attribute. The S-BFD discriminators of a | |||
| advertised as such. | node are considered a node-level attribute and advertised as such. | |||
| This document defines a new BGP-LS Attribute TLV called the S-BFD | This document defines a new BGP-LS Attribute TLV called the S-BFD | |||
| Discriminators TLV and its format is as follows: | Discriminators TLV and its format is as follows: | |||
| 0 1 2 3 | 0 1 2 3 | |||
| 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Type | Length | | | Type | Length | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Discriminator 1 | | | Discriminator 1 | | |||
| skipping to change at page 4, line 23 ¶ | skipping to change at page 4, line 23 ¶ | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | ... | | | ... | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Discriminator n (Optional) | | | Discriminator n (Optional) | | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Figure 1: S-BFD Discriminators TLV | Figure 1: S-BFD Discriminators TLV | |||
| where: | where: | |||
| o Type: 1032 (early allocation by IANA) | o Type: 1032 | |||
| o Length: variable. It MUST be a minimum of 4 octets and increments | o Length: variable. It MUST be a minimum of 4 octets and increments | |||
| of 4 octets for each additional discriminator. | by 4 octets for each additional discriminator. | |||
| o Discriminator n: 4 octets each, carrying an S-BFD local | o Discriminator n: 4 octets each, carrying an S-BFD local | |||
| discriminator value of the node. At least one discriminator MUST | discriminator value of the node. At least one discriminator MUST | |||
| be included in the TLV. | be included in the TLV. | |||
| The S-BFD Discriminators TLV can be added to the BGP-LS Attribute | The S-BFD Discriminators TLV can be added to the BGP-LS Attribute | |||
| associated with the Node NLRI that originates the corresponding | associated with the Node NLRI that originates the corresponding | |||
| underlying IGP TLV/sub-TLV as described below. This information is | underlying IGP TLV/sub-TLV as described below. This information is | |||
| derived from the protocol specific advertisements as follows: | derived from the protocol specific advertisements as follows: | |||
| skipping to change at page 5, line 36 ¶ | skipping to change at page 5, line 36 ¶ | |||
| The new protocol extensions introduced in this document augment the | The new protocol extensions introduced in this document augment the | |||
| existing IGP topology information that can be distributed via BGP-LS | existing IGP topology information that can be distributed via BGP-LS | |||
| [RFC7752]. Procedures and protocol extensions defined in this | [RFC7752]. Procedures and protocol extensions defined in this | |||
| document do not affect the BGP security model other than as discussed | document do not affect the BGP security model other than as discussed | |||
| in the Security Considerations section of [RFC7752]. More | in the Security Considerations section of [RFC7752]. More | |||
| specifically, the aspects related to limiting the nodes and consumers | specifically, the aspects related to limiting the nodes and consumers | |||
| with which the topology information is shared via BGP-LS to trusted | with which the topology information is shared via BGP-LS to trusted | |||
| entities within an administrative domain. | entities within an administrative domain. | |||
| The TLV introduced in this document is used to propagate IGP defined | The TLV introduced in this document is used to propagate IGP defined | |||
| information ([RFC7883] and [RFC7883]). The TLV represents | information ([RFC7883] and [RFC7884]). The TLV represents | |||
| information used to set up S-BFD sessions. The IGP instances | information used to set up S-BFD sessions. The IGP instances | |||
| originating this information are assumed to support any required | originating this information are assumed to support any required | |||
| security and authentication mechanisms (as described in [RFC7883] and | security and authentication mechanisms (as described in [RFC7883] and | |||
| [RFC7883]) to prevent any security issues when propagating the | [RFC7884]). | |||
| information into BGP-LS. | ||||
| Advertising the S-BFD Discriminators via BGP-LS makes it possible for | Advertising the S-BFD Discriminators via BGP-LS makes it possible for | |||
| attackers to initiate S-BFD sessions using the advertised | attackers to initiate S-BFD sessions using the advertised | |||
| information. The vulnerabilities this poses and how to mitigate them | information. The vulnerabilities this poses and how to mitigate them | |||
| are discussed in [RFC7880]. | are discussed in [RFC7880]. | |||
| 7. Acknowledgements | 7. Acknowledgements | |||
| The authors would like to thank Nan Wu for his contributions to this | The authors would like to thank Nan Wu for his contributions to this | |||
| work. The authors would also like to thank Gunter Van De Velde and | work. The authors would also like to thank Gunter Van De Velde and | |||
| End of changes. 10 change blocks. | ||||
| 14 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||