draft-ietf-idr-bgp-ls-segment-routing-ext-01.txt   draft-ietf-idr-bgp-ls-segment-routing-ext-02.txt 
Inter-Domain Routing S. Previdi, Ed. Inter-Domain Routing S. Previdi, Ed.
Internet-Draft P. Psenak Internet-Draft P. Psenak
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: August 13, 2017 Cisco Systems, Inc. Expires: December 27, 2017 Cisco Systems, Inc.
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
M. Chen M. Chen
Huawei Technologies Huawei Technologies
J. Tantsura June 25, 2017
Individual
February 9, 2017
BGP Link-State extensions for Segment Routing BGP Link-State extensions for Segment Routing
draft-ietf-idr-bgp-ls-segment-routing-ext-01 draft-ietf-idr-bgp-ls-segment-routing-ext-02
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 within IGP topologies by encoding paths as sequences of paths within IGP topologies by encoding paths as sequences of
topological sub-paths, called "segments". These segments are topological sub-paths, called "segments". These segments are
advertised by the link-state routing protocols (IS-IS, OSPF and advertised by the link-state routing protocols (IS-IS, OSPF and
OSPFv3). OSPFv3).
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 2, line 4 skipping to change at page 1, line 47
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 August 13, 2017.
This Internet-Draft will expire on December 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 26 skipping to change at page 2, line 25
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. BGP-LS Extensions for Segment Routing . . . . . . . . . . . . 5 2. BGP-LS Extensions for Segment Routing . . . . . . . . . . . . 5
2.1. Node Attributes TLVs . . . . . . . . . . . . . . . . . . 5 2.1. Node Attributes TLVs . . . . . . . . . . . . . . . . . . 5
2.1.1. SR-Capabilities TLV . . . . . . . . . . . . . . . . . 5 2.1.1. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . 5
2.1.2. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . 6 2.1.2. SR-Capabilities TLV . . . . . . . . . . . . . . . . . 6
2.1.3. SR Local Block TLV . . . . . . . . . . . . . . . . . 7 2.1.3. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . 7
2.1.4. SRMS Preference TLV . . . . . . . . . . . . . . . . . 7 2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 7
2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 8 2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 8
2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 9 2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 9
2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 9 2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 10
2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 10 2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 10
2.3.1. Prefix-SID TLV . . . . . . . . . . . . . . . . . . . 11 2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 11
2.3.2. IPv6 Prefix-SID TLV . . . . . . . . . . . . . . . . . 12 2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 13
2.3.3. IGP Prefix Attributes TLV . . . . . . . . . . . . . . 13 2.3.1. Prefix-SID TLV . . . . . . . . . . . . . . . . . . . 14
2.3.4. Source Router Identifier (Source Router-ID) TLV . . . 14 2.3.2. IGP Prefix Attributes TLV . . . . . . . . . . . . . . 15
2.3.5. Range TLV . . . . . . . . . . . . . . . . . . . . . . 14 2.3.3. Source Router Identifier (Source Router-ID) TLV . . . 15
2.3.6. Binding SID TLV . . . . . . . . . . . . . . . . . . . 15 2.3.4. Range TLV . . . . . . . . . . . . . . . . . . . . . . 16
2.3.7. Binding SID SubTLVs . . . . . . . . . . . . . . . . . 16 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 17
2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 22 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs . . 18
2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs . . 23 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19
3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.1. Advertisement of a IS-IS Prefix SID TLV . . . . . . . . . 19
3.1. Advertisement of a IS-IS Prefix SID TLV . . . . . . . . . 25 3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV . . . . . . 19
3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV . . . . . . 25
3.3. Advertisement of a range of prefix-to-SID mappings in 3.3. Advertisement of a range of prefix-to-SID mappings in
OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . 26 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 26 3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 20
3.5. Advertisement of a path and its attributes from IS-IS 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 20
protocol . . . . . . . . . . . . . . . . . . . . . . . . 26 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
3.6. Advertisement of a path and its attributes from 5.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 21
OSPFv2/OSPFv3 protocol . . . . . . . . . . . . . . . . . 27 6. Manageability Considerations . . . . . . . . . . . . . . . . 22
4. Implementation Status . . . . . . . . . . . . . . . . . . . . 27 6.1. Operational Considerations . . . . . . . . . . . . . . . 22
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 6.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 22
5.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 28
6. Manageability Considerations . . . . . . . . . . . . . . . . 29 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22
6.1. Operational Considerations . . . . . . . . . . . . . . . 29 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 29 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 30 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 30 10.1. Normative References . . . . . . . . . . . . . . . . . . 23
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 10.2. Informative References . . . . . . . . . . . . . . . . . 24
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 30 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 24
10.1. Normative References . . . . . . . . . . . . . . . . . . 30 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
10.2. Informative References . . . . . . . . . . . . . . . . . 31
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
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 combining sub-paths called "segments". A segment can paths by combining sub-paths called "segments". A segment can
represent any instruction, topological or service-based. A segment represent any instruction, topological or service-based. A segment
can have a local semantic to an SR node or global within a domain. can have a local semantic to an SR node or global within a domain.
Within IGP topologies an SR path is encoded as a sequence of Within IGP topologies an SR path is encoded as a sequence of
topological sub-paths, called "IGP segments". These segments are topological sub-paths, called "IGP segments". These segments are
advertised by the link-state routing protocols (IS-IS, OSPF and advertised by the link-state routing protocols (IS-IS, OSPF and
skipping to change at page 5, line 16 skipping to change at page 5, line 16
This document describes extensions to BGP-LS to advertise the SR This document describes extensions to BGP-LS to advertise the SR
information. An external component (e.g., a controller) then can information. An external component (e.g., a controller) then can
collect SR information in the "northbound" direction across IGP areas collect SR information in the "northbound" direction across IGP areas
or ASes and construct the end-to-end path (with its associated SIDs) or ASes and construct the end-to-end path (with its associated SIDs)
that need to be applied to an incoming packet to achieve the desired that need to be applied to an incoming packet to achieve the desired
end-to-end forwarding. end-to-end forwarding.
2. BGP-LS Extensions for Segment Routing 2. BGP-LS Extensions for Segment Routing
This document defines IGP SR extensions BGP-LS TLVs and Sub-TLVs. This document defines IGP SR extensions BGP-LS TLVs and sub-TLVs.
Section 2.4 and Section 2.5 illustrates the equivalent TLVs and Sub- Section 2.4 and Section 2.5 illustrates the equivalent TLVs and sub-
TLVs in IS-IS, OSPF and OSPFv3 protocols. TLVs in IS-IS, OSPF 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. The corresponding BGP-LS attribute is a
Node Attribute, a Link Attribute or a Prefix Attribute. BGP-LS Node Attribute, a Link Attribute or a Prefix Attribute. BGP-LS
[RFC7752] defines the TLVs that map link-state information to BGP-LS [RFC7752] defines the TLVs that map link-state information to BGP-LS
NLRI and the BGP-LS attribute. This document adds additional BGP-LS NLRI and the BGP-LS attribute. This document adds additional BGP-LS
attribute TLVs in order to encode SR information. attribute TLVs in order to encode SR information.
2.1. Node Attributes TLVs 2.1. Node Attributes TLVs
The following Node Attribute TLVs are defined: The following Node Attribute TLVs are defined:
+----------------+-----------------+----------+---------------+ +----------------+-----------------+----------+---------------+
| TLV Code Point | Description | Length | Section | | TLV Code Point | Description | Length | Section |
+----------------+-----------------+----------+---------------+ +----------------+-----------------+----------+---------------+
| 1034 | SR Capabilities | variable | Section 2.1.1 | | 1161 | SID/Label | variable | Section 2.1.1 |
| 1035 | SR Algorithm | variable | Section 2.1.2 | | 1034 | SR Capabilities | variable | Section 2.1.2 |
| 1036 | SR Local Block | variable | Section 2.1.3 | | 1035 | SR Algorithm | variable | Section 2.1.3 |
| 1037 | SRMS Preference | variable | Section 2.1.4 | | 1036 | SR Local Block | variable | Section 2.1.4 |
| 1037 | 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 Node Attribute associated with
the Node NLRI that originates the corresponding SR TLV. the Node NLRI that originates the corresponding SR TLV.
2.1.1. SR-Capabilities TLV 2.1.1. SID/Label Sub-TLV
The SR Capabilities sub-TLV has following format: 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 following
format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where:
Type: TBD, suggested value 1161.
Length: Variable, 3 or 4 bytes
SID/Label: If length is set to 3, then the 20 rightmost bits
represent a label. If length is set to 4, then the value
represents a 32 bit SID.
The receiving router MUST ignore the SID/Label sub-TLV if the
length is other then 3 or 4.
2.1.2. SR-Capabilities TLV
The SR-Capabilities TLV is used in order to advertise the node's
Segment Routing Global Base (SRGB) as originated in:
o IS-IS, as defined by the SR-Capabilities TLV in
[I-D.ietf-isis-segment-routing-extensions].
o OSPF/OSPFv3, as defined by the SID/Label Range TLV in
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
The SR Capabilities TLV has following format:
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 | RESERVED | | Flags | RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Range Size | | Range Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// SID/Label Sub-TLV (variable) // // SID/Label sub-TLV (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD, suggested value 1034. Type: TBD, suggested value 1034.
Length: Variable. Length: Variable.
Flags: 1 octet of flags as defined in Flags: 1 octet of flags as defined in
[I-D.ietf-isis-segment-routing-extensions] and [I-D.ietf-isis-segment-routing-extensions].
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
One or more entries, each of which have the following format: One or more entries, each of which have the following format:
Range Size: 3 octet value indicating the number of labels in Range Size: 3 octet value indicating the number of labels in
the range. the range.
SID/Label sub-TLV (as defined in Section 2.3.7.2). SID/Label sub-TLV (as defined in Section 2.1.1).
2.1.2. SR-Algorithm TLV Multiple SRGB entries are encoded within the same SR Capabilities
TLV.
2.1.3. SR-Algorithm TLV
The SR-Algorithm TLV has the following format: The SR-Algorithm TLV has the following format:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Algorithm 1 | Algorithm... | Algorithm N | | | Algorithm 1 | Algorithm... | Algorithm N | |
+- -+ +- -+
skipping to change at page 7, line 7 skipping to change at page 7, line 43
+ + + +
where: where:
Type: TBD, suggested value 1035. Type: TBD, suggested value 1035.
Length: Variable. Length: Variable.
Algorithm: 1 octet identifying the algorithm. Algorithm: 1 octet identifying the algorithm.
2.1.3. SR Local Block TLV 2.1.4. SR Local Block TLV
The SR Local Block (SRLB) Sub-TLV contains the range of labels the The SR Local Block (SRLB) TLV contains the range of labels the node
node has reserved for local SIDs. Local SIDs are used, e.g., in IGP has reserved for local SIDs. Local SIDs are used, e.g., in IGP (IS-
(IS-IS, OSPF) for Adjacency-SIDs, and may also be allocated by other IS, OSPF) for Adjacency-SIDs, and may also be allocated by other
components than IGP protocols. As an example, an application or a components than IGP protocols. As an example, an application or a
controller may instruct a node to allocate a specific local SID. controller may instruct a node to allocate a specific local SID.
Therefore, in order for such applications or controllers to know the Therefore, in order for such applications or controllers to know the
range of local SIDs available, it is required that the node range of local SIDs available, it is required that the node
advertises its SRLB. advertises its SRLB.
The SRLB TLV has the following format: The SRLB TLV has the following format:
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 | RESERVED | | Flags | RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Range Size | | Range Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// SID/Label Sub-TLV (variable) // // SID/Label sub-TLV (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD, suggested value 1036. Type: TBD, suggested value 1036.
Length: Variable. Length: Variable.
Flags: 1 octet of flags. None are defined at this stage. Flags: 1 octet of flags. None are defined at this stage.
One or more entries, each of which have the following format: One or more entries, each of which have the following format:
Range Size: 3 octet value indicating the number of labels in Range Size: 3 octet value indicating the number of labels in
the range. the range.
SID/Label sub-TLV (as defined in Section 2.3.7.2). SID/Label sub-TLV (as defined in Section 2.1.1).
2.1.4. SRMS Preference TLV Multiple SRLB entries are encoded within the same SRLB TLV.
The Segment Routing Mapping Server (SRMS) Preference sub-TLV is used 2.1.5. SRMS Preference TLV
in order to associate a preference with SRMS advertisements from a
The Segment Routing Mapping Server (SRMS) Preference TLV is used in
order to associate a preference with SRMS advertisements from a
particular source. particular source.
The SRMS Preference sub-TLV has following format: The SRMS Preference TLV has following format:
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preference | | Preference |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: TBD, suggested value 1037. Type: TBD, suggested value 1037.
Length: 1. Length: 1.
Preference: 1 octet. Unsigned 8 bit SRMS preference. Preference: 1 octet. Unsigned 8 bit SRMS preference.
The use of the SRMS Preference TLV is defined in The use of the SRMS Preference TLV is defined in
[I-D.ietf-isis-segment-routing-extensions]. [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
2.2. Link Attribute TLVs 2.2. Link Attribute TLVs
The following Link Attribute TLVs are are defined: The following Link Attribute TLVs are are defined:
+-----------+----------------------------+----------+---------------+ +-----------+----------------------------+----------+---------------+
| TLV Code | Description | Length | Section | | TLV Code | Description | Length | Section |
| Point | | | | | Point | | | |
+-----------+----------------------------+----------+---------------+ +-----------+----------------------------+----------+---------------+
| 1099 | Adjacency Segment | variable | Section 2.2.1 | | 1099 | Adjacency Segment | variable | Section 2.2.1 |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1100 | LAN Adjacency Segment | variable | Section 2.2.2 | | 1100 | LAN Adjacency Segment | variable | Section 2.2.2 |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1172 | 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 Link Attribute associated with
the link whose local node originates the corresponding TLV. the link whose local node originates the corresponding TLV.
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
skipping to change at page 9, line 39 skipping to change at page 10, line 39
Weight: Weight used for load-balancing purposes. Weight: Weight used for load-balancing purposes.
SID/Index/Label: Label or index value depending on the flags SID/Index/Label: Label or index value depending on the flags
setting as defined in [I-D.ietf-isis-segment-routing-extensions], setting as defined in [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and [I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-ospf-ospfv3-segment-routing-extensions].
2.2.2. LAN Adjacency SID TLV 2.2.2. LAN Adjacency SID TLV
The LAN Adjacency SID (LAN-Adj-SID-SID) has the following format: The LAN Adjacency SID (LAN-Adj-SID-SID) TLV has the following format:
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 10, line 41 skipping to change at page 11, line 41
[I-D.ietf-ospf-segment-routing-extensions] and [I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-ospf-ospfv3-segment-routing-extensions].
Weight: Weight used for load-balancing purposes. Weight: Weight used for load-balancing purposes.
SID/Index/Label: Label or index value depending on the flags SID/Index/Label: Label or index value depending on the flags
setting as defined in [I-D.ietf-isis-segment-routing-extensions], setting as defined in [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and [I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-ospf-ospfv3-segment-routing-extensions].
2.2.3. L2 Bundle Member
The L2 Bundle Member Attribute TLV identifies an L2 Bundle Member
link which in turn is associated with a parent L3 link. The L3 link
is described by the Link NLRI defined in [RFC7752] and the L2 Bundle
Member Attribute TLV is associated with the Link NLRI. The TLV MAY
include sub-TLVs which describe attributes associated with the bundle
member. The identified bundle member represents a unidirectional
path from the originating router to the neighbor specified in the
parent L3 Link. Multiple L2 Bundle Member Attribute TLVs MAY be
associated with a Link NLRI.
The L2 Bundle Member Attribute TLV has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| L2 Bundle Member Descriptor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Link attribute sub-TLVs(variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where:
Type: TBD, suggested value 1172.
Length: Variable.
L2 Bundle Member Descriptor: A Link Local Identifier as defined in
[RFC4202].
Link attributes for L2 Bundle Member Links are advertised as sub-TLVs
of the L2Bundle Member Attribute TLV. The sub-TLVs are identical to
existing BGP-LS TLVs as identified in the table below.
+-----------+----------------------------+--------------------------+
| TLV Code | Description | Reference Document |
| Point | | |
+-----------+----------------------------+--------------------------+
| 1088 | Administrative group | [RFC7752] |
| | (color) | |
| 1089 | Maximum link bandwidth | [RFC7752] |
| 1090 | Max. reservable link | [RFC7752] |
| | bandwidth | |
| 1091 | Unreserved bandwidth | [RFC7752] |
| 1092 | TE default metric | [RFC7752] |
| 1093 | Link protection type | [RFC7752] |
| 1099 | Adjacency Segment | Section 2.2.1 |
| | Identifier (Adj-SID) TLV | |
| 1100 | LAN Adjacency Segment | Section 2.2.2 |
| | Identifier (Adj-SID) TLV | |
| 1104 | Unidirectional link delay | [I-D.ietf-idr-te-pm-bgp] |
| 1105 | 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 | |
| 1107 | Unidirectional packet loss | [I-D.ietf-idr-te-pm-bgp] |
| 1108 | Unidirectional residual | [I-D.ietf-idr-te-pm-bgp] |
| | bandwidth | |
| 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] |
| | bandwidth | |
| 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] |
| | utilization | |
+-----------+----------------------------+--------------------------+
Table 3: L2 Bundle Member Link Attribute TLVs
2.3. Prefix Attribute TLVs 2.3. Prefix Attribute TLVs
The following Prefix Attribute TLVs and Sub-TLVs are defined: The following Prefix Attribute TLVs and sub-TLVs are defined:
+----------------+-----------------------+----------+---------------+ +----------------+-----------------------+----------+---------------+
| TLV Code Point | Description | Length | Section | | TLV Code Point | Description | Length | Section |
+----------------+-----------------------+----------+---------------+ +----------------+-----------------------+----------+---------------+
| 1158 | Prefix SID | variable | Section 2.3.1 | | 1158 | Prefix SID | variable | Section 2.3.1 |
| 1159 | Range | variable | Section 2.3.5 | | 1159 | Range | variable | Section 2.3.4 |
| 1160 | Binding SID | variable | Section 2.3.6 | | 1170 | IGP Prefix Attributes | variable | Section 2.3.2 |
| 1169 | IPv6 Prefix SID | variable | Section 2.3.2 | | 1171 | Source Router-ID | variable | Section 2.3.3 |
| 1170 | IGP Prefix Attributes | variable | Section 2.3.3 |
| 1171 | Source Router-ID | variable | Section 2.3.4 |
+----------------+-----------------------+----------+---------------+ +----------------+-----------------------+----------+---------------+
Table 3: Prefix Attribute TLVs Table 4: Prefix Attribute TLVs
+------------+-------------------------+----------+-----------------+
| TLV Code | Description | Length | Section |
| Point | | | |
+------------+-------------------------+----------+-----------------+
| 1161 | SID/Label TLV | variable | Section 2.3.7.2 |
| 1162 | ERO Metric TLV | 4 octets | Section 2.3.7.3 |
| 1163 | IPv4 ERO TLV | 8 octets | Section 2.3.7.4 |
| 1164 | IPv6 ERO TLV | 20 | Section 2.3.7.5 |
| | | octets | |
| 1165 | Unnumbered Interface ID | 12 | Section 2.3.7.6 |
| | ERO TLV | | |
| 1166 | IPv4 Backup ERO TLV | 8 octets | Section 2.3.7.7 |
| 1167 | IPv6 Backup ERO TLV | 10 | Section 2.3.7.8 |
| | | octets | |
| 1168 | Unnumbered Interface ID | 12 | Section 2.3.7.9 |
| | Backup ERO TLV | | |
+------------+-------------------------+----------+-----------------+
Table 4: Prefix Attribute - Binding SID Sub-TLVs
2.3.1. Prefix-SID TLV 2.3.1. Prefix-SID TLV
The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose
local node in the corresponding Prefix NLRI is the node that local node in the corresponding Prefix NLRI is the node that
originates the corresponding SR TLV. originates the corresponding SR TLV.
The Prefix-SID TLV is used in order to advertise a Prefix-SID as
originated in:
o IS-IS, as defined by the Prefix-SID TLV in
[I-D.ietf-isis-segment-routing-extensions].
o OSPF/OSPFv3, as defined by the Prefix-SID TLV in
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
The Prefix-SID has the following format: The Prefix-SID has the following format:
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 | Algorithm | Reserved | | Flags | Algorithm | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Index/Label (variable) | | SID/Index/Label (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, suggested value 1158. Type: TBD, suggested value 1158.
Length: Variable Length: Variable
Algorithm: 1 octet value identify the algorithm. Algorithm: 1 octet value identify the algorithm.
SID/Index/Label: Label or index value depending on the flags SID/Index/Label:
setting as defined in [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and * IS-IS: Label or index value as defined in
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-isis-segment-routing-extensions],
* OSPF: Label or index value as defined in
[I-D.ietf-ospf-segment-routing-extensions],
* OSPFv3: Label or index value as defined in
[I-D.ietf-ospf-ospfv3-segment-routing-extensions],
The Prefix-SID TLV includes a Flags field. In the context of BGP-LS, The Prefix-SID TLV includes a Flags field. In the context of BGP-LS,
the Flags field format and the semantic of each individual flag MUST the Flags field format and the semantic of each individual flag MUST
be taken from the corresponding source protocol (i.e.: the protocol be taken from the corresponding source protocol (i.e.: the protocol
of origin of the Prefix-SID being advertised in BGP-LS). of origin of the Prefix-SID being advertised in BGP-LS).
IS-IS Prefix-SID flags are defined in IS-IS Prefix-SID flags are defined in
[I-D.ietf-isis-segment-routing-extensions] section 2.1. [I-D.ietf-isis-segment-routing-extensions] section 2.1.
OSPF Prefix-SID flags are defined in OSPF Prefix-SID flags are defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5. [I-D.ietf-ospf-segment-routing-extensions] section 5.
OSPFv3 Prefix-SID flags are defined in OSPFv3 Prefix-SID flags are defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5. [I-D.ietf-ospf-segment-routing-extensions] section 5.
2.3.2. IPv6 Prefix-SID TLV 2.3.2. IGP Prefix Attributes TLV
The IPv6 Prefix-SID TLV can ONLY be added to the Prefix Attribute
whose local node in the corresponding Prefix NLRI is the node that
originates the corresponding SR TLV.
The IPv6 Prefix-SID has the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Algorithm | //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ //
// Sub-TLVs //
// //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where:
Type: TBD, suggested value 1169.
Length: 3 + length of Sub-TLVs.
Flags: 2 octet field of flags. None of them is defined at this
stage.
Algorithm: 1 octet value identify the algorithm as defined in
[I-D.previdi-isis-ipv6-prefix-sid].
Sub-TLVs: additional information encoded into the IPv6 Prefix-SID
Sub-TLV as defined in [I-D.previdi-isis-ipv6-prefix-sid].
The IPv6 Prefix-SID TLV is defined in
[I-D.previdi-isis-ipv6-prefix-sid].
2.3.3. IGP Prefix Attributes TLV
The IGP Prefix Attribute TLV carries IPv4/IPv6 prefix attribute flags The IGP Prefix Attribute TLV carries IPv4/IPv6 prefix attribute flags
as defined in [RFC7684] and [RFC7794]. as defined in [RFC7684] and [RFC7794].
The IGP Prefix Attribute TLV has the following format: The IGP Prefix Attribute TLV has the following format:
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 |
skipping to change at page 14, line 15 skipping to change at page 15, line 48
Length: variable. Length: variable.
Flags: a variable length flag field (according to the length Flags: a variable length flag field (according to the length
field). Flags are routing protocol specific (OSPF and IS-IS). field). Flags are routing protocol specific (OSPF and IS-IS).
OSPF flags are defined in [RFC7684] and IS-IS flags are defined in OSPF flags are defined in [RFC7684] and IS-IS flags are defined in
[RFC7794]. The receiver of the BGP-LS update, when inspecting the [RFC7794]. The receiver of the BGP-LS update, when inspecting the
IGP Prefix Attribute TLV, MUST check the Protocol-ID of the NLRI IGP Prefix Attribute TLV, MUST check the Protocol-ID of the NLRI
and refer to the protocol specification in order to parse the and refer to the protocol specification in order to parse the
flags. flags.
2.3.4. Source Router Identifier (Source Router-ID) TLV 2.3.3. Source Router Identifier (Source Router-ID) TLV
The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the
originator as defined in [RFC7794]. While defined in the IS-IS originator as defined in [RFC7794]. While defined in the IS-IS
protocol, the Source Router-ID TLV may be used to carry the OSPF protocol, the Source Router-ID TLV may be used to carry the OSPF
Router-ID of the prefix originator. Router-ID of the prefix originator.
The Source Router-ID TLV has the following format: The Source Router-ID TLV has the following format:
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
skipping to change at page 14, line 42 skipping to change at page 16, line 27
where: where:
Type: TBD, suggested value 1171. Type: TBD, suggested value 1171.
Length: 4 or 16. Length: 4 or 16.
IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address. IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address.
The semantic of the Source Router-ID TLV is defined in [RFC7794]. The semantic of the Source Router-ID TLV is defined in [RFC7794].
2.3.5. Range TLV 2.3.4. Range TLV
The Range TLV can ONLY be added to the Prefix Attribute whose local The Range TLV can ONLY be added to the Prefix Attribute whose local
node in the corresponding Prefix NLRI is the node that originates the node in the corresponding Prefix NLRI is the node that originates the
corresponding SR TLV. corresponding SR TLV.
When the range TLV is used in order to advertise a path to a prefix When the range TLV is used in order to advertise a range of prefix-
or a range of prefix-to-SID mappings, the Prefix-NLRI the Range TLV to-SID mappings as defined in
is attached to MUST be advertised as a non-routing prefix where no [I-D.ietf-ospf-segment-routing-extensions],
IGP metric TLV (TLV 1095) is attached. [I-D.ietf-ospf-ospfv3-segment-routing-extensions]and
[I-D.ietf-isis-segment-routing-extensions]. The Prefix-NLRI the
Range TLV is attached to MUST be advertised as a non-routing prefix
where no IGP metric TLV (TLV 1095) is attached.
The format of the Range TLV is as follows: The format of the Range TLV 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | RESERVED | Range Size | | Flags | RESERVED | Range Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Sub-TLVs // // sub-TLVs //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Figure 2: Range TLV format Figure 2: Range TLV format
Type: 1159 Type: 1159
Length is 4. Length is 4.
Flags: Only used when the source protocol is OSPF and defined in Flags: as defined in [I-D.ietf-ospf-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] section 4 and [I-D.ietf-ospf-ospfv3-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. [I-D.ietf-isis-segment-routing-extensions].
Range Size: 2 octets as defined in Range Size: 2 octets as defined in
[I-D.ietf-ospf-segment-routing-extensions] section 4. [I-D.ietf-ospf-segment-routing-extensions].
Within the Range TLV, the following SubTLVs are may be present:
Binding SID TLV, defined in Section 2.3.6
Prefix-SID TLV, defined in Section 2.3.1
SID/Label TLV, defined in Section 2.3.7.2
2.3.6. Binding SID TLV
The Binding SID TLV can be used in two ways:
o as a sub-TLV of the Range TLV
o as a Prefix Attribute TLV
The format of the Binding SID TLV is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Weight | Flags | RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// SubTLVs (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where:
Figure 3: Binding SID Sub-TLV format
Type is 1160
Length is variable
Weight and Flags are mapped to Weight and Flags defined in
[I-D.ietf-isis-segment-routing-extensions] section 2.4,
[I-D.ietf-ospf-segment-routing-extensions] section 4 and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4.
Sub-TLVs are defined in the following sections.
2.3.7. Binding SID SubTLVs
This section defines the Binding SID Sub-TLVs in BGP-LS to encode the
equivalent Sub-TLVs defined in
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
All ERO (Explicit Route Object) Sub-TLVs must immediately follow the
(SID)/Label Sub-TLV.
All Backup ERO Sub-TLVs must immediately follow the last ERO Sub-TLV.
2.3.7.1. Binding SID Prefix-SID Sub-TLV
When encoding IS-IS Mapping Server entries as defined in
[I-D.ietf-isis-segment-routing-extensions] the Prefix-SID TLV defined
in Section 2.3.1 is used as Sub-TLV in the Binding TLV.
2.3.7.2. SID/Label Sub-TLV
The SID/Label TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where:
Type: TBD, suggested value 1161.
Length: Variable, 3 or 4 bytes
SID/Label: If length is set to 3, then the 20 rightmost bits
represent a label. If length is set to 4, then the value
represents a 32 bit SID.
The receiving router MUST ignore the SID/Label Sub-TLV if the
length is other then 3 or 4.
2.3.7.3. ERO Metric Sub-TLV
The ERO Metric Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Metric (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
ERO Metric Sub-TLV format
where:
Type: TBD, suggested value 1162.
Length: Always 4
Metric: A 4 octet metric representing the aggregate IGP or TE path
cost.
2.3.7.4. IPv4 ERO Sub-TLV
The ERO Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 ERO Sub-TLV format
where:
Type: TBD, suggested value 1163
Length: 8 octets
Flags: 1 octet of flags as defined in:
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
IPv4 Address - the address of the explicit route hop.
2.3.7.5. IPv6 ERO Sub-TLV
The IPv6 ERO Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- -+
| |
+- IPv6 Address -+
| |
+- -+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 ERO Sub-TLV format
where:
Type: TBD, suggested value 1164
Length: 20 octets
Flags: 1 octet of flags as defined in:
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
IPv6 Address - the address of the explicit route hop.
2.3.7.6. Unnumbered Interface ID ERO Sub-TLV
The Unnumbered Interface-ID ERO Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Router ID (IPv4, 4 octet or IPv6, 16 octets) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where:
Unnumbered Interface ID ERO Sub-TLV format
Type: TBD, suggested value 1165.
Length: Variable (12 for IPv4 Router-ID or 24 for IPv6 Router-ID).
Flags: 1 octet of flags as defined in:
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
Router-ID: Router-ID of the next-hop.
Interface ID: is the identifier assigned to the link by the router
specified by the Router-ID.
2.3.7.7. IPv4 Backup ERO Sub-TLV
The IPv4 Backup ERO Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 Address (4 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 Backup ERO Sub-TLV format
where:
Type: TBD, suggested value 1166.
Length: 8 octets
Flags: 1 octet of flags as defined in:
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
IPv4 Address: Address of the explicit route hop.
2.3.7.8. IPv6 Backup ERO Sub-TLV
The IPv6 Backup ERO Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+- -+
| |
+- IPv6 Address -+
| |
+- -+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 Backup ERO Sub-TLV format
where:
Type: TBD, suggested value 1167.
Length: 8 octets
Flags: 1 octet of flags as defined in:
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
IPv6 Address: Address of the explicit route hop.
2.3.7.9. Unnumbered Interface ID Backup ERO Sub-TLV
The Unnumbered Interface-ID Backup ERO Sub-TLV has following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Router ID (IPv4, 4 octet or IPv6, 16 octets) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interface ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unnumbered Interface ID Backup ERO Sub-TLV format
where:
Type: TBD, suggested value 1168.
Length: Variable (12 for IPv4 Router-ID or 24 for IPv6 Router-ID).
Flags: 1 octet of flags as defined in:
[I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions].
Router-ID: Router-ID of the next-hop.
Interface ID: Identifier assigned to the link by the router Within the Range TLV, the Prefix-SID TLV (used as sub-TLV in this
specified by the Router-ID. context) MAY be present.
2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs
This section illustrate the IS-IS Segment Routing Extensions TLVs and This section illustrate the IS-IS Segment Routing Extensions TLVs and
Sub-TLVs mapped to the ones defined in this document. sub-TLVs mapped to the ones defined in this document.
The following table, illustrates for each BGP-LS TLV, its equivalence The following table, illustrates for each BGP-LS TLV, its equivalence
in IS-IS. in IS-IS.
+-----------+------------------------------+----------+-------------+ +-----------+------------------------------+----------+-------------+
| TLV Code | Description | Length | IS-IS TLV | | TLV Code | Description | Length | IS-IS TLV |
| Point | | | /Sub-TLV | | Point | | | /sub-TLV |
+-----------+------------------------------+----------+-------------+ +-----------+------------------------------+----------+-------------+
| 1034 | SR Capabilities | variable | 2 [1] | | 1034 | SR Capabilities | variable | 2 [1] |
| 1035 | SR Algorithm | variable | 19 [2] | | 1035 | SR Algorithm | variable | 19 [2] |
| 1099 | Adjacency Segment Identifier | variable | 31 [3] | | 1099 | Adjacency Segment Identifier | variable | 31 [3] |
| | (Adj-SID) TLV | | | | | (Adj-SID) TLV | | |
| 1100 | LAN Adjacency Segment | variable | 32 [4] | | 1100 | LAN Adjacency Segment | variable | 32 [4] |
| | Identifier (LAN-Adj-SID) TLV | | | | | Identifier (LAN-Adj-SID) TLV | | |
| 1158 | Prefix SID | variable | 3 [5] | | 1158 | Prefix SID | variable | 3 [5] |
| 1160 | Binding SID | variable | 149 [6] | | 1161 | SID/Label TLV | variable | 1 [6] |
| 1161 | SID/Label TLV | variable | 1 [7] | | 1170 | IGP Prefix Attributes | variable | 4 [7] |
| 1162 | ERO Metric TLV | 4 octets | 10 [8] | | 1171 | Source Router ID | variable | 11/12 [8] |
| 1163 | IPv4 ERO TLV | 5 octets | 11 [9] | | 1172 | L2 Bundle Member TLV | variable | 25 [9] |
| 1164 | IPv6 ERO TLV | 17 | 12 [10] |
| | | octets | |
| 1165 | Unnumbered Interface ID ERO | variable | 13 [11] |
| | TLV | | |
| 1166 | IPv4 Backup ERO TLV | 5 octets | 14 [12] |
| 1167 | IPv6 Backup ERO TLV | 17 | 15 [13] |
| | | octets | |
| 1168 | Unnumbered Interface ID | variable | 16 [14] |
| | Backup ERO TLV | | |
| 1169 | IPv6 Prefix SID | variable | 5 [15] |
| 1170 | IGP Prefix Attributes | variable | 4 [16] |
| 1171 | Source Router ID | variable | 11/12 [17] |
+-----------+------------------------------+----------+-------------+ +-----------+------------------------------+----------+-------------+
Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs
2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs
This section illustrate the OSPF and OSPFv3 Segment Routing This section illustrate the OSPF and OSPFv3 Segment Routing
Extensions TLVs and Sub-TLVs mapped to the ones defined in this Extensions TLVs and sub-TLVs mapped to the ones defined in this
document. document.
The following table, illustrates for each BGP-LS TLV, its equivalence The following table, illustrates for each BGP-LS TLV, its equivalence
in OSPF and OSPFv3. in OSPF and OSPFv3.
+------------+-----------------------------+----------+-------------+ +-----------+------------------------------+----------+-------------+
| TLV Code | Description | Length | OSPF TLV | | TLV Code | Description | Length | OSPF TLV |
| Point | | | /Sub-TLV | | Point | | | /sub-TLV |
+------------+-----------------------------+----------+-------------+ +-----------+------------------------------+----------+-------------+
| 1034 | SR Capabilities | variable | 9 [18] | | 1034 | SR Capabilities | variable | 9 [10] |
| 1035 | SR Algorithm | variable | 8 [19] | | 1035 | SR Algorithm | variable | 8 [11] |
| 1099 | Adjacency Segment | variable | 2 [20] | | 1099 | Adjacency Segment Identifier | variable | 2 [12] |
| | Identifier (Adj-SID) TLV | | | | | (Adj-SID) TLV | | |
| 1100 | LAN Adjacency Segment | variable | 3 [21] | | 1100 | LAN Adjacency Segment | variable | 3 [13] |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1158 | Prefix SID | variable | 2 [22] | | 1158 | Prefix SID | variable | 2 [14] |
| 1161 | SID/Label TLV | variable | 1 [23] | | 1161 | SID/Label TLV | variable | 1 [15] |
| 1162 | ERO Metric TLV | 4 octets | 8 [24] | +-----------+------------------------------+----------+-------------+
| 1163 | IPv4 ERO TLV | 8 octets | 4 [25] |
| 1165 | Unnumbered Interface ID ERO | 12 | 5 [26] |
| | TLV | octets | |
| 1166 | IPv4 Backup ERO TLV | 8 octets | 6 [27] |
| 1167 | Unnumbered Interface ID | 12 | 7 [28] |
| | Backup ERO TLV | octets | |
| 1167 | Unnumbered Interface ID | 12 | 7 [29] |
| | Backup ERO TLV | octets | |
+------------+-----------------------------+----------+-------------+
Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs
+------------+----------------------------+----------+--------------+ +-----------+-----------------------------+----------+--------------+
| TLV Code | Description | Length | OSPFv3 TLV | | TLV Code | Description | Length | OSPFv3 TLV |
| Point | | | /Sub-TLV | | Point | | | /sub-TLV |
+------------+----------------------------+----------+--------------+ +-----------+-----------------------------+----------+--------------+
| 1034 | SR Capabilities | variable | 9 [30] | | 1034 | SR Capabilities | variable | 9 [16] |
| 1035 | SR Algorithm | variable | 8 [31] | | 1035 | SR Algorithm | variable | 8 [17] |
| 1099 | Adjacency Segment | variable | 5 [32] | | 1099 | Adjacency Segment | variable | 5 [18] |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1100 | LAN Adjacency Segment | variable | 6 [33] | | 1100 | LAN Adjacency Segment | variable | 6 [19] |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1158 | Prefix SID | variable | 4 [34] | | 1158 | Prefix SID | variable | 4 [20] |
| 1161 | SID/Label TLV | variable | 3 [35] | | 1161 | SID/Label TLV | variable | 3 [21] |
| 1162 | ERO Metric TLV | 4 octets | 8 [36] | +-----------+-----------------------------+----------+--------------+
| 1163 | IPv4 ERO TLV | 8 octets | 9 [37] |
| 1164 | IPv6 ERO TLV | 20 | 8 [38] |
| | | octets | |
| 1165 | Unnumbered Interface ID | 12 | 11 [39] |
| | ERO TLV | octets | |
| 1166 | IPv4 Backup ERO TLV | 8 octets | 12 [40] |
| 1167 | IPv6 Backup ERO TLV | 20 | 13 [41] |
| | | octets | |
| 1167 | Unnumbered Interface ID | 12 | 14 [42] |
| | Backup ERO TLV | octets | |
+------------+----------------------------+----------+--------------+
Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs
3. Procedures 3. Procedures
The following sections describe the different operations for the The following sections describe the different operations for the
propagation of SR TLVs into BGP-LS. propagation of SR TLVs into BGP-LS.
3.1. Advertisement of a IS-IS Prefix SID TLV 3.1. Advertisement of a IS-IS Prefix SID TLV
skipping to change at page 26, line 14 skipping to change at page 19, line 52
the Prefix-SID TLV have the semantic defined in the Prefix-SID TLV have the semantic defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5 or [I-D.ietf-ospf-segment-routing-extensions] section 5 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5.
3.3. Advertisement of a range of prefix-to-SID mappings in OSPF 3.3. Advertisement of a range of prefix-to-SID mappings in OSPF
The advertisement of a range of prefix-to-SID mappings in OSPF has The advertisement of a range of prefix-to-SID mappings in OSPF has
following rules: following rules:
The OSPF/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-LS The OSPF/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-LS
Prefix Attribute Range TLV as defined in Section 2.3.5. The flags Prefix Attribute Range TLV as defined in Section 2.3.4. The flags
of the Range TLV have the semantic mapped to the definition in of the Range TLV have the semantic mapped to the definition in
[I-D.ietf-ospf-segment-routing-extensions] section 4 or [I-D.ietf-ospf-segment-routing-extensions] section 4 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The
Prefix-SID from the original OSPF Prefix SID Sub-TLV is encoded Prefix-SID from the original OSPF Prefix SID sub-TLV is encoded
using the BGP-LS Prefix Attribute Prefix-SID as defined in using the BGP-LS Prefix Attribute Prefix-SID as defined in
Section 2.3.1 with the flags set according to the definition in Section 2.3.1 with the flags set according to the definition in
[I-D.ietf-ospf-segment-routing-extensions] section 5 or [I-D.ietf-ospf-segment-routing-extensions] section 5 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5.
3.4. Advertisement of a range of IS-IS SR bindings 3.4. Advertisement of a range of IS-IS SR bindings
The advertisement of a range of IS-IS SR bindings has following The advertisement of a range of IS-IS Mapping Server bindings
rules: ([I-D.ietf-isis-segment-routing-extensions]) is encoded using the
following TLV/sub-TLV structure:
In IS-IS the Mapping Server binding ranges are advertised using
the Binding TLV. The IS-IS Binding TLV is encoded in the BGP-LS
Prefix Attribute Range TLV as defined in Section 2.3.5 using the
Binding Sub-TLV as defined in Section 2.3.6. The flags in the
Range TLV are all set to zero on transmit and ignored on
reception. The range value from the original IS-IS Binding TLV is
encoded in the Range TLV "Range" field.
3.5. Advertisement of a path and its attributes from IS-IS protocol
The advertisement of a Path and its attributes is described in
[I-D.ietf-isis-segment-routing-extensions] section 2.4 and has
following rules:
The original Binding SID TLV (from IS-IS) is encoded into the BGP-
LS Range TLV defined in Section 2.3.5 using the Binding Sub-TLV as
defined in Section 2.3.6. The set of Sub-TLVs from the original
IS-IS Binding TLV are encoded as Sub-TLVs of the BGP-LS Binding
TLV as defined in Section 2.3.6. This includes the SID/Label TLV
defined in Section 2.3.
3.6. Advertisement of a path and its attributes from OSPFv2/OSPFv3 Range TLV
protocol Prefix-SID TLV (used as a sub-TLV in this context)
The advertisement of a Path and its attributes is described in where:
[I-D.ietf-ospf-segment-routing-extensions] section 6 and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 6 and has
following rules:
Advertisement of a path for a single prefix: the original Binding o The Range TLV is defined in Section 2.3.4.
SID TLV (from OSPFv2/OSPFv3) is encoded into the BGP-LS Prefix
Attribute Binding TLV as defined in Section 2.3.6. The set of
Sub-TLVs from the original OSPFv2/OSPFv3 Binding TLV are encoded
as Sub-TLVs of the BGP-LS Binding TLV as defined in Section 2.3.6.
This includes the SID/Label TLV defined in Section 2.3.
Advertisement of an SR path for range of prefixes: the OSPF/OSPFv3 o The Prefix-SID TLV (used as sub-TLV in this context) is defined in
Extended Prefix Range TLV is encoded in the BGP-LS Prefix Section 2.3.1.
Attribute Range TLV as defined in Section 2.3.5. The original
OSPFv2/OSPFv3 Binding SID TLV is encoded into the BGP-LS Binding
Sub-TLV as defined in Section 2.3.6. The set of Sub-TLVs from the
original OSPFv2/OSPFv3 Binding TLV are encoded as Sub-TLVs of the
BGP-LS Binding TLV as defined in Section 2.3.6. This includes the
SID/Label TLV defined in Section 2.3.
4. Implementation Status 4. Implementation Status
Note to RFC Editor: Please remove this section prior to publication, Note to RFC Editor: Please remove this section prior to publication,
as well as the reference to RFC 7942. as well as the reference to RFC 7942.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC7942]. Internet-Draft, and is based on a proposal described in [RFC7942].
The description of implementations in this section is intended to The description of implementations in this section is intended to
skipping to change at page 28, line 22 skipping to change at page 21, line 25
this draft requires. However, when IANA-assigned values are this draft requires. However, when IANA-assigned values are
available, implementations will be updated to use them. available, implementations will be updated to use them.
5. IANA Considerations 5. IANA Considerations
This document requests assigning code-points from the registry for This document requests assigning code-points from the registry for
BGP-LS attribute TLVs based on table Table 8. BGP-LS attribute TLVs based on table Table 8.
5.1. TLV/Sub-TLV Code Points Summary 5.1. TLV/Sub-TLV Code Points Summary
This section contains the global table of all TLVs/Sub-TLVs defined This section contains the global table of all TLVs/sub-TLVs defined
in this document. in this document.
+-----------+--------------------------+----------+-----------------+ +-----------+----------------------------+----------+---------------+
| TLV Code | Description | Length | Section | | TLV Code | Description | Length | Section |
| Point | | | | | Point | | | |
+-----------+--------------------------+----------+-----------------+ +-----------+----------------------------+----------+---------------+
| 1034 | SR Capabilities | variable | Section 2.1.1 | | 1034 | SR Capabilities | variable | Section 2.1.2 |
| 1035 | SR Algorithm | variable | Section 2.1.2 | | 1035 | SR Algorithm | variable | Section 2.1.3 |
| 1036 | SR Local Block | variable | Section 2.1.3 | | 1036 | SR Local Block | variable | Section 2.1.4 |
| 1037 | SRMS Preference | variable | Section 2.1.4 | | 1037 | SRMS Preference | variable | Section 2.1.5 |
| 1099 | Adjacency Segment | variable | Section 2.2.1 | | 1099 | Adjacency Segment | variable | Section 2.2.1 |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1100 | LAN Adjacency Segment | variable | Section 2.2.2 | | 1100 | LAN Adjacency Segment | variable | Section 2.2.2 |
| | Identifier (Adj-SID) TLV | | | | | Identifier (Adj-SID) TLV | | |
| 1158 | Prefix SID | variable | Section 2.3.1 | | 1158 | Prefix SID | variable | Section 2.3.1 |
| 1159 | Range | variable | Section 2.3.5 | | 1159 | Range | variable | Section 2.3.4 |
| 1160 | Binding SID | variable | Section 2.3.6 | | 1161 | SID/Label TLV | variable | Section 2.1.1 |
| 1161 | SID/Label TLV | variable | Section 2.3.7.2 | | 1170 | IGP Prefix Attributes | variable | Section 2.3.2 |
| 1162 | ERO Metric TLV | 4 octets | 1 [43] | | 1171 | Source Router-ID | variable | Section 2.3.3 |
| 1163 | IPv4 ERO TLV | 8 octets | 1 [44] | | 1172 | L2 Bundle Member TLV | variable | Section 2.2.3 |
| 1164 | IPv6 ERO TLV | 20 | 1 [45] | +-----------+----------------------------+----------+---------------+
| | | octets | |
| 1165 | Unnumbered Interface ID | 12 | 1 [46] |
| | ERO TLV | octets | |
| 1166 | IPv4 Backup ERO TLV | 8 octets | 1 [47] |
| 1167 | IPv6 Backup ERO TLV | 20 | 1 [48] |
| | | octets | |
| 1168 | Unnumbered Interface ID | 12 | 1 [49] |
| | Backup ERO TLV | octets | |
| 1169 | IPv6 Prefix SID | variable | Section 2.3.2 |
| 1170 | IGP Prefix Attributes | variable | Section 2.3.3 |
| 1171 | Source Router-ID | variable | Section 2.3.4 |
+-----------+--------------------------+----------+-----------------+
Table 8: Summary Table of TLV/Sub-TLV Codepoints Table 8: Summary Table of TLV/Sub-TLV Codepoints
6. Manageability Considerations 6. Manageability Considerations
This section is structured as recommended in [RFC5706]. This section is structured as recommended in [RFC5706].
6.1. Operational Considerations 6.1. Operational Considerations
6.1.1. Operations 6.1.1. Operations
skipping to change at page 30, line 17 skipping to change at page 22, line 28
Procedures and protocol extensions defined in this document do not Procedures and protocol extensions defined in this document do not
affect the BGP security model. See the 'Security Considerations' affect the BGP security model. See the 'Security Considerations'
section of [RFC4271] for a discussion of BGP security. Also refer to section of [RFC4271] for a discussion of BGP security. Also refer to
[RFC4272] and [RFC6952] for analysis of security issues for BGP. [RFC4272] and [RFC6952] for analysis of security issues for BGP.
8. Contributors 8. Contributors
The following people have substantially contributed to the editing of The following people have substantially contributed to the editing of
this document: this document:
Les Ginsberg
Cisco Systems
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
Individual
Email: jefftant@gmail.com
9. Acknowledgements 9. Acknowledgements
The authors would like to thank Les Ginsberg and Ketan Jivan The authors would like to thank Ketan Jivan Talaulikar for his review
Talaulikar for their review of this document. of this document.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-idr-te-pm-bgp]
Previdi, S., Wu, Q., Gredler, H., Ray, S.,
jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg,
"BGP-LS Advertisement of IGP Traffic Engineering
Performance Metric Extensions", draft-ietf-idr-te-pm-
bgp-05 (work in progress), April 2017.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., Previdi, S., Filsfils, C., Bashandy, A., Gredler, H.,
Litkowski, S., Decraene, B., and j. jefftant@gmail.com, Litkowski, S., Decraene, B., and j. jefftant@gmail.com,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-09 (work in progress), October segment-routing-extensions-13 (work in progress), June
2016. 2017.
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] [I-D.ietf-ospf-ospfv3-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, "OSPFv3 Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3
Extensions for Segment Routing", draft-ietf-ospf-ospfv3- Extensions for Segment Routing", draft-ietf-ospf-ospfv3-
segment-routing-extensions-07 (work in progress), October segment-routing-extensions-09 (work in progress), March
2016. 2017.
[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-10 (work in progress), October 2016. routing-extensions-17 (work in progress), June 2017.
[I-D.previdi-isis-ipv6-prefix-sid]
Previdi, S., Ginsberg, L., and C. Filsfils, "Segment
Routing IPv6 Prefix-SID", draft-previdi-isis-ipv6-prefix-
sid-03 (work in progress), November 2016.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005,
<http://www.rfc-editor.org/info/rfc4202>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006,
<http://www.rfc-editor.org/info/rfc4271>. <http://www.rfc-editor.org/info/rfc4271>.
[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
Advertisement", RFC 7684, DOI 10.17487/RFC7684, November Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
2015, <http://www.rfc-editor.org/info/rfc7684>. 2015, <http://www.rfc-editor.org/info/rfc7684>.
skipping to change at page 31, line 41 skipping to change at page 24, line 26
[RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and
U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4
and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794,
March 2016, <http://www.rfc-editor.org/info/rfc7794>. March 2016, <http://www.rfc-editor.org/info/rfc7794>.
10.2. Informative References 10.2. Informative References
[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. Shakir, "Segment Routing Architecture", draft-ietf-
spring-segment-routing-10 (work in progress), November spring-segment-routing-12 (work in progress), June 2017.
2016.
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis",
RFC 4272, DOI 10.17487/RFC4272, January 2006, RFC 4272, DOI 10.17487/RFC4272, January 2006,
<http://www.rfc-editor.org/info/rfc4272>. <http://www.rfc-editor.org/info/rfc4272>.
[RFC5706] Harrington, D., "Guidelines for Considering Operations and [RFC5706] Harrington, D., "Guidelines for Considering Operations and
Management of New Protocols and Protocol Extensions", Management of New Protocols and Protocol Extensions",
RFC 5706, DOI 10.17487/RFC5706, November 2009, RFC 5706, DOI 10.17487/RFC5706, November 2009,
<http://www.rfc-editor.org/info/rfc5706>. <http://www.rfc-editor.org/info/rfc5706>.
skipping to change at page 32, line 34 skipping to change at page 25, line 18
[3] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [3] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.2.1 extensions-05#section-2.2.1
[4] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [4] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.2.2 extensions-05#section-2.2.2
[5] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [5] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.1 extensions-05#section-2.1
[6] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [6] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4
[7] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.3 extensions-05#section-2.3
[8] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [7] http://tools.ietf.org/html/RFC7794
extensions-05#section-2.4.7
[9] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.8
[10] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.9
[11] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.10
[12] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.11
[13] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.12
[14] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.13
[15] http://tools.ietf.org/html/draft-previdi-isis-ipv6-prefix-sid-01
[16] http://tools.ietf.org/html/RFC7794 [8] http://tools.ietf.org/html/RFC7794
[17] http://tools.ietf.org/html/RFC7794 [9] http://tools.ietf.org/html/draft-ietf-isis-l2bundles-05
[18] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [10] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-3.2 extensions-05#section-3.2
[19] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [11] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-3.1 extensions-05#section-3.1
[20] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [12] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-7.1 extensions-05#section-7.1
[21] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [13] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-7.2 extensions-05#section-7.2
[22] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [14] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-5 extensions-05#section-5
[23] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [15] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-2.1 extensions-05#section-2.1
[24] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [16] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
extensions-05#section-6.1
[25] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-6.2.1
[26] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-6.2.2
[27] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-6.2.3
[28] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-6.2.4
[29] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-05#section-6.2.4
[30] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-3.2 routing-extensions-05#section-3.2
[31] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [17] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-3.1 routing-extensions-05#section-3.1
[32] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [18] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-7.1 routing-extensions-05#section-7.1
[33] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [19] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-7.2 routing-extensions-05#section-7.2
[34] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [20] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-5 routing-extensions-05#section-5
[35] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [21] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-2.1 routing-extensions-05#section-2.1
[36] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.1
[37] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.2.1
[38] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.2.2
[39] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.2.3
[40] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.2.4
[41] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.2.5
[42] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-6.2.6
[43] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.7
[44] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.8
[45] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.9
[46] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.10
[47] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.11
[48] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.12
[49] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-2.4.13
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: stefano@previdi.net
Peter Psenak Peter Psenak
Cisco Systems, Inc. Cisco Systems, Inc.
Apollo Business Center Apollo Business Center
Mlynske nivy 43 Mlynske nivy 43
Bratislava 821 09 Bratislava 821 09
Slovakia Slovakia
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
skipping to change at page 36, line 11 skipping to change at line 1160
RtBrick Inc. RtBrick Inc.
Email: hannes@rtbrick.com Email: hannes@rtbrick.com
Mach(Guoyi) Chen Mach(Guoyi) Chen
Huawei Technologies Huawei Technologies
Huawei Building, No. 156 Beiqing Rd. Huawei Building, No. 156 Beiqing Rd.
Beijing 100095 Beijing 100095
China China
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
Jeff Tantsura
Individual
Email: jefftant@gmail.com
 End of changes. 82 change blocks. 
713 lines changed or deleted 332 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/