draft-ietf-idr-bgpls-segment-routing-epe-01.txt   draft-ietf-idr-bgpls-segment-routing-epe-02.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: June 5, 2016 S. Ray Expires: June 23, 2016 S. Ray
Individual Contributor Individual Contributor
K. Patel K. Patel
Cisco Systems, Inc. Cisco Systems, Inc.
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
December 3, 2015 December 21, 2015
Segment Routing Egress Peer Engineering BGP-LS Extensions Segment Routing Egress Peer Engineering BGP-LS Extensions
draft-ietf-idr-bgpls-segment-routing-epe-01 draft-ietf-idr-bgpls-segment-routing-epe-02
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 June 5, 2016. This Internet-Draft will expire on June 23, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
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 . . . . . . . . . . . . . . . . . . 3
3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 3 3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 4
4. Link NLRI for EPE Connectivity Description . . . . . . . . . 4 4. Link NLRI for EPE Connectivity Description . . . . . . . . . 5
4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 5 4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 5
4.2. EPE Node Descriptors . . . . . . . . . . . . . . . . . . 5 4.2. EPE Node Descriptors . . . . . . . . . . . . . . . . . . 6
4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6 4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7
5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 8 5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 9
5.1. Peer Node Segment (Peer-Node-SID) . . . . . . . . . . . . 9 5.1. Peer Node Segment (Peer-Node-SID) . . . . . . . . . . . . 9
5.2. Peer Adjacency Segment (Peer-Adj-SID) . . . . . . . . . . 10 5.2. Peer Adjacency Segment (Peer-Adj-SID) . . . . . . . . . . 10
5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 11 5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 11
6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 11 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 11 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12
6.1.1. Peer Node Segment for Node D . . . . . . . . . . . . 13 6.2. Peer Node Segment for Node D . . . . . . . . . . . . . . 14
6.1.2. Peer Node Segment for Node H . . . . . . . . . . . . 14 6.3. Peer Node Segment for Node H . . . . . . . . . . . . . . 14
6.1.3. Peer Node Segment for Node E . . . . . . . . . . . . 14 6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14
6.1.4. Peer Adjacency Segment for Node E, Link 1 . . . . . . 14 6.5. Peer Adjacency Segment for Node E, Link 1 . . . . . . . . 15
6.1.5. Peer Adjacency Segment for Node E, Link 2 . . . . . . 15 6.6. Peer Adjacency Segment for Node E, Link 2 . . . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. Manageability Considerations . . . . . . . . . . . . . . . . 16 8. Manageability Considerations . . . . . . . . . . . . . . . . 16
9. Security Considerations . . . . . . . . . . . . . . . . . . . 16 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
12.1. Normative References . . . . . . . . . . . . . . . . . . 16 12.1. Normative References . . . . . . . . . . . . . . . . . . 17
12.2. Informative References . . . . . . . . . . . . . . . . . 17 12.2. Informative References . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
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
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
skipping to change at page 3, line 35 skipping to change at page 3, line 35
point topology information (including its peers, interfaces and point topology information (including its peers, interfaces and
peering ASs) in a way that is exploitable in order to compute peering ASs) in a way that is exploitable in order to compute
efficient Egress Point Engineering policies and strategies. efficient Egress Point Engineering policies and strategies.
This document defines new types of segments: a Peer Node segment This document defines new types of segments: a Peer Node segment
describing the BGP session between two nodes; a Peer Adjacency describing the BGP session between two nodes; a Peer Adjacency
Segment describing the link (one or more) that is used by the BGP Segment describing the link (one or more) that is used by the BGP
session; the Peer Set Segment describing an arbitrary set of sessions session; the Peer Set Segment describing an arbitrary set of sessions
or links between the local BGP node and its peers. or links between the local BGP node and its peers.
While an egress point topology usually refers to eBGP sessions
between external peers, there's nothing in the extensions defined in
this document that would prevent the use of these extensions in the
context of iBGP sessions.
2. Segment Routing Documents 2. Segment Routing Documents
The main reference for this document is the SR architecture defined The main reference for this document is the SR architecture defined
in [I-D.ietf-spring-segment-routing]. in [I-D.ietf-spring-segment-routing].
The Segment Routing Egress Peer Engineering architecture is described The Segment Routing Egress Peer Engineering architecture is described
in [I-D.filsfils-spring-segment-routing-central-epe]. in [I-D.ietf-spring-segment-routing-central-epe].
3. BGP Peering Segments 3. BGP Peering Segments
As defined in [draft-filsfils-spring-segment-routing-epe], an EPE As defined in [I-D.ietf-spring-segment-routing-central-epe], an EPE
enabled Egress PE node MAY advertise segments corresponding to its enabled Egress PE node MAY advertise segments corresponding to its
attached peers. These segments are called BGP peering segments or attached peers. These segments are called BGP peering segments or
BGP Peering SIDs. They enable the expression of source-routed inter- BGP Peering SIDs. They enable the expression of source-routed inter-
domain paths. domain paths.
An ingress border router of an AS may compose a list of segments to An ingress border router of an AS may compose a list of segments to
steer a flow along a selected path within the AS, towards a selected steer a flow along a selected path within the AS, towards a selected
egress border router C of the AS and through a specific peer. At egress border router C of the AS and through a specific peer. At
minimum, a BGP Peering Engineering policy applied at an ingress PE minimum, a BGP Peering Engineering policy applied at an ingress PE
involves two segments: the Node SID of the chosen egress PE and then involves two segments: the Node SID of the chosen egress PE and then
skipping to change at page 4, line 29 skipping to change at page 4, line 37
o Peer Set Segment (Peer-Set-SID) o Peer Set Segment (Peer-Set-SID)
Each BGP session MUST be described by a Peer Node Segment. The Each BGP session MUST be described by a Peer Node Segment. The
description of the BGP session MAY be augmented by additional description of the BGP session MAY be augmented by additional
Adjacency Segments. Finally, each Peer Node Segment and Peer Adjacency Segments. Finally, each Peer Node Segment and Peer
Adjacency Segment MAY be part of the same group/set so to be able to Adjacency Segment MAY be part of the same group/set so to be able to
group EPE resources under a common Peer-Set Segment Identifier (SID). group EPE resources under a common Peer-Set Segment Identifier (SID).
Therefore, when the extensions defined in this document are applied Therefore, when the extensions defined in this document are applied
to the use case defined in to the use case defined in
[I-D.filsfils-spring-segment-routing-central-epe]: [I-D.ietf-spring-segment-routing-central-epe]:
o One Peer Node Segment MUST be present. o One Peer Node Segment MUST be present.
o One or more Peer Adjacency Segments MAY be present. o One or more Peer Adjacency Segments MAY be present.
o Each of the Peer Node and Peer Adjacency Segment MAY use the same o Each of the Peer Node and Peer Adjacency Segment MAY use the same
Peer-Set. Peer-Set.
While an egress point topology usually refers to eBGP sessions
between external peers, there's nothing in the extensions defined in
this document that would prevent the use of these extensions in the
context of iBGP sessions.
4. Link NLRI for EPE Connectivity Description 4. Link NLRI for 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 [I-D.ietf-idr-ls-distribution]) is used. A new Protocol ID is in [I-D.ietf-idr-ls-distribution]) is used. A new Protocol ID is
used (codepoint to be assigned by IANA, suggested value 7). used (codepoint to be assigned by IANA, suggested value 7).
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 carrying IGP link-state information as defined in
in[I-D.ietf-idr-ls-distribution]. The Link NLRI Type uses [I-D.ietf-idr-ls-distribution]. The Link NLRI Type uses descriptors
descriptors and attributes already defined in and attributes already defined in [I-D.ietf-idr-ls-distribution] in
[I-D.ietf-idr-ls-distribution] in addition to new TLVs defined in the addition to new TLVs defined in the following sections of this
following sections of this document. document.
The format of the Link NLRI Type is as follows: The extensions defined in this document apply to both internal and
external BGP-LS EPE advertisements.
[I-D.ietf-idr-ls-distribution] defines Link NLRI Type 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
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Protocol-ID | | Protocol-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Identifier | | Identifier |
| (64 bits) | | (64 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Local Node Descriptors // // Local Node Descriptors //
skipping to change at page 8, line 35 skipping to change at page 8, line 45
Section 3.1. In this case V and L flags MUST be unset. Section 3.1. In this case V and L flags MUST be unset.
* A 16 octet IPv6 address. In this case the V flag MUST be set. * 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 The L flag MUST be unset if the IPv6 address is globally
unique. 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.filsfils-spring-segment-routing-central-epe] case described in [I-D.ietf-spring-segment-routing-central-epe] and
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.filsfils-spring-segment-routing-central-epe] and MAY be omitted [I-D.ietf-spring-segment-routing-central-epe] and MAY be omitted for
for other use cases. other use cases.
In addition, BGP-LS Nodes and Link Attributes, as defined in In addition, BGP-LS Nodes and Link Attributes, as defined in
[I-D.ietf-idr-ls-distribution]MAY be inserted in order to advertise [I-D.ietf-idr-ls-distribution]MAY be inserted in order to advertise
the characteristics of the link. the characteristics of the link.
5. Peer Node and Peer Adjacency Segments 5. Peer Node and Peer Adjacency Segments
In this section the following Peer Segments are defined: In this section the following Peer Segments are defined:
Peer Node Segment (Peer-Node-SID) Peer Node Segment (Peer-Node-SID)
skipping to change at page 9, line 18 skipping to change at page 9, line 29
The Peer Node, Peer Adjacency and Peer Set segments can be either a The Peer Node, Peer Adjacency and Peer Set segments can be either a
local or a global segment (depending on the setting of the V and L local or a global segment (depending on the setting of the V and L
flags defined in Figure 2. For example, when EPE is used in the flags defined in Figure 2. For example, when EPE is used in the
context of a SR network over the IPv6 dataplane, it is likely the context of a SR network over the IPv6 dataplane, it is likely the
case that the IPv6 addresses used as SIDs will be global. case that the IPv6 addresses used as SIDs will be global.
5.1. Peer Node Segment (Peer-Node-SID) 5.1. Peer Node Segment (Peer-Node-SID)
The Peer Node Segment describes the BGP session peer (neighbor). It The Peer Node Segment describes the BGP session peer (neighbor). It
MUST be present when describing an EPE topology as defined in MUST be present when describing an EPE topology as defined in
[I-D.filsfils-spring-segment-routing-central-epe]. The Peer Node [I-D.ietf-spring-segment-routing-central-epe]. The Peer Node Segment
Segment is encoded within the BGP-LS Link NLRI specified in is encoded within the BGP-LS Link NLRI specified in Section 4.
Section 4.
The Peer Node Segment, at the BGP node advertising it, has the The Peer Node Segment, at the BGP node advertising it, has the
following semantic: following semantic:
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.
skipping to change at page 11, line 49 skipping to change at page 12, line 10
The Peer Set Attribute contains the Peer-Set-SID TLV, defined in The Peer Set Attribute contains the Peer-Set-SID TLV, defined in
Section 4.3 identifying the set of which the Peer Node Segment or Section 4.3 identifying the set of which the Peer Node Segment or
Peer Adjacency Segment is a member. Peer Adjacency Segment 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 described for IPv4 with MPLS-based segments. The solution is illustrated for IPv4 with MPLS-based segments and the
EPE topology is based on eBGP sessions between external peers.
As stated in Section 3, the solution illustrated hereafter is equally
applicable to an iBGP session topology. In other words, the solution
also applies to the case where C, D, H, and E are in the same AS and
run iBGP sessions between each other.
+------+ +------+
| | | |
+---D F +---D F
+---------+ / | AS 2 |\ +------+ +---------+ / | AS 2 |\ +------+
| X |/ +------+ \ | Z |---L/8 | X |/ +------+ \ | Z |---L/8
A C---+ \| | A C---+ \| |
| |\\ \ +------+ /| AS 4 |---M/8 | |\\ \ +------+ /| AS 4 |---M/8
| AS1 | \\ +-H |/ +------+ | AS1 | \\ +-H |/ +------+
| | \\ | G | | \\ | G
skipping to change at page 13, line 32 skipping to change at page 13, line 44
o An Peer Adjacency segment (Peer-Adj-SID) is defined for each o An Peer Adjacency segment (Peer-Adj-SID) is defined for each
recursing interface to a multi-hop peer (CE upper and lower recursing interface to a multi-hop peer (CE upper and lower
interfaces). interfaces).
o A Peer Set segment (Peer-Set-SID) is defined to include all peers o A Peer Set segment (Peer-Set-SID) is defined to include all peers
in AS3 (peers H and E). in AS3 (peers H and E).
Local BGP-LS Identifier in router C is set to 10000. 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 new Protocol-ID value (to be assigned by IANA). Link NLRI uses the new Protocol-ID value (to be assigned by IANA)
6.1.1. Peer Node Segment for Node D Once the BGP-LS update is originated by C, it may be advertised to
internal (iBGP) as well as external (eBGP) neighbors supporting the
BGP-LS EPE extensions defined in this document.
6.2. Peer Node Segment 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, BGP-LS
Identifier): 3.3.3.3 , AS1, 10000 Identifier): 3.3.3.3 , AS1, 10000
o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2 o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4
neighbor address): 1.0.1.1, 1.0.1.2 neighbor address): 1.0.1.1, 1.0.1.2
skipping to change at page 14, line 4 skipping to change at page 14, line 20
Identifier): 3.3.3.3 , AS1, 10000 Identifier): 3.3.3.3 , AS1, 10000
o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2 o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4
neighbor address): 1.0.1.1, 1.0.1.2 neighbor address): 1.0.1.1, 1.0.1.2
Attributes: Attributes:
o Peer-Node-SID: 1012 o Peer-Node-SID: 1012
o Link Attributes: see section 3.3.2 of o Link Attributes: see section 3.3.2 of
[I-D.ietf-idr-ls-distribution] [I-D.ietf-idr-ls-distribution]
6.1.2. Peer Node Segment for Node H 6.3. Peer Node Segment for Node H
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGPL Identifier): o Local Node Descriptors (BGP Router-ID, ASN, BGPL Identifier):
3.3.3.3 , AS1, 10000 3.3.3.3 , AS1, 10000
o Remote Node Descriptors (BGP Router-ID ASN): 6.6.6.6, AS3 o Remote Node Descriptors (BGP Router-ID ASN): 6.6.6.6, AS3
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4
peer address): 1.0.2.1, 1.0.2.2 peer address): 1.0.2.1, 1.0.2.2
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 o Link Attributes: see section 3.3.2 of
[I-D.ietf-idr-ls-distribution] [I-D.ietf-idr-ls-distribution]
6.1.3. Peer Node Segment for Node E 6.4. Peer Node Segment for Node E
Descriptors: Descriptors:
o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier):
3.3.3.3 , AS1, 10000 3.3.3.3 , AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3
o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4
peer address): 3.3.3.3, 1.0.5.2 peer address): 3.3.3.3, 1.0.5.2
Attributes: Attributes:
o Peer-Node-SID: 1052 o Peer-Node-SID: 1052
o Peer-Set-SID: 1060 o Peer-Set-SID: 1060
6.1.4. Peer Adjacency Segment for Node E, Link 1 6.5. Peer Adjacency Segment 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, BGP-LS Identifier):
3.3.3.3 , AS1, 10000 3.3.3.3 , AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3
o Link Descriptors (local interface identifier, IPv4 peer interface o Link Descriptors (local interface identifier, IPv4 peer interface
address): 0.0.0.1.0.0.0.0 , 1.0.3.2 address): 0.0.0.1.0.0.0.0 , 1.0.3.2
Attributes: Attributes:
o Peer-Adj-SID: 1032 o Peer-Adj-SID: 1032
o LinkAttributes: see section 3.3.2 of o LinkAttributes: see section 3.3.2 of
[I-D.ietf-idr-ls-distribution] [I-D.ietf-idr-ls-distribution]
6.1.5. Peer Adjacency Segment for Node E, Link 2 6.6. Peer Adjacency Segment 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, BGP-LS Identifier):
3.3.3.3 , AS1, 10000 3.3.3.3 , AS1, 10000
o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3
o Link Descriptors (local interface identifier, IPv4 peer interface o Link Descriptors (local interface identifier, IPv4 peer interface
address): 0.0.0.2.0.0.0.0 , 1.0.4.2 address): 0.0.0.2.0.0.0.0 , 1.0.4.2
skipping to change at page 17, line 31 skipping to change at page 17, line 45
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008,
<http://www.rfc-editor.org/info/rfc5307>. <http://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, <http://www.rfc-editor.org/info/rfc6286>. June 2011, <http://www.rfc-editor.org/info/rfc6286>.
12.2. Informative References 12.2. Informative References
[I-D.filsfils-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Patel, K., Shaw, S., Ginsburg,
D., and D. Afanasiev, "Segment Routing Centralized Egress
Peer Engineering", draft-filsfils-spring-segment-routing-
central-epe-05 (work in progress), August 2015.
[I-D.ietf-idr-ls-distribution] [I-D.ietf-idr-ls-distribution]
Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. Gredler, H., Medved, J., Previdi, S., Farrel, A., and S.
Ray, "North-Bound Distribution of Link-State and TE Ray, "North-Bound Distribution of Link-State and TE
Information using BGP", draft-ietf-idr-ls-distribution-13 Information using BGP", draft-ietf-idr-ls-distribution-13
(work in progress), October 2015. (work in progress), October 2015.
[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. rjs@rob.sh, "Segment Routing Architecture", draft- and r. rjs@rob.sh, "Segment Routing Architecture", draft-
ietf-spring-segment-routing-06 (work in progress), October ietf-spring-segment-routing-07 (work in progress),
2015. December 2015.
[I-D.ietf-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Ginsburg, D., and D. Afanasiev,
"Segment Routing Centralized Egress Peer Engineering",
draft-ietf-spring-segment-routing-central-epe-00 (work in
progress), October 2015.
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Via Del Serafico, 200 Via Del Serafico, 200
Rome 00142 Rome 00142
Italy Italy
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
 End of changes. 29 change blocks. 
54 lines changed or deleted 76 lines changed or added

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