draft-ietf-idr-bgpls-segment-routing-epe-14.txt   draft-ietf-idr-bgpls-segment-routing-epe-15.txt 
Network Working Group S. Previdi, Ed. Inter-Domain Routing S. Previdi, Ed.
Internet-Draft C. Filsfils Internet-Draft Individual
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track C. Filsfils
Expires: June 22, 2018 K. Patel Expires: September 6, 2018 Cisco Systems, Inc.
K. Patel
Arrcus, Inc. Arrcus, Inc.
S. Ray S. Ray
Individual Contributor Individual Contributor
J. Dong J. Dong
Huawei Technologies Huawei Technologies
December 19, 2017 March 5, 2018
BGP-LS extensions for Segment Routing BGP Egress Peer Engineering BGP-LS extensions for Segment Routing BGP Egress Peer Engineering
draft-ietf-idr-bgpls-segment-routing-epe-14 draft-ietf-idr-bgpls-segment-routing-epe-15
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 10 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 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 June 22, 2018. This Internet-Draft will expire on September 6, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Segment Routing Documents . . . . . . . . . . . . . . . . . . 3 2. Segment Routing Documents . . . . . . . . . . . . . . . . . . 4
3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 4 3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 4
4. Link NLRI for BGP-EPE Connectivity Description . . . . . . . 5 4. Link NLRI for BGP-EPE Connectivity Description . . . . . . . 5
4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 5 4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 6
4.2. Mandatory BGP-EPE Node Descriptors . . . . . . . . . . . 6 4.2. Mandatory BGP-EPE Node Descriptors . . . . . . . . . . . 6
4.3. Optional BGP-EPE Node Descriptors . . . . . . . . . . . . 7 4.3. Optional BGP-EPE Node Descriptors . . . . . . . . . . . . 7
4.4. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7 4.4. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7
5. Peer-Node and Peer-Adj SIDs . . . . . . . . . . . . . . . . . 9 5. Peer-Node and Peer-Adj SIDs . . . . . . . . . . . . . . . . . 9
5.1. Peer-Node-SID . . . . . . . . . . . . . . . . . . . . . . 10 5.1. Peer-Node-SID . . . . . . . . . . . . . . . . . . . . . . 10
5.2. Peer-Adj-SID . . . . . . . . . . . . . . . . . . . . . . 11 5.2. Peer-Adj-SID . . . . . . . . . . . . . . . . . . . . . . 11
5.3. Peer-Set-SID . . . . . . . . . . . . . . . . . . . . . . 12 5.3. Peer-Set-SID . . . . . . . . . . . . . . . . . . . . . . 12
6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12
6.2. Peer-Node-SID for Node D . . . . . . . . . . . . . . . . 14 6.2. Peer-Node-SID for Node D . . . . . . . . . . . . . . . . 14
6.3. Peer-Node-SID for Node F . . . . . . . . . . . . . . . . 15 6.3. Peer-Node-SID for Node F . . . . . . . . . . . . . . . . 15
6.4. Peer-Node-SID for Node E . . . . . . . . . . . . . . . . 15 6.4. Peer-Node-SID for Node E . . . . . . . . . . . . . . . . 15
6.5. Peer-Adj-SID for Node E, Link 1 . . . . . . . . . . . . . 15 6.5. Peer-Adj-SID for Node E, Link 1 . . . . . . . . . . . . . 15
6.6. Peer-Adj-SID for Node E, Link 2 . . . . . . . . . . . . . 16 6.6. Peer-Adj-SID for Node E, Link 2 . . . . . . . . . . . . . 16
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 . . . . . . . . 18 8.2. Node Descriptors and Link Attribute TLVs . . . . . . . . 17
9. Manageability Considerations . . . . . . . . . . . . . . . . 18 9. Manageability Considerations . . . . . . . . . . . . . . . . 18
10. Security Considerations . . . . . . . . . . . . . . . . . . . 19 10. Security Considerations . . . . . . . . . . . . . . . . . . . 18
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
13.1. Normative References . . . . . . . . . . . . . . . . . . 20 13.1. Normative References . . . . . . . . . . . . . . . . . . 19
13.2. Informative References . . . . . . . . . . . . . . . . . 20 13.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
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 with segment identifiers prepending the packet with an SR header with segment identifiers
(SID). A SID can represent any instruction, topological or service- (SID). A SID can represent any instruction, topological or service-
based. SR allows to enforce a flow through any topological path and based. SR allows to enforce a flow through any topological path and
skipping to change at page 6, line 36 skipping to change at page 6, line 42
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.
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 Router-ID> tuple is globally unique.
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.
4.3. Optional BGP-EPE Node Descriptors 4.3. Optional BGP-EPE Node Descriptors
skipping to change at page 8, line 31 skipping to change at page 8, line 31
Descriptor, and Attribute TLVs"). Descriptor, and Attribute TLVs").
o Length: variable. o Length: variable.
o Flags: one octet of flags used when advertising a Peer-Adj-SID o Flags: one octet of flags used when advertising a Peer-Adj-SID
(Peer-Node and Peer-Set SIDs don't have flags defined). The (Peer-Node and Peer-Set SIDs don't have flags defined). The
following Peer-Adj-SID flags have been defined: following Peer-Adj-SID flags have been defined:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|V|L| | |V|L|B|P| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
where: where:
* V-Flag: Value flag. If set, then the Adj-SID carries a value. * V-Flag: Value flag. If set, then the SID carries a label
By default the flag is SET. value. By default the flag is SET.
* L-Flag: Local Flag. If set, then the value/index carried by * L-Flag: Local Flag. If set, then the value/index carried by
the Adj-SID has local significance. By default the flag is the SID has local significance. By default the flag is SET.
SET.
* B-Flag: Backup Flag. If set, the SID refers to a path that is
eligible for protection.
* P-Flag: Persistent Flag: If set, the SID is persistently
allocated, i.e., the SID value remains consistent across router
restart and session/interface flap.
* Other bits: MUST be zero when originated and ignored when * Other bits: MUST be zero when originated and ignored when
received. received.
o Weight: 1 octet. The value represents the weight of the SID for o Weight: 1 octet. The value represents the weight of the SID for
the purpose of load balancing. An example use of the weight is the purpose of load balancing. An example use of the weight is
described in [I-D.ietf-spring-segment-routing]. described in [I-D.ietf-spring-segment-routing].
o SID/Index/Label. According to the TLV length and to the V and L o SID/Index/Label. According to the TLV length and to the V and L
flags settings, it contains either: flags settings, it contains either:
skipping to change at page 9, line 15 skipping to change at page 9, line 22
* A 3 octet local label where the 20 rightmost bits are used for * A 3 octet local label where the 20 rightmost bits are used for
encoding the label value. In this case the V and L flags MUST encoding the label value. In this case the V and L flags MUST
be set. be set.
* A 4 octet index defining the offset in the SRGB (Segment * A 4 octet index defining the offset in the SRGB (Segment
Routing Global Block as defined in Routing Global Block as defined in
[I-D.ietf-spring-segment-routing] advertised by this router. [I-D.ietf-spring-segment-routing] advertised by this router.
In this case, the SRGB MUST be advertised using the extensions In this case, the SRGB MUST be advertised using the extensions
defined in [I-D.ietf-idr-bgp-ls-segment-routing-ext]. defined in [I-D.ietf-idr-bgp-ls-segment-routing-ext].
* A 16 octet IPv6 address. In this case the V flag MUST be set.
The L flag MUST be unset if the IPv6 address is globally
unique.
The values of the Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID Sub- The values of the Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID Sub-
TLVs SHOULD be persistent across router restart. TLVs SHOULD be persistent across router restart.
The Peer-Node-SID MUST be present when BGP-LS is used for the use The Peer-Node-SID MUST be present when BGP-LS is used for the use
case described in [I-D.ietf-spring-segment-routing-central-epe] and case described in [I-D.ietf-spring-segment-routing-central-epe] and
MAY be omitted for other use cases. MAY be omitted for other use cases.
The Peer-Adj-SID and Peer-Set-SID SubTLVs MAY be present when BGP-LS The Peer-Adj-SID and Peer-Set-SID SubTLVs MAY be present when BGP-LS
is used for the use case described in is used for the use case described in
[I-D.ietf-spring-segment-routing-central-epe] and MAY be omitted for [I-D.ietf-spring-segment-routing-central-epe] and MAY be omitted for
other use cases. other use cases.
In addition, BGP-LS Nodes and Link Attributes, as defined in In addition, BGP-LS Node and Link Attributes, as defined in [RFC7752]
[RFC7752] MAY be inserted in order to advertise the characteristics MAY be inserted in order to advertise the characteristics of the
of the link. link.
5. Peer-Node and Peer-Adj SIDs 5. Peer-Node and Peer-Adj SIDs
In this section the following SIDs are defined: In this section the following SIDs are defined:
Peer Node Segment Identifier (Peer-Node-SID) Peer Node Segment Identifier (Peer-Node-SID)
Peer Adjacency Segment Identifier (Peer-Adj-SID) Peer Adjacency Segment Identifier (Peer-Adj-SID)
Peer Set Segment Identifier (Peer-Set-SID) Peer Set Segment Identifier (Peer-Set-SID)
The Peer-Node, Peer-Adj and Peer-Set SIDs can be either a local or a The Peer-Node, Peer-Adj and Peer-Set SIDs can be either a local or a
global (depending on the setting of the V and L flags defined in global (depending on the setting of the V and L flags defined in
Figure 2. For example, when BGP-EPE is used in the context of a SR Figure 2.
network over the IPv6 dataplane, it is likely the case that the IPv6
addresses used as SIDs will be global.
5.1. Peer-Node-SID 5.1. Peer-Node-SID
The Peer-Node-SID describes the BGP session peer (neighbor). It MUST The Peer-Node-SID describes the BGP session peer (neighbor). It MUST
be present when describing a BGP-EPE topology as defined in be present when describing a BGP-EPE topology as defined in
[I-D.ietf-spring-segment-routing-central-epe]. The Peer-Node-SID is [I-D.ietf-spring-segment-routing-central-epe]. The Peer-Node-SID is
encoded within the BGP-LS Link NLRI specified in Section 4. encoded within the BGP-LS Link NLRI specified in Section 4.
The Peer-Node-SID, at the BGP node advertising it, has the following The Peer-Node-SID, at the BGP node advertising it, has the following
semantic: semantic:
skipping to change at page 10, line 25 skipping to change at page 10, line 25
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-SID is advertised with a Link NLRI, where: The Peer-Node-SID 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.
BGP-LS Identifier. * Local ASN.
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
Peer ASN. session).
* 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 11, line 22 skipping to change at page 11, line 22
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-Adj-SID is advertised with a Link NLRI, where: The Peer-Adj-SID 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.
BGP-LS Identifier. * Local ASN.
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
Peer ASN. session).
* 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],
MAY contain the following TLVs: MAY contain the following TLVs:
skipping to change at page 12, line 28 skipping to change at page 12, line 28
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: load balance across any connected interface to any peer o Next-Hop: load balance across any connected interface to any peer
in the related set. in the related set.
The Peer-Set-SID is advertised within a Link NLRI (describing a Peer The Peer-Set-SID is advertised within a Link NLRI (describing a Peer
Node Segment or a Peer Adjacency segment) as a BGP-LS attribute. Node Segment or a Peer Adjacency segment) as a BGP-LS attribute.
The Peer Set Attribute contains the Peer-Set-SID TLV, defined in The Link Attribute contains the Peer-Set-SID TLV, defined in
Section 4.4 identifying the set of which the Peer-Node-SID or Peer- Section 4.4 identifying the set of which the Peer-Node-SID or Peer-
Adj-SID is a member. Adj-SID is a member.
6. Illustration 6. Illustration
6.1. Reference Diagram 6.1. Reference Diagram
The following reference diagram is used throughout this document. The following reference diagram is used throughout this document.
The solution is illustrated for IPv6 with MPLS-based SIDs and the The solution is illustrated for IPv6 with MPLS-based SIDs and the
BGP-EPE topology is based on eBGP sessions between external peers. BGP-EPE topology is based on eBGP sessions between external peers.
skipping to change at page 14, line 28 skipping to change at page 14, line 28
Node C configuration is such that: Node C configuration is such that:
o A Peer-Node-SID is allocated to each peer (D, F and E). o A Peer-Node-SID is allocated to each peer (D, F and E).
o An Peer-Adj-SID is defined for each recursing interface to a o An Peer-Adj-SID is defined for each recursing interface to a
multi-hop peer (CE upper and lower interfaces). multi-hop peer (CE upper and lower interfaces).
o A Peer-Set-SID is defined to include all peers in AS3 (peers F and o A Peer-Set-SID is defined to include all peers in AS3 (peers F and
E). E).
Local BGP-LS Identifier in router C is set to 10000.
The Link NLRI Type is used in order to encode C's connectivity. The The Link NLRI Type is used in order to encode C's connectivity. The
Link NLRI uses the Protocol-ID value (to be assigned by IANA) Link NLRI uses the Protocol-ID for BGP value 7 assigned by IANA.
Once the BGP-LS update is originated by C, it may be advertised to Once the BGP-LS update is originated by C, it may be advertised to
internal (iBGP) as well as external (eBGP) neighbors supporting the internal (iBGP) as well as external (eBGP) neighbors supporting the
BGP-LS EPE extensions defined in this document. BGP-LS EPE extensions defined in this document.
6.2. Peer-Node-SID for Node D 6.2. Peer-Node-SID for Node D
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, local ASN, BGP-LS o Local Node Descriptors (BGP Router-ID, local ASN): 192.0.2.3, AS1
Identifier): 192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, peer ASN): 192.0.2.4, AS2 o Remote Node Descriptors (BGP Router-ID, peer ASN): 192.0.2.4, AS2
o Link Descriptors (BGP session IPv6 local address, BGP session IPv6 o Link Descriptors (BGP session IPv6 local address, BGP session IPv6
neighbor address): 2001:db8:cd::c, 2001:db8:cd::d neighbor address): 2001:db8:cd::c, 2001:db8:cd::d
Attributes: Attributes:
o Peer-Node-SID: 1012 o Peer-Node-SID: 1012
o Link Attributes: see section 3.3.2 of [RFC7752] o Link Attributes: see section 3.3.2 of [RFC7752]
6.3. Peer-Node-SID for Node F 6.3. Peer-Node-SID for Node F
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGPLS Identifier): o Local Node Descriptors (BGP Router-ID, ASN): 192.0.2.3, AS1
192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID ASN): 192.0.2.6, AS3 o Remote Node Descriptors (BGP Router-ID ASN): 192.0.2.6, AS3
o Link Descriptors (BGP session IPv6 local address, BGP session IPv6 o Link Descriptors (BGP session IPv6 local address, BGP session IPv6
peer address): 2001:db8:cf::c, 2001:db8:cf::f peer address): 2001:db8:cf::c, 2001:db8:cf::f
Attributes: Attributes:
o Peer-Node-SID: 1022 o Peer-Node-SID: 1022
o Peer-Set-SID: 1060 o Peer-Set-SID: 1060
o Link Attributes: see section 3.3.2 of [RFC7752] o Link Attributes: see section 3.3.2 of [RFC7752]
6.4. Peer-Node-SID for Node E 6.4. Peer-Node-SID for Node E
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN): 192.0.2.3, AS1
192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3
o Link Descriptors (BGP session IPv6 local address, BGP session IPv6 o Link Descriptors (BGP session IPv6 local address, BGP session IPv6
peer address): 2001:db8:c::c, 2001:db8:e::e peer address): 2001:db8:c::c, 2001:db8:e::e
Attributes: Attributes:
o Peer-Node-SID: 1052 o Peer-Node-SID: 1052
o Peer-Set-SID: 1060 o Peer-Set-SID: 1060
6.5. Peer-Adj-SID for Node E, Link 1 6.5. Peer-Adj-SID for Node E, Link 1
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN): 192.0.2.3, AS1
192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3
o Link Descriptors (local interface identifier, IPv6 peer interface o Link Descriptors (local interface identifier, IPv6 peer interface
address): 0.0.0.1.0.0.0.0 , 2001:db8:ce1::e address): 0.0.0.1.0.0.0.0 , 2001:db8:ce1::e
Attributes: Attributes:
o Peer-Adj-SID: 1032 o Peer-Adj-SID: 1032
o LinkAttributes: see section 3.3.2 of [RFC7752] o LinkAttributes: see section 3.3.2 of [RFC7752]
6.6. Peer-Adj-SID for Node E, Link 2 6.6. Peer-Adj-SID for Node E, Link 2
skipping to change at page 16, line 17 skipping to change at page 16, line 13
Attributes: Attributes:
o Peer-Adj-SID: 1032 o Peer-Adj-SID: 1032
o LinkAttributes: see section 3.3.2 of [RFC7752] o LinkAttributes: see section 3.3.2 of [RFC7752]
6.6. Peer-Adj-SID for Node E, Link 2 6.6. Peer-Adj-SID for Node E, Link 2
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN): 192.0.2.3, AS1
192.0.2.3, AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 192.0.2.5, AS3
o Link Descriptors (local interface identifier, IPv6 peer interface o Link Descriptors (local interface identifier, IPv6 peer interface
address): 0.0.0.2.0.0.0.0 , 2001:db8:ce2::e address): 0.0.0.2.0.0.0.0 , 2001:db8:ce2::e
Attributes: Attributes:
o Peer-Adj-SID: 1042 o Peer-Adj-SID: 1042
skipping to change at page 20, line 4 skipping to change at page 19, line 43
Email: ketant@cisco.com Email: ketant@cisco.com
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, Arjun Sreekantiah and Bruno Decraene for their Gredler, Peter Psenak, Arjun Sreekantiah and Bruno Decraene for their
feedback and comments. feedback and comments.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing Litkowski, S., and R. Shakir, "Segment Routing
Architecture", draft-ietf-spring-segment-routing-13 (work Architecture", draft-ietf-spring-segment-routing-15 (work
in progress), October 2017. in progress), January 2018.
[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>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<https://www.rfc-editor.org/info/rfc4271>. <https://www.rfc-editor.org/info/rfc4271>.
skipping to change at page 20, line 39 skipping to change at page 20, line 32
(GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008,
<https://www.rfc-editor.org/info/rfc5307>. <https://www.rfc-editor.org/info/rfc5307>.
[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, <https://www.rfc-editor.org/info/rfc6286>. June 2011, <https://www.rfc-editor.org/info/rfc6286>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-idr-bgp-ls-segment-routing-ext] [I-D.ietf-idr-bgp-ls-segment-routing-ext]
Previdi, S., Psenak, P., Filsfils, C., Gredler, H., and M. Previdi, S., Talaulikar, K., Filsfils, C., Gredler, H.,
Chen, "BGP Link-State extensions for Segment Routing", and M. Chen, "BGP Link-State extensions for Segment
draft-ietf-idr-bgp-ls-segment-routing-ext-03 (work in Routing", draft-ietf-idr-bgp-ls-segment-routing-ext-04
progress), July 2017. (work in progress), January 2018.
[I-D.ietf-spring-segment-routing-central-epe] [I-D.ietf-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Dawra, G., Aries, E., and D. Filsfils, C., Previdi, S., Dawra, G., Aries, E., and D.
Afanasiev, "Segment Routing Centralized BGP Egress Peer Afanasiev, "Segment Routing Centralized BGP Egress Peer
Engineering", draft-ietf-spring-segment-routing-central- Engineering", draft-ietf-spring-segment-routing-central-
epe-08 (work in progress), December 2017. epe-10 (work in progress), December 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,
<https://www.rfc-editor.org/info/rfc7752>. <https://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,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi (editor)
Cisco Systems, Inc. Individual
Email: stefano@previdi.net Email: stefano@previdi.net
Clarence Filsfils Clarence Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
Brussels Brussels
BE Belgium
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
Keyur Patel Keyur Patel
Arrcus, Inc. Arrcus, Inc.
Email: Keyur@arrcus.com Email: Keyur@arrcus.com
Saikat Ray Saikat Ray
Individual Contributor Individual Contributor
 End of changes. 38 change blocks. 
64 lines changed or deleted 63 lines changed or added

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