draft-ietf-idr-bgpls-segment-routing-epe-00.txt   draft-ietf-idr-bgpls-segment-routing-epe-01.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: December 19, 2015 S. Ray Expires: June 5, 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
June 17, 2015 December 3, 2015
Segment Routing Egress Peer Engineering BGP-LS Extensions Segment Routing Egress Peer Engineering BGP-LS Extensions
draft-ietf-idr-bgpls-segment-routing-epe-00 draft-ietf-idr-bgpls-segment-routing-epe-01
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 December 19, 2015. This Internet-Draft will expire on June 5, 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
skipping to change at page 2, line 39 skipping to change at page 2, line 39
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 . . . . . . . . . . . . . . . . . . . . 3
4. Link NLRI for EPE Connectivity Description . . . . . . . . . 4 4. Link NLRI for EPE Connectivity Description . . . . . . . . . 4
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 . . . . . . . . . . . . . . . . . . 5
4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6 4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6
5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 8 5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 8
5.1. Peer Node Segment . . . . . . . . . . . . . . . . . . . . 8 5.1. Peer Node Segment (Peer-Node-SID) . . . . . . . . . . . . 9
5.2. Peer Adjacency Segment . . . . . . . . . . . . . . . . . 9 5.2. Peer Adjacency Segment (Peer-Adj-SID) . . . . . . . . . . 10
5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 10 5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 11
6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 10 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 11
6.1.1. Peer Node Segment for Node D . . . . . . . . . . . . 12 6.1.1. Peer Node Segment for Node D . . . . . . . . . . . . 13
6.1.2. Peer Node Segment for Node H . . . . . . . . . . . . 13 6.1.2. Peer Node Segment for Node H . . . . . . . . . . . . 14
6.1.3. Peer Node Segment for Node E . . . . . . . . . . . . 13 6.1.3. Peer Node Segment for Node E . . . . . . . . . . . . 14
6.1.4. Peer Adj Segment for Node E, Link 1 . . . . . . . . . 13 6.1.4. Peer Adjacency Segment for Node E, Link 1 . . . . . . 14
6.1.5. Peer Adj Segment for Node E, Link 2 . . . . . . . . . 14 6.1.5. Peer Adjacency Segment for Node E, Link 2 . . . . . . 15
7. BGP-LS EPE TLV/Sub-TLV Code Points Summary . . . . . . . . . 14 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 8. Manageability Considerations . . . . . . . . . . . . . . . . 16
9. Manageability Considerations . . . . . . . . . . . . . . . . 15 9. Security Considerations . . . . . . . . . . . . . . . . . . . 16
10. Security Considerations . . . . . . . . . . . . . . . . . . . 15 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 12.1. Normative References . . . . . . . . . . . . . . . . . . 16
13.1. Normative References . . . . . . . . . . . . . . . . . . 16 12.2. Informative References . . . . . . . . . . . . . . . . . 17
13.2. Informative References . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
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
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 4, line 13 skipping to change at page 4, line 13
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
the BGP Peering Segment for the chosen egress PE peer or peering the BGP Peering Segment for the chosen egress PE peer or peering
interface. interface.
This document defines the BGP EPE Peering Segments: Peer Node, Peer This document defines the BGP EPE Peering Segments:
Adjacency and Peer Set.
o Peer Node Segment (Peer-Node-SID)
o Peer Adjacency Segment (Peer-Adj-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.filsfils-spring-segment-routing-central-epe]:
skipping to change at page 7, line 5 skipping to change at page 7, line 5
(when BGP confederations are used). (when BGP confederations are used).
o Node Descriptors as defined in defined in o Node Descriptors as defined in defined in
[I-D.ietf-idr-ls-distribution]. [I-D.ietf-idr-ls-distribution].
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 | | |
+----------+--------------------------+----------+ +----------+---------------------------+----------+
| 1099 | Adjacency-Segment | variable | | 1101 | Peer Node Segment | variable |
| | Identifier (Adj-SID) | | | | Identifier (Peer-Node-SID)| |
| TBA | Peer-Segment Identifier | variable | | 1102 | Peer Adjacency Segment | variable |
| | (Peer-SID) | | | | Identifier (Peer-Adj-SID) | |
| TBA | Peer-Set-SID | variable | | 1103 | Peer Set Segment | variable |
+----------+--------------------------+----------+ | | Identifier (Peer-Set-SID) | |
+----------+---------------------------+----------+
Adj-SID is defined in Figure 1: TLV code points for BGP-LS EPE
[I-D.gredler-idr-bgp-ls-segment-routing-extension] and the same
format is used for the Peer-SID and Peer-Set-SID TLVs.
Peer-SID and Peer-Set SID are two new sub-TLVs with the same format Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format
as the Adj-SID and whose codepoints are to be assigned by IANA: defined here below:
Peer-SID: SID representing the peer of the BGP session. The 0 1 2 3
format is the same as defined for the Adj-SID in 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
[I-D.gredler-idr-bgp-ls-segment-routing-extension]. Suggested +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
codepoint value: 1036 | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Weight | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label/Index (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Peer-Set-SID: the SID representing the group the peer is part of. where:
The format is the same as defined for the Adj-SID in
[I-D.gredler-idr-bgp-ls-segment-routing-extension]. Suggested
codepoint value: 1037
The value of the Adj-SID, Peer-SID and Peer-Set-SID Sub-TLVs SHOULD Figure 2
be persistent across router restart.
The Peer-SID MUST be present when BGP-LS is used for the use case o Type: To be assigned by IANA. The suggested values are defined in
described in [I-D.filsfils-spring-segment-routing-central-epe] and Figure 1.
MAY be omitted for other use cases.
The Adj-SID and Peer-Set-SID SubTLVs MAY be present when BGP-LS is o Length: variable.
used for the use case described in
o Flags: following flags have been defined:
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|V|L| |
+-+-+-+-+-+-+-+-+
where:
* V-Flag: Value flag. If set, then the Adj-SID carries a value.
By default the flag is SET.
* L-Flag: Local Flag. If set, then the value/index carried by
the Adj-SID has local significance. By default the flag is
SET.
* Other bits: MUST be zero when originated and ignored when
received.
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
described in [I-D.ietf-spring-segment-routing].
o SID/Index/Label. According to the TLV length and to the V and L
flags settings, it contains either:
* 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
be set.
* A 4 octet index defining the offset in the SID/Label space
advertised by this router using the encodings defined in
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.
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-
TLVs SHOULD be persistent across router restart.
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]
and MAY be omitted for other use cases.
The Peer-Adj-SID and Peer-Set-SID SubTLVs MAY be present when BGP-LS
is used for the use case described in
[I-D.filsfils-spring-segment-routing-central-epe] and MAY be omitted [I-D.filsfils-spring-segment-routing-central-epe] and MAY be omitted
for other use cases. for 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)
Peer Adjacency Segment (Peer-Adj-SID)
Peer Adjacency Segment (Peer Adj SID) Peer Set Segment (Peer-Set-SID)
Peer Set Segment (Peer Set SID) 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
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
case that the IPv6 addresses used as SIDs will be global.
5.1. Peer Node Segment 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.filsfils-spring-segment-routing-central-epe]. The Peer Node
Segment is encoded within the BGP-LS Link NLRI specified in Segment is encoded within the BGP-LS Link NLRI specified in
Section 4. Section 4.
The Peer Node Segment is a local segment. At the BGP node The Peer Node Segment, at the BGP node advertising it, has the
advertising it, its semantic is: 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.
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
skipping to change at page 9, line 14 skipping to change at page 10, line 14
* 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.
* IPv6 Interface Address (Sub-TLV 261) contains the BGP session * IPv6 Interface Address (Sub-TLV 261) contains the BGP session
IPv6 local address. IPv6 local address.
* IPv6 Neighbor Address (Sub-TLV 262) contains the BGP session * IPv6 Neighbor Address (Sub-TLV 262) contains the BGP session
IPv6 peer address. IPv6 peer address.
o Link Attribute contains the Peer-SID TLV as defined in o Link Attribute contains the Peer-Node-SID TLV as defined in
Section 4.3. Section 4.3.
o In addition, BGP-LS Link Attributes, as defined in o In addition, BGP-LS Link Attributes, as defined in
[I-D.ietf-idr-ls-distribution], MAY be inserted in order to [I-D.ietf-idr-ls-distribution], MAY be inserted in order to
advertise the characteristics of the link. advertise the characteristics of the link.
5.2. Peer Adjacency Segment 5.2. Peer Adjacency Segment (Peer-Adj-SID)
The Peer Adjacency Segment is a local segment. At the BGP node The Peer Adjacency Segment, at the BGP node advertising it, has the
advertising it, its semantic is: 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 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 EPE enabled egress PE. Local BGP Router ID of the 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 o Link Descriptors Sub-TLVs, as defined in
[I-D.ietf-idr-ls-distribution], contain the addresses used by the [I-D.ietf-idr-ls-distribution], MUST contain the following TLVs:
BGP session:
* 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
[I-D.ietf-idr-ls-distribution], MAY contain the following TLVs:
* IPv4 Interface Address (Sub-TLV 259) contains the address of
the local interface through which the BGP session is
established.
* IPv6 Interface Address (Sub-TLV 261) contains the address of
the local interface through which the BGP session is
established.
* IPv4 Neighbor Address (Sub-TLV 260) contains the IPv4 address * IPv4 Neighbor Address (Sub-TLV 260) contains the IPv4 address
of the peer interface used by the BGP session. of the peer interface used by the BGP session.
* IPv6 Neighbor Address (Sub-TLV 262) contains the IPv6 address * IPv6 Neighbor Address (Sub-TLV 262) contains the IPv6 address
of the peer interface used by the BGP session. of the peer interface used by the BGP session.
o Link attribute used with the Peer Adjacency SID contains the Adj- o Link attribute used with the Peer-Adj-SID contains the TLV as
SID TLV as defined in Section 4.3. defined in Section 4.3.
In addition, BGP-LS Link Attributes, as defined in In addition, BGP-LS 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.3. Peer Set Segment 5.3. Peer Set Segment
The Peer Set Segment is a local segment. At the BGP node advertising The Peer Adjacency Segment, at the BGP node advertising it, has the
it, its semantic is: 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: 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 Segment is advertised within a Link NLRI (describing a The Peer Set Segment is advertised within a Link NLRI (describing a
Peer Node Segment or a Peer Adjacency segment) as a BGP-LS attribute. Peer Node Segment or a Peer Adjacency segment) as a BGP-LS attribute.
skipping to change at page 11, line 19 skipping to change at page 12, line 19
| 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
+----P----+ +===E AS 3 | +----P----+ +===E AS 3 |
| +--Q---+ | +--Q---+
| | | |
+----------------+ +----------------+
Figure 1: 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, E's interface:
skipping to change at page 12, line 20 skipping to change at page 13, line 20
o Multi-hop eBGP peering with E on ip address 1.0.5.2 (E) o Multi-hop eBGP peering with E on ip address 1.0.5.2 (E)
C's resolution of the multi-hop eBGP session to E: C's resolution of the multi-hop eBGP session to E:
o Static route 1.0.5.2/32 via 1.0.3.2 o Static route 1.0.5.2/32 via 1.0.3.2
o Static route 1.0.5.2/32 via 1.0.4.2 o Static route 1.0.5.2/32 via 1.0.4.2
Node C configuration is such that: Node C configuration is such that:
o A Peer Node segment is allocated to each peer (D, H and E). o A Peer Node segment (Peer-Node-SID) is allocated to each peer (D,
H and E).
o An Adjacency segment is defined for each recursing interface to a o An Peer Adjacency segment (Peer-Adj-SID) is defined for each
multi-hop peer (CE upper and lower interfaces). recursing interface to a multi-hop peer (CE upper and lower
interfaces).
o A Peer Set segment is defined to include all peers in AS3 (peers H o A Peer Set segment (Peer-Set-SID) is defined to include all peers
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 6.1.1. 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
Attributes: Attributes:
o Peer-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.1.2. 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-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.1.3. 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-SID: 1052 o Peer-Node-SID: 1052
o Peer-Set-SID: 1060 o Peer-Set-SID: 1060
6.1.4. Peer Adj Segment for Node E, Link 1 6.1.4. 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 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 Adj Segment for Node E, Link 2 6.1.5. 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
Attributes: Attributes:
o Adj-SID: 1042 o Peer-Adj-SID: 1042
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]
7. BGP-LS EPE TLV/Sub-TLV Code Points Summary 7. IANA Considerations
The following table contains the TLVs/Sub-TLVs defined in this This document defines:
document.
Two new Node Descriptors Sub-TLVs: BGP-Router-ID and BGP
Confederation Member.
A new Protocol-ID for EPE: BGP-EPE.
Three new BGP-LS Attribute Sub-TLVs: Peer-Node-SID, Peer-Adj-SID
and Peer-Set-SID.
The codepoints are to be assigned by IANA. The following are the
suggested values:
+---------------------+--------------------------+-------------+ +---------------------+--------------------------+-------------+
| Suggested Codepoint | Description | Defined in: | | Suggested Codepoint | Description | Defined in: |
+---------------------+--------------------------+-------------+ +---------------------+--------------------------+-------------+
| 7 | Protocol-ID | Section 4 | | 7 | Protocol-ID | Section 4 |
| 516 | BGP Router ID | Section 4.1 | | 516 | BGP Router ID | Section 4.1 |
| 517 | BGP Confederation Member | Section 4.1 | | 517 | BGP Confederation Member | Section 4.1 |
| 1036 | Peer-SID | Section 4.3 | | 1101 | Peer-Node-SID | Section 4.3 |
| 1037 | Peer-Set-SID | Section 4.3 | | 1102 | Peer-Adj-SID | Section 4.3 |
| 1103 | Peer-Set-SID | Section 4.3 |
+---------------------+--------------------------+-------------+ +---------------------+--------------------------+-------------+
Table 1: Summary Table of BGP-LS EPE Codepoints Table 1: Summary Table of BGP-LS EPE Codepoints
8. IANA Considerations 8. Manageability Considerations
This document defines:
Two new Node Descriptors Sub-TLVs: BGP-Router-ID and BGP
Confederation Member.
A new Protocol-ID for EPE: BGP-EPE.
Two new BGP-LS Attribute Sub-TLVs: the Peer-SID and the Peer-Set-
SID.
The codepoints are to be assigned by IANA.
9. Manageability Considerations
TBD TBD
10. Security Considerations 9. Security Considerations
[I-D.ietf-idr-ls-distribution] defines BGP-LS NLRIs to which the [I-D.ietf-idr-ls-distribution] defines BGP-LS NLRIs to which the
extensions defined in this document apply. extensions defined in this document apply.
The Security Section of [I-D.ietf-idr-ls-distribution] also applies The Security Section of [I-D.ietf-idr-ls-distribution] also applies
to the: to:
new Node Descriptors Sub-TLVs: BGP-Router ID and BGP Confederation
Member;
Peer-SID and Peer-Set-SID attributes o New Node Descriptors Sub-TLVs: BGP-Router-ID and BGP-
Confederation-Member;
defined in this document. o New BGP-LS Attributes TLVs: Peer-Node-SID, Peer-Adj-SID and Peer-
Set-SID.
11. Contributors 10. Contributors
Acee Lindem gave a substantial contribution to this document. Acee Lindem gave a substantial contribution to this document.
12. Acknowledgements 11. Acknowledgements
The authors would like to thank Jakob Heitz, Howard Yang and Hannes The authors would like to thank Jakob Heitz, Howard Yang, Hannes
Gredler for their feedback and comments. Gredler, Peter Psenak, Ketan Jivan Talaulikar, and Arjun Sreekantiah
for their feedback and comments.
13. References 12. References
13.1. Normative References
12.1. Normative References
[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, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Protocol 4 (BGP-4)", RFC 4271, January 2006. Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006,
<http://www.rfc-editor.org/info/rfc4271>.
[RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous
System Confederations for BGP", RFC 5065, August 2007. System Confederations for BGP", RFC 5065,
DOI 10.17487/RFC5065, August 2007,
<http://www.rfc-editor.org/info/rfc5065>.
[RFC5307] Kompella, K. and Y. Rekhter, "IS-IS Extensions in Support [RFC5307] Kompella, K., Ed. and Y. Rekhter, Ed., "IS-IS Extensions
of Generalized Multi-Protocol Label Switching (GMPLS)", in Support of Generalized Multi-Protocol Label Switching
RFC 5307, October 2008. (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008,
<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, June 2011. Identifier for BGP-4", RFC 6286, DOI 10.17487/RFC6286,
June 2011, <http://www.rfc-editor.org/info/rfc6286>.
13.2. Informative References 12.2. Informative References
[I-D.filsfils-spring-segment-routing-central-epe] [I-D.filsfils-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Patel, K., Aries, E., Filsfils, C., Previdi, S., Patel, K., Shaw, S., Ginsburg,
shaw@fb.com, s., Ginsburg, D., and D. Afanasiev, "Segment D., and D. Afanasiev, "Segment Routing Centralized Egress
Routing Centralized Egress Peer Engineering", draft- Peer Engineering", draft-filsfils-spring-segment-routing-
filsfils-spring-segment-routing-central-epe-03 (work in central-epe-05 (work in progress), August 2015.
progress), January 2015.
[I-D.gredler-idr-bgp-ls-segment-routing-extension]
Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M.,
and J. Tantsura, "BGP Link-State extensions for Segment
Routing", draft-gredler-idr-bgp-ls-segment-routing-
extension-02 (work in progress), October 2014.
[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-11 Information using BGP", draft-ietf-idr-ls-distribution-13
(work in progress), June 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. Shakir, "Segment Routing Architecture", draft-ietf- and r. rjs@rob.sh, "Segment Routing Architecture", draft-
spring-segment-routing-03 (work in progress), May 2015. ietf-spring-segment-routing-06 (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. 59 change blocks. 
143 lines changed or deleted 210 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/