rfc9104v2.txt   rfc9104.txt 
Internet Engineering Task Force (IETF) J. Tantsura Internet Engineering Task Force (IETF) J. Tantsura
Request for Comments: 9104 Microsoft Request for Comments: 9104 Microsoft
Category: Standards Track Z. Wang Category: Standards Track Z. Wang
ISSN: 2070-1721 Q. Wu ISSN: 2070-1721 Q. Wu
Huawei Huawei
K. Talaulikar K. Talaulikar
Cisco Systems Cisco Systems
July 2021 August 2021
Distribution of Traffic Engineering Extended Administrative Groups Distribution of Traffic Engineering Extended Administrative Groups
Using the Border Gateway Protocol - Link State (BGP-LS) Using the Border Gateway Protocol - Link State (BGP-LS)
Abstract Abstract
Administrative groups are link attributes used for traffic Administrative groups are link attributes used for traffic
engineering. This document defines an extension to the Border engineering. This document defines an extension to the Border
Gateway Protocol - Link State (BGP-LS) for advertisement of extended Gateway Protocol - Link State (BGP-LS) for advertisement of extended
administrative groups (EAGs). administrative groups (EAGs).
skipping to change at line 153 skipping to change at line 153
Table 1 Table 1
4. Manageability Considerations 4. 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 is distributed via [RFC7752]. existing IGP topology information that is distributed via [RFC7752].
Procedures and protocol extensions defined in this document do not Procedures and protocol extensions defined in this document do not
affect the BGP protocol operations and management other than as affect the BGP protocol operations and management other than as
discussed in Section 6 ("Manageability Considerations") of [RFC7752]. discussed in Section 6 ("Manageability Considerations") of [RFC7752].
Specifically, the malformed attribute tests for syntactic checks in Specifically, the tests for malformed attributes, to perform
Section 6.2.2 ("Fault Management") of [RFC7752] now encompass the new syntactic checks as described in Section 6.2.2 ("Fault Management")
BGP-LS Attribute TLV defined in this document. The semantic or of [RFC7752], now encompass the new BGP-LS Attribute TLV defined in
content checking for the TLV specified in this document and its this document. The semantic or content checking for the TLV
association with the BGP-LS Network Layer Reachability Information specified in this document and its association with the BGP-LS
(NLRI) types or its BGP-LS Attribute are left to the consumer of the Network Layer Reachability Information (NLRI) types or its BGP-LS
BGP-LS information (e.g., an application or a controller) and not to Attribute are left to the consumer of the BGP-LS information (e.g.,
BGP itself. an application or a controller) and not to BGP itself.
A consumer of the BGP-LS information retrieves this information over A consumer of the BGP-LS information retrieves this information over
a BGP-LS session (refer to Sections 1 and 2 of [RFC7752]). a BGP-LS session (refer to Sections 1 and 2 of [RFC7752]).
5. Security Considerations 5. Security Considerations
The procedures and protocol extensions defined in this document do The procedures and protocol extensions defined in this document do
not affect the BGP security model. See the "Security Considerations" not affect the BGP security model. See the "Security Considerations"
section of [RFC4271] for a discussion of BGP security. This document section of [RFC4271] for a discussion of BGP security. This document
only introduces a new Attribute TLV, and any syntactic error in it only introduces a new Attribute TLV, and any syntactic error in it
 End of changes. 2 change blocks. 
9 lines changed or deleted 9 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/