draft-ietf-idr-bgpls-segment-routing-epe-09.txt   draft-ietf-idr-bgpls-segment-routing-epe-10.txt 
Network Working Group S. Previdi, Ed. Network Working Group S. Previdi, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: August 20, 2017 K. Patel Expires: September 10, 2017 K. Patel
Arrcus, Inc. Arrcus, Inc.
S. Ray S. Ray
Individual Contributor Individual Contributor
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
February 16, 2017 March 9, 2017
Segment Routing BGP Egress Peer Engineering BGP-LS Extensions Segment Routing BGP Egress Peer Engineering BGP-LS Extensions
draft-ietf-idr-bgpls-segment-routing-epe-09 draft-ietf-idr-bgpls-segment-routing-epe-10
Abstract Abstract
Segment Routing (SR) leverages source routing. A node steers a Segment Routing (SR) leverages source routing. A node steers a
packet through a controlled set of instructions, called segments, by packet through a controlled set of instructions, called segments, by
prepending the packet with an SR header. A segment can represent any prepending the packet with an SR header. A segment can represent any
instruction, topological or service-based. SR allows to enforce a instruction, topological or service-based. SR allows to enforce a
flow through any topological path and service chain while maintaining flow through any topological path and service chain while maintaining
per-flow state only at the ingress node of the SR domain. per-flow state only at the ingress node of the SR domain.
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 August 20, 2017. This Internet-Draft will expire on September 10, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 7 skipping to change at page 3, line 7
6.3. Peer Node Segment for Node H . . . . . . . . . . . . . . 14 6.3. Peer Node Segment for Node H . . . . . . . . . . . . . . 14
6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14 6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14
6.5. Peer Adjacency Segment for Node E, Link 1 . . . . . . . . 15 6.5. Peer Adjacency Segment for Node E, Link 1 . . . . . . . . 15
6.6. Peer Adjacency Segment for Node E, Link 2 . . . . . . . . 15 6.6. Peer Adjacency Segment for Node E, Link 2 . . . . . . . . 15
7. Implementation Status . . . . . . . . . . . . . . . . . . . . 16 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
8.1. New BGP-LS Protocol-ID . . . . . . . . . . . . . . . . . 17 8.1. New BGP-LS Protocol-ID . . . . . . . . . . . . . . . . . 17
8.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 17 8.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 17
9. Manageability Considerations . . . . . . . . . . . . . . . . 18 9. Manageability Considerations . . . . . . . . . . . . . . . . 18
10. Security Considerations . . . . . . . . . . . . . . . . . . . 18 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
13.1. Normative References . . . . . . . . . . . . . . . . . . 19 13.1. Normative References . . . . . . . . . . . . . . . . . . 19
13.2. Informative References . . . . . . . . . . . . . . . . . 19 13.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
Segment Routing (SR) leverages source routing. A node steers a Segment Routing (SR) leverages source routing. A node steers a
packet through a controlled set of instructions, called segments, by packet through a controlled set of instructions, called segments, by
prepending the packet with an SR header. A segment can represent any prepending the packet with an SR header. A segment can represent any
skipping to change at page 5, line 10 skipping to change at page 5, line 10
While an egress point topology usually refers to eBGP sessions While an egress point topology usually refers to eBGP sessions
between external peers, there's nothing in the extensions defined in between external peers, there's nothing in the extensions defined in
this document that would prevent the use of these extensions in the this document that would prevent the use of these extensions in the
context of iBGP sessions. context of iBGP sessions.
4. Link NLRI for BGP-EPE Connectivity Description 4. Link NLRI for BGP-EPE Connectivity Description
This section describes the NLRI used for describing the connectivity This section describes the NLRI used for describing the connectivity
of the BGP Egress router. The connectivity is based on links and of the BGP Egress router. The connectivity is based on links and
remote peers/ASs and therefore the existing Link-Type NLRI (defined remote peers/ASs and therefore the existing Link-Type NLRI (defined
in [RFC7752]) is used. A new Protocol ID is used: BGP (codepoint to in [RFC7752]) is used. A new Protocol-ID is used: BGP (codepoint 7
be assigned by IANA). assigned by IANA (Section 8) from the registry "BGP-LS Protocol-
IDs").
The use of a new Protocol-ID allows separation and differentiation The use of a new Protocol-ID allows separation and differentiation
between the NLRIs carrying BGP-EPE descriptors from the NLRIs between the NLRIs carrying BGP-EPE descriptors from the NLRIs
carrying IGP link-state information as defined in [RFC7752]. The carrying IGP link-state information as defined in [RFC7752]. The
Link NLRI Type uses descriptors and attributes already defined in Link NLRI Type uses descriptors and attributes already defined in
[RFC7752] in addition to new TLVs defined in the following sections [RFC7752] in addition to new TLVs defined in the following sections
of this document. of this document.
The extensions defined in this document apply to both internal and The extensions defined in this document apply to both internal and
external BGP-LS EPE advertisements. external BGP-LS EPE advertisements.
skipping to change at page 5, line 48 skipping to change at page 5, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Node Descriptors and Link Descriptors are defined in [RFC7752]. Node Descriptors and Link Descriptors are defined in [RFC7752].
4.1. BGP Router ID and Member ASN 4.1. BGP Router ID and Member ASN
Two new Node Descriptors Sub-TLVs are defined in this document: Two new Node Descriptors Sub-TLVs are defined in this document:
o BGP Router Identifier (BGP Router-ID): o BGP Router Identifier (BGP Router-ID):
Type: TBD2 (to be assigned by IANA from the registry "BGP-LS Type: 516 (assigned by IANA (Section 8) from the registry "BGP-
Node Descriptor, Link Descriptor, Prefix Descriptor, and LS Node Descriptor, Link Descriptor, Prefix Descriptor, and
Attribute TLVs"). Attribute TLVs").
Length: 4 octets Length: 4 octets
Value: 4 octet unsigned integer representing the BGP Identifier Value: 4 octet unsigned integer representing the BGP Identifier
as defined in [RFC4271] and [RFC6286]. as defined in [RFC4271] and [RFC6286].
o Confederation Member ASN (Member-ASN) o Confederation Member ASN (Member-ASN)
Type: TBD3 (to be assigned by IANA from the registry "BGP-LS Type: 517 (assigned by IANA (Section 8) from the registry "BGP-
Node Descriptor, Link Descriptor, Prefix Descriptor, and LS Node Descriptor, Link Descriptor, Prefix Descriptor, and
Attribute TLVs"). Attribute TLVs").
Length: 4 octets Length: 4 octets
Value: 4 octet unsigned integer representing the Member ASN Value: 4 octet unsigned integer representing the Member ASN
inside the Confederation.[RFC5065]. inside the Confederation.[RFC5065].
4.2. BGP-EPE Node Descriptors 4.2. BGP-EPE Node Descriptors
The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI
as Local Node Descriptors: as Local Node Descriptors:
o BGP Router ID, which contains the BGP Identifier of the local BGP- o BGP Router-ID, which contains the BGP Identifier of the local BGP-
EPE capable node. EPE capable node.
o Autonomous System Number, which contains the local ASN or local o Autonomous System Number, which contains the local ASN or local
confederation identifier (ASN) if confederations are used. confederation identifier (ASN) if confederations are used.
o BGP-LS Identifier. o BGP-LS Identifier.
It has to be noted that [RFC6286] (section 2.1) requires the BGP It has to be noted that [RFC6286] (section 2.1) requires the BGP
identifier (router-id) to be unique within an Autonomous System. identifier (router-id) to be unique within an Autonomous System.
Therefore, the <ASN, BGP identifier> tuple is globally unique. Therefore, the <ASN, BGP identifier> tuple is globally unique.
skipping to change at page 6, line 46 skipping to change at page 6, line 49
as Local Node Descriptors: as Local Node Descriptors:
o Member-ASN, which contains the ASN of the confederation member o Member-ASN, which contains the ASN of the confederation member
(when BGP confederations are used). (when BGP confederations are used).
o Node Descriptors as defined in [RFC7752]. o Node Descriptors as defined in [RFC7752].
The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI
as Remote Node Descriptors: as Remote Node Descriptors:
o BGP Router ID, which contains the BGP Identifier of the peer node. o BGP Router-ID, which contains the BGP Identifier of the peer node.
o Autonomous System Number, which contains the peer ASN or the peer o Autonomous System Number, which contains the peer ASN or the peer
confederation identifier (ASN), if confederations are used. confederation identifier (ASN), if confederations are used.
The following Node Descriptors Sub-TLVs MAY appear in the Link NLRI The following Node Descriptors Sub-TLVs MAY appear in the Link NLRI
as Remote Node Descriptors: as Remote Node Descriptors:
o Member-ASN, which contains the ASN of the confederation member o Member-ASN, which contains the ASN of the confederation member
(when BGP confederations are used). (when BGP confederations are used).
skipping to change at page 7, line 22 skipping to change at page 7, line 22
4.3. Link Attributes 4.3. Link Attributes
The following BGP-LS Link attributes TLVs are used with the Link The following BGP-LS Link attributes TLVs are used with the Link
NLRI: NLRI:
+----------+---------------------------+----------+ +----------+---------------------------+----------+
| TLV Code | Description | Length | | TLV Code | Description | Length |
| Point | | | | Point | | |
+----------+---------------------------+----------+ +----------+---------------------------+----------+
| TBD4 | Peer Node Segment | variable | | 1101 | Peer Node Segment | variable |
| | Identifier (Peer-Node-SID)| | | | Identifier (Peer-Node-SID)| |
| TBD5 | Peer Adjacency Segment | variable | | 1102 | Peer Adjacency Segment | variable |
| | Identifier (Peer-Adj-SID) | | | | Identifier (Peer-Adj-SID) | |
| TBD6 | Peer Set Segment | variable | | 1103 | Peer Set Segment | variable |
| | Identifier (Peer-Set-SID) | | | | Identifier (Peer-Set-SID) | |
+----------+---------------------------+----------+ +----------+---------------------------+----------+
Figure 1: BGP-LS TLV code points for BGP-EPE Figure 1: BGP-LS TLV code points for BGP-EPE
Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format
defined here below: defined here below:
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 7, line 49 skipping to change at page 7, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Weight | Reserved | | Flags | Weight | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label/Index (variable) | | SID/Label/Index (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Figure 2 Figure 2
o Type: TBD4 or TBD5 or TBD6, to be assigned by IANA. o Type: 1101 or 1102 or 1103 (assigned by IANA (Section 8) from the
registry "BGP-LS Node Descriptor, Link Descriptor, Prefix
Descriptor, and Attribute TLVs").
o Length: variable. o Length: variable.
o Flags: following flags have been defined: o Flags: following flags have been defined:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|V|L| | |V|L| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 9, line 48 skipping to change at page 9, line 50
o SR header operation: NEXT (as defined in o SR header operation: NEXT (as defined in
[I-D.ietf-spring-segment-routing]). [I-D.ietf-spring-segment-routing]).
o Next-Hop: the connected peering node to which the segment is o Next-Hop: the connected peering node to which the segment is
related. related.
The Peer Node Segment is advertised with a Link NLRI, where: The Peer Node Segment is advertised with a Link NLRI, where:
o Local Node Descriptors contains o Local Node Descriptors contains
Local BGP Router ID of the BGP-EPE enabled egress PE. Local BGP Router-ID of the BGP-EPE enabled egress PE.
Local ASN. Local ASN.
BGP-LS Identifier. BGP-LS Identifier.
o Remote Node Descriptors contains o Remote Node Descriptors contains
Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session).
Peer BGP Router-ID (i.e.: the peer BGP ID used in the BGP session).
Peer ASN. Peer ASN.
o Link Descriptors Sub-TLVs, as defined in [RFC7752], contain the o Link Descriptors Sub-TLVs, as defined in [RFC7752], contain the
addresses used by the BGP session: addresses used by the BGP session:
* IPv4 Interface Address (Sub-TLV 259) contains the BGP session * IPv4 Interface Address (Sub-TLV 259) contains the BGP session
IPv4 local address. IPv4 local address.
* IPv4 Neighbor Address (Sub-TLV 260) contains the BGP session * IPv4 Neighbor Address (Sub-TLV 260) contains the BGP session
IPv4 peer address. IPv4 peer address.
skipping to change at page 10, line 42 skipping to change at page 10, line 45
o SR header operation: NEXT (as defined in o SR header operation: NEXT (as defined in
[I-D.ietf-spring-segment-routing]). [I-D.ietf-spring-segment-routing]).
o Next-Hop: the interface peer address. o Next-Hop: the interface peer address.
The Peer Adjacency Segment is advertised with a Link NLRI, where: The Peer Adjacency Segment is advertised with a Link NLRI, where:
o Local Node Descriptors contains o Local Node Descriptors contains
Local BGP Router ID of the BGP-EPE enabled egress PE. Local BGP Router-ID of the BGP-EPE enabled egress PE.
Local ASN. Local ASN.
BGP-LS Identifier. BGP-LS Identifier.
o Remote Node Descriptors contains o Remote Node Descriptors contains
Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session). Peer BGP Router-ID (i.e.: the peer BGP ID used in the BGP session).
Peer ASN. Peer ASN.
o Link Descriptors Sub-TLVs, as defined in [RFC7752], MUST contain o Link Descriptors Sub-TLVs, as defined in [RFC7752], MUST contain
the following TLVs: the following TLVs:
* Link Local/Remote Identifiers (Sub-TLV 258) contains the * Link Local/Remote Identifiers (Sub-TLV 258) contains the
4-octet Link Local Identifier followed by the 4-octet value 0 4-octet Link Local Identifier followed by the 4-octet value 0
indicating the Link Remote Identifier in unknown [RFC5307]. indicating the Link Remote Identifier in unknown [RFC5307].
o In addition, Link Descriptors Sub-TLVs, as defined in [RFC7752], o In addition, Link Descriptors Sub-TLVs, as defined in [RFC7752],
skipping to change at page 12, line 42 skipping to change at page 12, line 42
Figure 3: Reference Diagram Figure 3: Reference Diagram
IPv4 addressing: IPv4 addressing:
o C's IPv4 address of interface to D: 1.0.1.1/24, D's interface: o C's IPv4 address of interface to D: 1.0.1.1/24, D's interface:
1.0.1.2/24 1.0.1.2/24
o C's IPv4 address of interface to H: 1.0.2.1/24, H's interface: o C's IPv4 address of interface to H: 1.0.2.1/24, H's interface:
1.0.2.2/24 1.0.2.2/24
o C's IPv4 address of upper interface to E: 1.0.3.1, E's interface: o C's IPv4 address of upper interface to E: 1.0.3.1/24, E's
1.0.3.2/24 interface: 1.0.3.2/24
o C's local identifier of upper interface to E: 0.0.0.1.0.0.0.0 o C's local identifier of upper interface to E: 0.0.0.1.0.0.0.0
o C's IPv4 address of lower interface to E: 1.0.4.1/24, E's o C's IPv4 address of lower interface to E: 1.0.4.1/24, E's
interface: 1.0.4.2/24 interface: 1.0.4.2/24
o C's local identifier of lower interface to E: 0.0.0.2.0.0.0.0 o C's local identifier of lower interface to E: 0.0.0.2.0.0.0.0
o Loopback of E used for eBGP multi-hop peering to C: 1.0.5.2/32 o Loopback of E used for eBGP multi-hop peering to C: 1.0.5.2/32
o C's loopback is 3.3.3.3/32 with SID 64 o C's loopback is 3.3.3.3/32 with SID 64
skipping to change at page 16, line 39 skipping to change at page 16, line 39
Several early implementations exist and will be reported in detail in Several early implementations exist and will be reported in detail in
a forthcoming version of this document. For purposes of early a forthcoming version of this document. For purposes of early
interoperability testing, when no FCFS code point was available, interoperability testing, when no FCFS code point was available,
implementations have made use of the following values: implementations have made use of the following values:
+---------------------------------------+ +---------------------------------------+
| Codepoint | Description | | Codepoint | Description |
+---------------------------------------+ +---------------------------------------+
| 7 | Protocol-ID BGP | | 7 | Protocol-ID BGP |
| 516 | BGP Router ID | | 516 | BGP Router-ID |
| 517 | BGP Confederation Member | | 517 | BGP Confederation Member |
| 1101 | Peer-Node-SID | | 1101 | Peer-Node-SID |
| 1102 | Peer-Adj-SID | | 1102 | Peer-Adj-SID |
| 1103 | Peer-Set-SID | | 1103 | Peer-Set-SID |
+------------+--------------------------+ +------------+--------------------------+
It will ease implementation interoperability and deployment if the IANA has now confirmed the assignment of the above coidepoints.
value could be preserved. However, when IANA-assigned values are SeeSection 8.
available, implementations will be updated to use them.
8. IANA Considerations 8. IANA Considerations
This document defines: This document defines:
A new Protocol-ID: BGP. The codepoint is from the "BGP-LS A new Protocol-ID: BGP. The codepoint is from the "BGP-LS
Protocol-IDs" registry. Protocol-IDs" registry.
Two new TLVs: BGP-Router-ID and BGP Confederation Member. The Two new TLVs: BGP-Router-ID and BGP Confederation Member. The
codepoints are in the "BGP-LS Node Descriptor, Link Descriptor, codepoints are in the "BGP-LS Node Descriptor, Link Descriptor,
skipping to change at page 17, line 25 skipping to change at page 17, line 25
Three new BGP-LS Attribute TLVs: Peer-Node-SID, Peer-Adj-SID and Three new BGP-LS Attribute TLVs: Peer-Node-SID, Peer-Adj-SID and
Peer-Set-SID. The codepoints are in the "BGP-LS Node Descriptor, Peer-Set-SID. The codepoints are in the "BGP-LS Node Descriptor,
Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry. Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry.
8.1. New BGP-LS Protocol-ID 8.1. New BGP-LS Protocol-ID
This document defines a new value in the registry "BGP-LS Protocol- This document defines a new value in the registry "BGP-LS Protocol-
IDs": IDs":
+---------------------------------------+ +----------------------------------------------+
| Codepoint | Description | | Codepoint | Description | Status |
+---------------------------------------+ +----------------------------------------------+
| TBD1 | BGP | | 7 | BGP | Assigned by IANA |
+---------------------------------------+ +----------------------------------------------+
8.2. Node Descriptors and Link Attribute TLVs 8.2. Node Descriptors and Link Attribute TLVs
This document defines 5 new TLVs in the registry "BGP-LS Node This document defines 5 new TLVs in the registry "BGP-LS Node
Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs": Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs":
o Two new node descriptor TLVs o Two new node descriptor TLVs
o Three new link attribute TLVs o Three new link attribute TLVs
All the new 5 codepoints are in the same registry: "BGP-LS Node All the new 5 codepoints are in the same registry: "BGP-LS Node
Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs". Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs".
However, the registry is organized in ranges (node descriptors, link However, the registry is organized in ranges (node descriptors, link
descriptors, node attributes, link attributes). The allocation descriptors, node attributes, link attributes).
should be done accordingly.
The following new Node Descriptors TLVs are defined: The following new Node Descriptors TLVs are defined:
+---------------------------------------+ +-----------------------------------------------------------+
| Codepoint | Description | | Codepoint | Description | Status |
+---------------------------------------+ +-----------------------------------------------------------+
| TBD2 | BGP Router ID | | 516 | BGP Router-ID | Assigned by IANA |
| TBD3 | BGP Confederation Member | | 517 | BGP Confederation Member | Assigned by IANA |
+------------+--------------------------+ +------------+----------------------------------------------+
The following new Link Attribute TLVs are defined: The following new Link Attribute TLVs are defined:
+---------------------------------------+ +-----------------------------------------------------------+
| Codepoint | Description | | Codepoint | Description | Status |
+---------------------------------------+ +-----------------------------------------------------------+
| TBD4 | Peer-Node-SID | | 1101 | Peer-Node-SID | Assigned by IANA |
| TBD5 | Peer-Adj-SID | | 1102 | Peer-Adj-SID | Assigned by IANA |
| TBD6 | Peer-Set-SID | | 1103 | Peer-Set-SID | Assigned by IANA |
+------------+--------------------------+ +------------+----------------------------------------------+
9. Manageability Considerations 9. Manageability Considerations
This BGP-LS ([RFC7752]) extensions that are described in this This BGP-LS ([RFC7752]) extensions that are described in this
document consists of additional BGP-LS descriptors and TLVs that will document consists of additional BGP-LS descriptors and TLVs that will
follow the same manageability functions of BGP-LS, described in follow the same manageability functions of BGP-LS, described in
[RFC7752]. [RFC7752].
The operator MUST be capable of configuring, enabling, disabling the The operator MUST be capable of configuring, enabling, disabling the
advertisement of each of the Peer-Node-SID, Peer-Adj-SID and Peer- advertisement of each of the Peer-Node-SID, Peer-Adj-SID and Peer-
skipping to change at page 19, line 7 skipping to change at page 18, line 46
The Security Section of [RFC7752] also applies to: The Security Section of [RFC7752] also applies to:
o New Node Descriptors Sub-TLVs: BGP-Router-ID and BGP- o New Node Descriptors Sub-TLVs: BGP-Router-ID and BGP-
Confederation-Member; Confederation-Member;
o New BGP-LS Attributes TLVs: Peer-Node-SID, Peer-Adj-SID and Peer- o New BGP-LS Attributes TLVs: Peer-Node-SID, Peer-Adj-SID and Peer-
Set-SID. Set-SID.
11. Contributors 11. Contributors
Saikat Ray and Acee Lindem gave a substantial contribution to this Acee Lindem gave a substantial contribution to this document.
document.
12. Acknowledgements 12. Acknowledgements
The authors would like to thank Jakob Heitz, Howard Yang, Hannes The authors would like to thank Jakob Heitz, Howard Yang, Hannes
Gredler, Peter Psenak, Ketan Jivan Talaulikar, and Arjun Sreekantiah Gredler, Peter Psenak, Ketan Jivan Talaulikar, and Arjun Sreekantiah
for their feedback and comments. for their feedback and comments.
13. References 13. References
13.1. Normative References 13.1. Normative References
skipping to change at page 19, line 49 skipping to change at page 19, line 38
[RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP [RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP
Identifier for BGP-4", RFC 6286, DOI 10.17487/RFC6286, Identifier for BGP-4", RFC 6286, DOI 10.17487/RFC6286,
June 2011, <http://www.rfc-editor.org/info/rfc6286>. June 2011, <http://www.rfc-editor.org/info/rfc6286>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
and R. Shakir, "Segment Routing Architecture", draft-ietf- and R. Shakir, "Segment Routing Architecture", draft-ietf-
spring-segment-routing-10 (work in progress), November spring-segment-routing-11 (work in progress), February
2016. 2017.
[I-D.ietf-spring-segment-routing-central-epe] [I-D.ietf-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev, Filsfils, C., Previdi, S., Aries, E., and D. Afanasiev,
"Segment Routing Centralized BGP Peer Engineering", draft- "Segment Routing Centralized BGP Egress Peer Engineering",
ietf-spring-segment-routing-central-epe-03 (work in draft-ietf-spring-segment-routing-central-epe-04 (work in
progress), November 2016. progress), February 2017.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<http://www.rfc-editor.org/info/rfc7752>. <http://www.rfc-editor.org/info/rfc7752>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
 End of changes. 29 change blocks. 
55 lines changed or deleted 57 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/