draft-ietf-idr-bgpls-segment-routing-epe-04.txt   draft-ietf-idr-bgpls-segment-routing-epe-05.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Expires: November 13, 2016 S. Ray Expires: November 13, 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
May 12, 2016 May 12, 2016
Segment Routing BGP Egress Peer Engineering BGP-LS Extensions Segment Routing BGP Egress Peer Engineering BGP-LS Extensions
draft-ietf-idr-bgpls-segment-routing-epe-04 draft-ietf-idr-bgpls-segment-routing-epe-05
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 34 skipping to change at page 2, line 34
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 . . . . . . . . . . . . . . . . . . . . 4 3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 4
4. Link NLRI for BGP-PE 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 . . . . . . . . . . . . . . 5
4.2. BGP-PE Node Descriptors . . . . . . . . . . . . . . . . . 6 4.2. BGP-EPE Node Descriptors . . . . . . . . . . . . . . . . 6
4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7 4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 7
5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 12
6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 12
6.2. Peer Node Segment for Node D . . . . . . . . . . . . . . 14 6.2. Peer Node Segment for Node D . . . . . . . . . . . . . . 14
6.3. Peer Node Segment for Node H . . . . . . . . . . . . . . 14 6.3. Peer Node Segment for Node H . . . . . . . . . . . . . . 14
6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14 6.4. Peer Node Segment for Node E . . . . . . . . . . . . . . 14
skipping to change at page 5, line 5 skipping to change at page 5, line 5
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 While an egress point topology usually refers to eBGP sessions
between external peers, there's nothing in the extensions defined in between external peers, there's nothing in the extensions defined in
this document that would prevent the use of these extensions in the this document that would prevent the use of these extensions in the
context of iBGP sessions. context of iBGP sessions.
4. Link NLRI for BGP-PE Connectivity Description 4. Link NLRI for BGP-EPE Connectivity Description
This section describes the NLRI used for describing the connectivity This section describes the NLRI used for describing the connectivity
of the BGP Egress router. The connectivity is based on links and of the BGP Egress router. The connectivity is based on links and
remote peers/ASs and therefore the existing Link-Type NLRI (defined remote peers/ASs and therefore the existing Link-Type NLRI (defined
in [RFC7752]) is used. A new Protocol ID is used (codepoint to be in [RFC7752]) is used. A new Protocol ID is used (codepoint to be
assigned by IANA, suggested value 7). 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 in [RFC7752]. The carrying IGP link-state information as defined in [RFC7752]. The
skipping to change at page 6, line 16 skipping to change at page 6, line 16
o Confederation Member ASN (Member-ASN) o Confederation Member ASN (Member-ASN)
Type: TBA (suggested value 517). Type: TBA (suggested value 517).
Length: 4 octets Length: 4 octets
Value: 4 octet unsigned integer representing the Member ASN Value: 4 octet unsigned integer representing the Member ASN
inside the Confederation.[RFC5065]. inside the Confederation.[RFC5065].
4.2. BGP-PE Node Descriptors 4.2. BGP-EPE Node Descriptors
The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI
as Local Node Descriptors: as Local Node Descriptors:
o BGP Router ID, which contains the BGP Identifier of the local BGP- o BGP Router ID, which contains the BGP Identifier of the local BGP-
EPE capable node. EPE capable node.
o Autonomous System Number, which contains the local ASN or local o Autonomous System Number, which contains the local ASN or local
confederation identifier (ASN) if confederations are used. confederation identifier (ASN) if confederations are used.
skipping to change at page 7, line 27 skipping to change at page 7, line 27
| Point | | | | Point | | |
+----------+---------------------------+----------+ +----------+---------------------------+----------+
| 1101 | Peer Node Segment | variable | | 1101 | Peer Node Segment | variable |
| | Identifier (Peer-Node-SID)| | | | Identifier (Peer-Node-SID)| |
| 1102 | Peer Adjacency Segment | variable | | 1102 | Peer Adjacency Segment | variable |
| | Identifier (Peer-Adj-SID) | | | | Identifier (Peer-Adj-SID) | |
| 1103 | Peer Set Segment | variable | | 1103 | Peer Set Segment | variable |
| | Identifier (Peer-Set-SID) | | | | Identifier (Peer-Set-SID) | |
+----------+---------------------------+----------+ +----------+---------------------------+----------+
Figure 1: BGP-LS TLV code points for BGP-PE Figure 1: BGP-LS TLV code points for BGP-EPE
Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format Peer-Node-SID, Peer-Adj-SID and Peer-Set-SID have all the same format
defined here below: defined here below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Weight | Reserved | | Flags | Weight | Reserved |
skipping to change at page 16, line 31 skipping to change at page 16, line 31
| 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 |
| 1101 | Peer-Node-SID | Section 4.3 | | 1101 | Peer-Node-SID | Section 4.3 |
| 1102 | Peer-Adj-SID | Section 4.3 | | 1102 | Peer-Adj-SID | Section 4.3 |
| 1103 | Peer-Set-SID | Section 4.3 | | 1103 | Peer-Set-SID | Section 4.3 |
+---------------------+--------------------------+-------------+ +---------------------+--------------------------+-------------+
Table 1: Summary Table of BGP-LS Codepoints for BGP-PE Table 1: Summary Table of BGP-LS Codepoints for BGP-EPE
8. Manageability Considerations 8. Manageability Considerations
TBD TBD
9. Security Considerations 9. Security Considerations
[RFC7752] defines BGP-LS NLRIs to which the extensions defined in [RFC7752] defines BGP-LS NLRIs to which the extensions defined in
this document apply. this document apply.
 End of changes. 7 change blocks. 
7 lines changed or deleted 7 lines changed or added

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