draft-ietf-idr-bgp-ls-segment-routing-ext-10.txt   draft-ietf-idr-bgp-ls-segment-routing-ext-11.txt 
Inter-Domain Routing S. Previdi, Ed. Inter-Domain Routing S. Previdi
Internet-Draft Internet-Draft Huawei Technologies
Intended status: Standards Track K. Talaulikar Intended status: Standards Track K. Talaulikar
Expires: April 22, 2019 C. Filsfils Expires: April 25, 2019 C. Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
M. Chen M. Chen
Huawei Technologies Huawei Technologies
October 19, 2018 October 22, 2018
BGP Link-State extensions for Segment Routing BGP Link-State extensions for Segment Routing
draft-ietf-idr-bgp-ls-segment-routing-ext-10 draft-ietf-idr-bgp-ls-segment-routing-ext-11
Abstract Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end Segment Routing (SR) allows for a flexible definition of end-to-end
paths by encoding paths as sequences of topological sub-paths, called paths by encoding paths as sequences of topological sub-paths, called
"segments". These segments are advertised by routing protocols e.g. "segments". These segments are advertised by routing protocols e.g.
by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within
IGP topologies. IGP topologies.
This draft defines extensions to the BGP Link-state address-family in This draft defines extensions to the BGP Link-state address-family in
skipping to change at page 1, line 49 skipping to change at page 1, line 49
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 April 22, 2019. This Internet-Draft will expire on April 25, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 5, line 24 skipping to change at page 5, line 24
global SID administration. global SID administration.
2. BGP-LS Extensions for Segment Routing 2. BGP-LS Extensions for Segment Routing
This document defines SR extensions to BGP-LS and specifies the TLVs This document defines SR extensions to BGP-LS and specifies the TLVs
and sub-TLVs for advertising SR information within the BGP-LS and sub-TLVs for advertising SR information within the BGP-LS
Attribute. Section 2.4 and Section 2.5 illustrates the equivalent Attribute. Section 2.4 and Section 2.5 illustrates the equivalent
TLVs and sub-TLVs in IS-IS, OSPFv2 and OSPFv3 protocols. TLVs and sub-TLVs in IS-IS, OSPFv2 and OSPFv3 protocols.
BGP-LS [RFC7752] defines the BGP-LS NLRI that can be a Node NLRI, a BGP-LS [RFC7752] defines the BGP-LS NLRI that can be a Node NLRI, a
Link NLRI or a Prefix NLRI. The corresponding BGP-LS attribute is a Link NLRI or a Prefix NLRI. BGP-LS [RFC7752] defines the TLVs that
Node Attribute, a Link Attribute or a Prefix Attribute. BGP-LS map link-state information to BGP-LS NLRI within the BGP-LS
[RFC7752] defines the TLVs that map link-state information to BGP-LS Attribute. This document adds additional BGP-LS Attribute TLVs in
NLRI and the BGP-LS attribute. This document adds additional BGP-LS order to encode SR information. It does not introduce any changes to
attribute TLVs in order to encode SR information. It does not the encoding of the BGP-LS NLRIs.
introduce any changes to the encoding of the BGP-LS NLRIs.
Some of the TLVs defined in this document contain fields (e.g. flags) Some of the TLVs defined in this document contain fields (e.g. flags)
whose semantics need to be interpreted accordingly to the respective whose semantics need to be interpreted accordingly to the respective
underlying IS-IS, OSPFv2 or OSPFv3 protocol. The receiver of the underlying IS-IS, OSPFv2 or OSPFv3 protocol. The receiver of the
BGP-LS update for any of the NLRIs MUST check the Protocol-ID of the BGP-LS update for any of the NLRIs MUST check the Protocol-ID of the
NLRI and refer to the underlying protocol specification in order to NLRI and refer to the underlying protocol specification in order to
parse such fields. The individual field descriptions in the sub- parse such fields. The individual field descriptions in the sub-
sections below point to the relevant underlying protocol sections below point to the relevant underlying protocol
specifications for such fields. specifications for such fields.
skipping to change at page 6, line 17 skipping to change at page 6, line 17
+-----------------+----------+---------------+ +-----------------+----------+---------------+
| SID/Label | variable | Section 2.1.1 | | SID/Label | variable | Section 2.1.1 |
| SR Capabilities | variable | Section 2.1.2 | | SR Capabilities | variable | Section 2.1.2 |
| SR Algorithm | variable | Section 2.1.3 | | SR Algorithm | variable | Section 2.1.3 |
| SR Local Block | variable | Section 2.1.4 | | SR Local Block | variable | Section 2.1.4 |
| SRMS Preference | variable | Section 2.1.5 | | SRMS Preference | variable | Section 2.1.5 |
+-----------------+----------+---------------+ +-----------------+----------+---------------+
Table 1: Node Attribute TLVs Table 1: Node Attribute TLVs
These TLVs can ONLY be added to the Node Attribute associated with These TLVs can ONLY be added to the BGP-LS Attribute associated with
the Node NLRI that originates the corresponding underlying IGP TLV/ the Node NLRI that originates the corresponding underlying IGP TLV/
sub-TLV described below. sub-TLV described below.
2.1.1. SID/Label Sub-TLV 2.1.1. SID/Label Sub-TLV
The SID/Label TLV is used as sub-TLV by the SR-Capabilities The SID/Label TLV is used as sub-TLV by the SR-Capabilities
(Section 2.1.2) and SRLB (Section 2.1.4) TLVs and has the following (Section 2.1.2) and SRLB (Section 2.1.4) TLVs and has the following
format: format:
0 1 2 3 0 1 2 3
skipping to change at page 11, line 5 skipping to change at page 11, line 5
+----------------------------------------+----------+---------------+ +----------------------------------------+----------+---------------+
| Adjacency Segment Identifier (Adj-SID) | variable | Section 2.2.1 | | Adjacency Segment Identifier (Adj-SID) | variable | Section 2.2.1 |
| TLV | | | | TLV | | |
| LAN Adjacency Segment Identifier (Adj- | variable | Section 2.2.2 | | LAN Adjacency Segment Identifier (Adj- | variable | Section 2.2.2 |
| SID) TLV | | | | SID) TLV | | |
| L2 Bundle Member TLV | variable | Section 2.2.3 | | L2 Bundle Member TLV | variable | Section 2.2.3 |
+----------------------------------------+----------+---------------+ +----------------------------------------+----------+---------------+
Table 2: Link Attribute TLVs Table 2: Link Attribute TLVs
These TLVs can ONLY be added to the Link Attribute associated with These TLVs can ONLY be added to the BGP-LS Attribute associated with
the link whose local node originates the corresponding underlying IGP the Link NLRI whose local node originates the corresponding
TLV/sub-TLV described below. underlying IGP TLV/sub-TLV described below.
For a LAN, normally a node only announces its adjacency to the IS-IS For a LAN, normally a node only announces its adjacency to the IS-IS
pseudo-node (or the equivalent OSPF Designated and Backup Designated pseudo-node (or the equivalent OSPF Designated and Backup Designated
Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN
Adjacency Segment TLV allows a node to announce adjacencies to all Adjacency Segment TLV allows a node to announce adjacencies to all
other nodes attached to the LAN in a single instance of the BGP-LS other nodes attached to the LAN in a single instance of the BGP-LS
Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI
would need to be originated for each additional adjacency in order to would need to be originated for each additional adjacency in order to
advertise the SR TLVs for these neighbor adjacencies. advertise the SR TLVs for these neighbor adjacencies.
skipping to change at page 14, line 21 skipping to change at page 14, line 21
| 1089 | Maximum link bandwidth | [RFC7752] | | 1089 | Maximum link bandwidth | [RFC7752] |
| 1090 | Max. reservable link | [RFC7752] | | 1090 | Max. reservable link | [RFC7752] |
| | bandwidth | | | | bandwidth | |
| 1091 | Unreserved bandwidth | [RFC7752] | | 1091 | Unreserved bandwidth | [RFC7752] |
| 1092 | TE default metric | [RFC7752] | | 1092 | TE default metric | [RFC7752] |
| 1093 | Link protection type | [RFC7752] | | 1093 | Link protection type | [RFC7752] |
| 1099 | Adjacency Segment | Section 2.2.1 | | 1099 | Adjacency Segment | Section 2.2.1 |
| | Identifier (Adj-SID) TLV | | | | Identifier (Adj-SID) TLV | |
| 1100 | LAN Adjacency Segment | Section 2.2.2 | | 1100 | LAN Adjacency Segment | Section 2.2.2 |
| | Identifier (Adj-SID) TLV | | | | Identifier (Adj-SID) TLV | |
| 1104 | Unidirectional link delay | [I-D.ietf-idr-te-pm-bgp] | | 1114 | Unidirectional link delay | [I-D.ietf-idr-te-pm-bgp] |
| 1105 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | | 1115 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] |
| | link delay | |
| 1106 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] |
| | link delay | | | | link delay | |
| 1107 | Unidirectional packet loss | [I-D.ietf-idr-te-pm-bgp] | | 1116 | Unidirectional Delay | [I-D.ietf-idr-te-pm-bgp] |
| 1108 | Unidirectional residual | [I-D.ietf-idr-te-pm-bgp] | | | Variation | |
| 1117 | Unidirectional packet loss | [I-D.ietf-idr-te-pm-bgp] |
| 1118 | Unidirectional residual | [I-D.ietf-idr-te-pm-bgp] |
| | bandwidth | | | | bandwidth | |
| 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] | | 1119 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] |
| | bandwidth | | | | bandwidth | |
| 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] | | 1120 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] |
| | utilization | | | | utilization | |
+-----------+----------------------------+--------------------------+ +-----------+----------------------------+--------------------------+
Table 3: L2 Bundle Member Link Attribute TLVs Table 3: BGP-LS Attribute TLVs also used as sub-TLVs of L2 Bundle
Member Attribute TLV
2.3. Prefix Attribute TLVs 2.3. Prefix Attribute TLVs
The following Prefix Attribute TLVs are defined: The following Prefix Attribute TLVs are defined:
+------------------------+----------+---------------+ +------------------------+----------+---------------+
| Description | Length | Section | | Description | Length | Section |
+------------------------+----------+---------------+ +------------------------+----------+---------------+
| Prefix SID | variable | Section 2.3.1 | | Prefix SID | variable | Section 2.3.1 |
| Range | variable | Section 2.3.4 | | Range | variable | Section 2.3.4 |
| Prefix Attribute Flags | variable | Section 2.3.2 | | Prefix Attribute Flags | variable | Section 2.3.2 |
| Source Router-ID | variable | Section 2.3.3 | | Source Router-ID | variable | Section 2.3.3 |
+------------------------+----------+---------------+ +------------------------+----------+---------------+
Table 4: Prefix Attribute TLVs Table 4: Prefix Attribute TLVs
These TLVs can ONLY be added to the Prefix Attribute associated with These TLVs can ONLY be added to the BGP-LS Attribute associated with
the prefix whose local node originates the corresponding underlying the Prefix NLRI whose local node originates the corresponding
IGP TLV/sub-TLV described below. underlying IGP TLV/sub-TLV described below.
2.3.1. Prefix-SID TLV 2.3.1. Prefix-SID TLV
The Prefix-SID TLV is used in order to advertise information related The Prefix-SID TLV is used in order to advertise information related
to a Prefix-SID. This information is originated in: to a Prefix-SID. This information is originated in:
o IS-IS, as defined by the Prefix-SID TLV in o IS-IS, as defined by the Prefix-SID TLV in
[I-D.ietf-isis-segment-routing-extensions]. [I-D.ietf-isis-segment-routing-extensions].
o OSPFv2 and OSPFv3, as defined by the Prefix-SID TLV in o OSPFv2 and OSPFv3, as defined by the Prefix-SID TLV in
skipping to change at page 24, line 9 skipping to change at page 24, line 9
Email: ginsberg@cisco.com Email: ginsberg@cisco.com
Acee Lindem Acee Lindem
Cisco Systems Cisco Systems
Email: acee@cisco.com Email: acee@cisco.com
Saikat Ray Saikat Ray
Individual Individual
Email: raysaikat@gmail.com Email: raysaikat@gmail.com
Jeff Tantsura Jeff Tantsura
Nuage Networks Apstra Inc.
Email: jefftant.ietf@gmail.com Email: jefftant.ietf@gmail.com
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Jeffrey Haas and Aijun Wang for their The authors would like to thank Jeffrey Haas, Aijun Wang and Robert
review of this document and their comments. Raszuk for their review of this document and their comments.
9. References 9. References
9.1. Normative References 9.1. Normative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C. Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C.
Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering
Performance Metric Extensions", draft-ietf-idr-te-pm- Performance Metric Extensions", draft-ietf-idr-te-pm-
bgp-13 (work in progress), October 2018. bgp-14 (work in progress), October 2018.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-19 (work in progress), July segment-routing-extensions-19 (work in progress), July
2018. 2018.
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] [I-D.ietf-ospf-ospfv3-segment-routing-extensions]
Psenak, P., Filsfils, C., Previdi, S., Gredler, H., Psenak, P. and S. Previdi, "OSPFv3 Extensions for Segment
Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 Routing", draft-ietf-ospf-ospfv3-segment-routing-
Extensions for Segment Routing", draft-ietf-ospf-ospfv3- extensions-16 (work in progress), October 2018.
segment-routing-extensions-15 (work in progress), August
2018.
[I-D.ietf-ospf-segment-routing-extensions] [I-D.ietf-ospf-segment-routing-extensions]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPF Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
Extensions for Segment Routing", draft-ietf-ospf-segment- Extensions for Segment Routing", draft-ietf-ospf-segment-
routing-extensions-25 (work in progress), April 2018. routing-extensions-25 (work in progress), April 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,
skipping to change at page 28, line 24 skipping to change at page 28, line 24
[30] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [30] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-4 routing-extensions-12#section-4
[31] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [31] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-2.1 routing-extensions-12#section-2.1
[32] http://tools.ietf.org/html/RFC8362#section-3.1 [32] http://tools.ietf.org/html/RFC8362#section-3.1
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi
Via Del Serafico, 200 Huawei Technologies
Rome 00142 Rome
Italy Italy
Email: stefano@previdi.net Email: stefano@previdi.net
Ketan Talaulikar Ketan Talaulikar
Cisco Systems, Inc. Cisco Systems, Inc.
S.No. 154/6, Phase I, Hinjawadi
Pune 411 057
India India
Email: ketant@cisco.com Email: ketant@cisco.com
Clarence Filsfils Clarence Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
Brussels Brussels
Belgium Belgium
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
 End of changes. 20 change blocks. 
42 lines changed or deleted 38 lines changed or added

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