BGP-LS Advertisement of IGP Traffic Engineering Performance Metric Extensions Cisco Systems, Inc.
US ginsberg@cisco.com
Cisco Systems, Inc.
IT stefano@previdi.net
Huawei
101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China bill.wu@huawei.com
Individual
AT hannes@gredler.at
Individual
US raysaikat@gmail.com
Individual
US jefftant.ietf@gmail.com
Cisco Systems, Inc.
Brussels BE cfilsfil@cisco.com
Networking Working Group This document defines new BGP-LS TLVs in order to carry the IGP Traffic Engineering Extensions defined in IS-IS and OSPF protocols. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. In this document, these words will appear with that interpretation only when in ALL CAPS. Lower case uses of these words are not to be interpreted as carrying RFC-2119 significance.
BGP-LS () defines NLRI and attributes in order to carry link-state information. New BGP-LS Link-Attribute TLVs are required in order to carry the Traffic Engineering Metric Extensions defined in and .
The following new Link Attribute TLVs are defined:
This TLV advertises the average link delay between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 4.
This sub-TLV advertises the minimum and maximum delay values between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 8.
This sub-TLV advertises the average link delay variation between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 4.
This sub-TLV advertises the loss (as a packet percentage) between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 4.
This sub-TLV advertises the residual bandwidth between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 4.
This sub-TLV advertises the available bandwidth between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 4.
This sub-TLV advertises the bandwidth utilization between two directly connected IGP link-state neighbors. The semantic of the TLV is described in and .
Type: TBA Length: 4.
Procedures and protocol extensions defined in this document do not affect the BGP security model. See the 'Security Considerations' section of for a discussion of BGP security. Also refer to and for analysis of security issues for BGP. The TLVs introduced in this document are used to propagate IGP defined information ( and .) These TLVs represent the state and resources availability of the IGP link. The IGP instances originating these TLVs are assumed to have all the required security and authentication mechanism (as described in and ) in order to prevent any security issue when propagating the TLVs into BGP-LS.
This document requests assigning code-points from the registry "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" for the new Link Attribute TLVs defined in the table below:
TBD