< draft-ietf-idr-bgp-ls-sbfd-extensions-07.txt   draft-ietf-idr-bgp-ls-sbfd-extensions-08.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 13, 2022 K. Talaulikar, Ed. Expires: October 30, 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 11, 2022 April 28, 2022
BGP Link-State Extensions for Seamless BFD BGP Link-State Extensions for Seamless BFD
draft-ietf-idr-bgp-ls-sbfd-extensions-07 draft-ietf-idr-bgp-ls-sbfd-extensions-08
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 13, 2022. This Internet-Draft will expire on October 30, 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 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
The BGP-LS [RFC7752] specifies the Node NLRI for the advertisement of BGP-LS [RFC7752] specifies the Node NLRI for the advertisement of
nodes and their attributes using the BGP-LS Attribute. The S-BFD nodes and their attributes using the BGP-LS Attribute. The S-BFD
discriminators of a node are considered a node-level attribute and discriminators of a node are considered a node-level attribute and
advertised as such. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 5 skipping to change at page 5, line 5
o OSPFv2/OSPFv3, as defined by the S-BFD Discriminator TLV in o OSPFv2/OSPFv3, as defined by the S-BFD Discriminator TLV in
[RFC7884]. [RFC7884].
4. IANA Considerations 4. IANA Considerations
IANA is requested to permanently allocate the following code-point IANA is requested to permanently allocate the following code-point
from the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, from the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor,
and Attribute TLVs" registry. The column "IS-IS TLV/Sub-TLV" defined and Attribute TLVs" registry. The column "IS-IS TLV/Sub-TLV" defined
in the registry does not require any value and should be left empty. in the registry does not require any value and should be left empty.
+---------------+--------------------------+----------+ +------------+--------------------------+---------------+
| Code Point | Description | Length | | Code Point | Description | Reference |
+---------------+--------------------------+----------+ +------------+--------------------------+---------------+
| 1032 | S-BFD Discriminators TLV | variable | | 1032 | S-BFD Discriminators TLV | This document |
+---------------+--------------------------+----------+ +---------------+--------------------------+------------+
Table 1: S-BFD Discriminators TLV Code-Point Allocation Table 1: S-BFD Discriminators TLV Code-Point Allocation
5. Manageability Considerations 5. Manageability Considerations
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 was distributed via [RFC7752]. existing IGP topology information that was distributed via BGP-LS
Procedures and protocol extensions defined in this document do not [RFC7752]. Procedures and protocol extensions defined in this
affect the BGP protocol operations and management other than as document do not affect the BGP protocol operations and management
discussed in the Manageability Considerations section of [RFC7752]. other than as discussed in the Manageability Considerations section
Specifically, the malformed NLRIs attribute tests in the Fault of [RFC7752]. Specifically, the malformed NLRIs attribute tests in
Management section of [RFC7752] now encompasses the new TLV for the the Fault Management section of [RFC7752] now encompass the new TLV
BGP-LS NLRI in this document. for the BGP-LS NLRI in this document.
6. Security Considerations 6. Security Considerations
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 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 [RFC7883]). 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
skipping to change at page 6, line 8 skipping to change at page 6, line 8
information into BGP-LS. 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 and Gunter Van De Velde for his review. The authors would also work. The authors would also like to thank Gunter Van De Velde and
like to thank Jeff Haas for his shepherd review and Alvaro Retana for Thomas Fossati for their reviews. The authors would also like to
his AD review of this document. thank Jeff Haas for his shepherd review and Alvaro Retana for his AD
review of this document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
 End of changes. 9 change blocks. 
21 lines changed or deleted 22 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/