draft-ietf-idr-bgp-ls-segment-routing-ext-03.txt   draft-ietf-idr-bgp-ls-segment-routing-ext-04.txt 
Inter-Domain Routing S. Previdi, Ed. Inter-Domain Routing S. Previdi, Ed.
Internet-Draft P. Psenak Internet-Draft K. Talaulikar
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: January 27, 2018 Cisco Systems, Inc. Expires: July 29, 2018 Cisco Systems, Inc.
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
M. Chen M. Chen
Huawei Technologies Huawei Technologies
July 26, 2017 January 25, 2018
BGP Link-State extensions for Segment Routing BGP Link-State extensions for Segment Routing
draft-ietf-idr-bgp-ls-segment-routing-ext-03 draft-ietf-idr-bgp-ls-segment-routing-ext-04
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 by encoding paths as sequences of topological sub-paths, called
topological sub-paths, called "segments". These segments are "segments". These segments are advertised by routing protocols e.g.
advertised by the link-state routing protocols (IS-IS, OSPF and by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within
OSPFv3). 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
order to carry segment information via BGP. order to carry segment routing information via BGP.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 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 January 27, 2018. This Internet-Draft will expire on July 29, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. 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. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . 5 2.1.1. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . 5
2.1.2. SR-Capabilities TLV . . . . . . . . . . . . . . . . . 6 2.1.2. SR-Capabilities TLV . . . . . . . . . . . . . . . . . 6
2.1.3. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . 7 2.1.3. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . 7
2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 7 2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 8
2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 8 2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 8
2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 9 2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 9
2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 10 2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 10
2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 10 2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 10
2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 11 2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 11
2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 13 2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 13
2.3.1. Prefix-SID TLV . . . . . . . . . . . . . . . . . . . 14 2.3.1. Prefix-SID TLV . . . . . . . . . . . . . . . . . . . 14
2.3.2. IGP Prefix Attributes TLV . . . . . . . . . . . . . . 15 2.3.2. Prefix Attribute Flags TLV . . . . . . . . . . . . . 15
2.3.3. Source Router Identifier (Source Router-ID) TLV . . . 15 2.3.3. Source Router Identifier (Source Router-ID) TLV . . . 16
2.3.4. Range TLV . . . . . . . . . . . . . . . . . . . . . . 16 2.3.4. Range TLV . . . . . . . . . . . . . . . . . . . . . . 16
2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 17 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 17
2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs . . 18 2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs . 18
3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1. Advertisement of a IS-IS Prefix SID TLV . . . . . . . . . 19 3.1. Advertisement of an IS-IS Prefix SID TLV . . . . . . . . 19
3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV . . . . . . 19 3.2. Advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV . . . . 19
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 19 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 20 3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 20
4. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 20
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
5.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 21 5.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 21
6. Manageability Considerations . . . . . . . . . . . . . . . . 22 6. Manageability Considerations . . . . . . . . . . . . . . . . 22
6.1. Operational Considerations . . . . . . . . . . . . . . . 22 6.1. Operational Considerations . . . . . . . . . . . . . . . 22
6.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 22 6.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 22
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.1. Normative References . . . . . . . . . . . . . . . . . . 23
10.1. Normative References . . . . . . . . . . . . . . . . . . 23 9.2. Informative References . . . . . . . . . . . . . . . . . 24
10.2. Informative References . . . . . . . . . . . . . . . . . 24 9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
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, OSPFv2 and
OSPFv3). OSPFv3).
Two types of IGP segments are defined, Prefix segments and Adjacency Two types of IGP segments are defined, Prefix segments and Adjacency
segments. Prefix segments, by default, represent an ECMP-aware segments. Prefix segments, by default, represent an ECMP-aware
shortest-path to a prefix, as per the state of the IGP topology. shortest-path to a prefix, as per the state of the IGP topology.
Adjacency segments represent a hop over a specific adjacency between Adjacency segments represent a hop over a specific adjacency between
two nodes in the IGP. A prefix segment is typically a multi-hop path two nodes in the IGP. A prefix segment is typically a multi-hop path
while an adjacency segment, in most of the cases, is a one-hop path. while an adjacency segment, in most of the cases, is a one-hop path.
[I-D.ietf-spring-segment-routing]. [I-D.ietf-spring-segment-routing].
skipping to change at page 4, line 46 skipping to change at page 4, line 46
In order to address the need for applications that require In order to address the need for applications that require
topological visibility across IGP areas, or even across Autonomous topological visibility across IGP areas, or even across Autonomous
Systems (AS), the BGP-LS address-family/sub-address-family have been Systems (AS), the BGP-LS address-family/sub-address-family have been
defined to allow BGP to carry Link-State information. The BGP defined to allow BGP to carry Link-State information. The BGP
Network Layer Reachability Information (NLRI) encoding format for Network Layer Reachability Information (NLRI) encoding format for
BGP-LS and a new BGP Path Attribute called the BGP-LS attribute are BGP-LS and a new BGP Path Attribute called the BGP-LS attribute are
defined in [RFC7752]. The identifying key of each Link-State object, defined in [RFC7752]. The identifying key of each Link-State object,
namely a node, link, or prefix, is encoded in the NLRI and the namely a node, link, or prefix, is encoded in the NLRI and the
properties of the object are encoded in the BGP-LS attribute. properties of the object are encoded in the BGP-LS attribute.
Figure Figure 1 describes a typical deployment scenario. In each IGP Figure 1 describes a typical deployment scenario. In each IGP area,
area, one or more nodes are configured with BGP-LS. These BGP one or more nodes are configured with BGP-LS. These BGP speakers
speakers form an IBGP mesh by connecting to one or more route- form an IBGP mesh by connecting to one or more route-reflectors.
reflectors. This way, all BGP speakers (specifically the route- This way, all BGP speakers (specifically the route-reflectors) obtain
reflectors) obtain Link-State information from all IGP areas (and Link-State information from all IGP areas (and from other ASes from
from other ASes from EBGP peers). An external component connects to EBGP peers). An external component connects to the route-reflector
the route-reflector to obtain this information (perhaps moderated by to obtain this information (perhaps moderated by a policy regarding
a policy regarding what information is or isn't advertised to the what information is or isn't advertised to the external component).
external component).
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 SR extensions to BGP-LS and specifies the TLVs
Section 2.4 and Section 2.5 illustrates the equivalent TLVs and sub- and sub-TLVs for advertising SR information. Section 2.4 and
TLVs in IS-IS, OSPF and OSPFv3 protocols. Section 2.5 illustrates the equivalent 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. 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
skipping to change at page 5, line 49 skipping to change at page 5, line 50
+-----------------+----------+---------------+ +-----------------+----------+---------------+
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. 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 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
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label (variable) | | SID/Label (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 28 skipping to change at page 6, line 28
SID/Label: If length is set to 3, then the 20 rightmost bits 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 represent a label. If length is set to 4, then the value
represents a 32 bit SID. represents a 32 bit SID.
The receiving router MUST ignore the SID/Label sub-TLV if the The receiving router MUST ignore the SID/Label sub-TLV if the
length is other then 3 or 4. length is other then 3 or 4.
2.1.2. SR-Capabilities TLV 2.1.2. SR-Capabilities TLV
The SR-Capabilities TLV is used in order to advertise the node's The SR-Capabilities TLV is used in order to advertise the node's SR
Segment Routing Global Base (SRGB) as originated in: Capabilities and its Segment Routing Global Base (SRGB) range(s).
This information is derived from the protocol specific
advertisements.
o IS-IS, as defined by the SR-Capabilities TLV in o IS-IS, as defined by the SR-Capabilities TLV in
[I-D.ietf-isis-segment-routing-extensions]. [I-D.ietf-isis-segment-routing-extensions].
o OSPF/OSPFv3, as defined by the SID/Label Range TLV in o OSPFv2/OSPFv3, as defined by the SID/Label Range TLV in
[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].
The SR Capabilities TLV has following format: 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 7, line 18 skipping to change at page 7, line 33
Flags: 1 octet of flags as defined in Flags: 1 octet of flags as defined in
[I-D.ietf-isis-segment-routing-extensions]. [I-D.ietf-isis-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.1.1). SID/Label sub-TLV (as defined in Section 2.1.1).
Multiple SRGB entries are encoded within the same SR Capabilities
TLV.
2.1.3. SR-Algorithm 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 45 skipping to change at page 8, line 9
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 5.
Length: Variable. Length: Variable.
Algorithm: 1 octet identifying the algorithm. Algorithm: 1 octet identifying the algorithm.
2.1.4. SR Local Block TLV 2.1.4. SR Local Block TLV
The SR Local Block (SRLB) TLV contains the range of labels the node The SR Local Block (SRLB) TLV contains the range(s) of labels the
has reserved for local SIDs. Local SIDs are used, e.g., in IGP (IS- node has reserved for local SIDs. Local SIDs are used, e.g., in IGP
IS, OSPF) for Adjacency-SIDs, and may also be allocated by other (IS-IS, OSPF) for Adjacency-SIDs, and may also be allocated by
components than IGP protocols. As an example, an application or a components other than IGP protocols. As an example, an application
controller may instruct a node to allocate a specific local SID. or a 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 |
skipping to change at page 8, line 36 skipping to change at page 8, line 47
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.1.1). SID/Label sub-TLV (as defined in Section 2.1.1).
Multiple SRLB entries are encoded within the same SRLB TLV.
2.1.5. SRMS Preference TLV 2.1.5. SRMS Preference TLV
The Segment Routing Mapping Server (SRMS) Preference TLV is used in The Segment Routing Mapping Server (SRMS) Preference TLV is used in
order to associate a preference with SRMS advertisements from a order to associate a preference with SRMS advertisements from a
particular source. particular source.
The SRMS Preference 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
skipping to change at page 13, line 39 skipping to change at page 13, line 39
| 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] | | 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] |
| | bandwidth | | | | bandwidth | |
| 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] | | 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] |
| | utilization | | | | utilization | |
+-----------+----------------------------+--------------------------+ +-----------+----------------------------+--------------------------+
Table 3: L2 Bundle Member Link Attribute TLVs 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 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 |
| IGP Prefix Attributes | 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
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 The Prefix-SID TLV is used in order to advertise information related
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 OSPF/OSPFv3, as defined by the Prefix-SID TLV in o OSPFv2/OSPFv3, as defined by the Prefix-SID TLV in
[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].
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 14, line 46 skipping to change at page 14, line 46
Length: Variable Length: Variable
Algorithm: 1 octet value identify the algorithm. Algorithm: 1 octet value identify the algorithm.
SID/Index/Label: SID/Index/Label:
* IS-IS: Label or index value as defined in * IS-IS: Label or index value as defined in
[I-D.ietf-isis-segment-routing-extensions], [I-D.ietf-isis-segment-routing-extensions],
* OSPF: Label or index value as defined in * OSPFv2: Label or index value as defined in
[I-D.ietf-ospf-segment-routing-extensions], [I-D.ietf-ospf-segment-routing-extensions],
* OSPFv3: Label or index value as defined in * OSPFv3: Label or index value as defined in
[I-D.ietf-ospf-ospfv3-segment-routing-extensions], [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 OSPFv2 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. IGP Prefix Attributes TLV 2.3.2. Prefix Attribute Flags TLV
The IGP Prefix Attribute TLV carries IPv4/IPv6 prefix attribute flags The Prefix Attribute Flags TLV carries IPv4/IPv6 prefix attribute
as defined in [RFC7684] and [RFC7794]. flags information. These flags are defined for OSPFv2 in [RFC7684],
for OSPFv3 in [RFC5340] and for ISIS in [RFC7794].
The IGP Prefix Attribute TLV has the following format: The Prefix Attribute Flags 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 (variable) // // Flags (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 5.
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. OSPFv2 flags are
OSPF flags are defined in [RFC7684] and IS-IS flags are defined in defined in [RFC7684], for OSPFv3 this maps to the Prefix Options
field defined in [RFC5340] 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 Prefix Attribute Flags 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.3. 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 of the Prefix. For IS-IS protocol this is as defined in
protocol, the Source Router-ID TLV may be used to carry the OSPF [RFC7794]. 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// IPv4/IPv6 Address (Router-ID) // // IPv4/IPv6 Address (Router-ID) //
skipping to change at page 18, line 17 skipping to change at page 18, line 17
| | | /sub-TLV | | | | /sub-TLV |
+----------------------------------------+----------+---------------+ +----------------------------------------+----------+---------------+
| SR Capabilities | variable | 2 [1] | | SR Capabilities | variable | 2 [1] |
| SR Algorithm | variable | 19 [2] | | SR Algorithm | variable | 19 [2] |
| Adjacency Segment Identifier (Adj-SID) | variable | 31 [3] | | Adjacency Segment Identifier (Adj-SID) | variable | 31 [3] |
| TLV | | | | TLV | | |
| LAN Adjacency Segment Identifier (LAN- | variable | 32 [4] | | LAN Adjacency Segment Identifier (LAN- | variable | 32 [4] |
| Adj-SID) TLV | | | | Adj-SID) TLV | | |
| Prefix SID | variable | 3 [5] | | Prefix SID | variable | 3 [5] |
| SID/Label TLV | variable | 1 [6] | | SID/Label TLV | variable | 1 [6] |
| IGP Prefix Attributes | variable | 4 [7] | | Prefix Attribute Flags | variable | 4 [7] |
| Source Router ID | variable | 11/12 [8] | | Source Router ID | variable | 11/12 [8] |
| L2 Bundle Member TLV | variable | 25 [9] | | L2 Bundle Member TLV | variable | 25 [9] |
+----------------------------------------+----------+---------------+ +----------------------------------------+----------+---------------+
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 OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs
This section illustrate the OSPF and OSPFv3 Segment Routing This section illustrate the OSPFv2 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 OSPFv2 and OSPFv3.
+---------------------------------------+----------+----------------+ +--------------------------------------+----------+-----------------+
| Description | Length | OSPF TLV/sub- | | Description | Length | OSPFv2 TLV/sub- |
| | | TLV | | | | TLV |
+---------------------------------------+----------+----------------+ +--------------------------------------+----------+-----------------+
| SR Capabilities | variable | 9 [10] | | SR Capabilities | variable | 9 [10] |
| SR Algorithm | variable | 8 [11] | | SR Algorithm | variable | 8 [11] |
| Adjacency Segment Identifier (Adj- | variable | 2 [12] | | Adjacency Segment Identifier (Adj- | variable | 2 [12] |
| SID) TLV | | | | SID) TLV | | |
| LAN Adjacency Segment Identifier | variable | 3 [13] | | LAN Adjacency Segment Identifier | variable | 3 [13] |
| (Adj-SID) TLV | | | | (Adj-SID) TLV | | |
| Prefix SID | variable | 2 [14] | | Prefix SID | variable | 2 [14] |
| SID/Label TLV | variable | 1 [15] | | SID/Label TLV | variable | 1 [15] |
+---------------------------------------+----------+----------------+ | Prefix Attribute Flags | variable | 4 [16] |
+--------------------------------------+----------+-----------------+
Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs
+--------------------------------------+----------+-----------------+ +--------------------------------------+----------+-----------------+
| Description | Length | OSPFv3 TLV/sub- | | Description | Length | OSPFv3 TLV/sub- |
| | | TLV | | | | TLV |
+--------------------------------------+----------+-----------------+ +--------------------------------------+----------+-----------------+
| SR Capabilities | variable | 9 [16] | | SR Capabilities | variable | 9 [17] |
| SR Algorithm | variable | 8 [17] | | SR Algorithm | variable | 8 [18] |
| Adjacency Segment Identifier (Adj- | variable | 5 [18] | | Adjacency Segment Identifier (Adj- | variable | 5 [19] |
| SID) TLV | | | | SID) TLV | | |
| LAN Adjacency Segment Identifier | variable | 6 [19] | | LAN Adjacency Segment Identifier | variable | 6 [20] |
| (Adj-SID) TLV | | | | (Adj-SID) TLV | | |
| Prefix SID | variable | 4 [20] | | Prefix SID | variable | 4 [21] |
| SID/Label TLV | variable | 3 [21] | | SID/Label TLV | variable | 3 [22] |
| Prefix Attribute Flags | variable | 4 [23] |
+--------------------------------------+----------+-----------------+ +--------------------------------------+----------+-----------------+
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 from OSPFv2, OSPFv3 and ISIS
protocols.
3.1. Advertisement of a IS-IS Prefix SID TLV 3.1. Advertisement of an IS-IS Prefix SID TLV
The advertisement of a IS-IS Prefix SID TLV has following rules: The advertisement of an IS-IS Prefix SID TLV has following rules:
The IS-IS Prefix-SID is encoded in the BGP-LS Prefix Attribute The IS-IS Prefix-SID is encoded in the BGP-LS Prefix Attribute
Prefix-SID as defined in Section 2.3.1. The flags in the Prefix- Prefix-SID as defined in Section 2.3.1. The flags in the Prefix-
SID TLV have the semantic defined in SID TLV have the semantic defined in
[I-D.ietf-isis-segment-routing-extensions] section 2.1. [I-D.ietf-isis-segment-routing-extensions] section 2.1.
3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV 3.2. Advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV
The advertisement of a OSPF/OSPFv3 Prefix-SID TLV has following The advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV has following
rules: rules:
The OSPF (or OSPFv3) Prefix-SID is encoded in the BGP-LS Prefix The OSPFv2/OSPFv3 Prefix-SID is encoded in the BGP-LS Prefix
Attribute Prefix-SID as defined in Section 2.3.1. The flags in Attribute Prefix-SID as defined in Section 2.3.1. The flags in
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 OSPFv2/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-
Prefix Attribute Range TLV as defined in Section 2.3.4. The flags LS Prefix Attribute Range TLV as defined in Section 2.3.4. The
of the Range TLV have the semantic mapped to the definition in flags of the Range TLV have the semantic mapped to the definition
[I-D.ietf-ospf-segment-routing-extensions] section 4 or in [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 Mapping Server bindings The advertisement of a range of IS-IS Mapping Server bindings
skipping to change at page 21, line 45 skipping to change at page 21, line 45
| 1035 | SR Algorithm | Section 2.1.3 | | 1035 | SR Algorithm | Section 2.1.3 |
| 1036 | SR Local Block | Section 2.1.4 | | 1036 | SR Local Block | Section 2.1.4 |
| 1037 | SRMS Preference | Section 2.1.5 | | 1037 | SRMS Preference | Section 2.1.5 |
| 1099 | Adjacency Segment Identifier (Adj- | Section 2.2.1 | | 1099 | Adjacency Segment Identifier (Adj- | Section 2.2.1 |
| | SID) TLV | | | | SID) TLV | |
| 1100 | LAN Adjacency Segment Identifier | Section 2.2.2 | | 1100 | LAN Adjacency Segment Identifier | Section 2.2.2 |
| | (Adj-SID) TLV | | | | (Adj-SID) TLV | |
| 1158 | Prefix SID | Section 2.3.1 | | 1158 | Prefix SID | Section 2.3.1 |
| 1159 | Range | Section 2.3.4 | | 1159 | Range | Section 2.3.4 |
| 1161 | SID/Label TLV | Section 2.1.1 | | 1161 | SID/Label TLV | Section 2.1.1 |
| 1170 | IGP Prefix Attributes | Section 2.3.2 | | 1170 | Prefix Attribute Flags | Section 2.3.2 |
| 1171 | Source Router-ID | Section 2.3.3 | | 1171 | Source Router-ID | Section 2.3.3 |
| 1172 | L2 Bundle Member TLV | Section 2.2.3 | | 1172 | L2 Bundle Member TLV | Section 2.2.3 |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
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].
skipping to change at page 22, line 28 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:
Peter Psenak
Cisco Systems
Email: ppsenak@cisco.com
Les Ginsberg Les Ginsberg
Cisco Systems Cisco Systems
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
Individual Nuage Networks
Email: jefftant@gmail.com Email: jefftant.ietf@gmail.com
9. Acknowledgements
The authors would like to thank Ketan Jivan Talaulikar for his review
of this document.
10. References
10.1. Normative References 9. References
9.1. Normative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Previdi, S., Wu, Q., Gredler, H., Ray, S., Ginsberg, L., Previdi, S., Wu, Q., Gredler, H., Ray, S.,
jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg, Tantsura, J., and C. Filsfils, "BGP-LS Advertisement of
"BGP-LS Advertisement of IGP Traffic Engineering IGP Traffic Engineering Performance Metric Extensions",
Performance Metric Extensions", draft-ietf-idr-te-pm- draft-ietf-idr-te-pm-bgp-08 (work in progress), August
bgp-06 (work in progress), June 2017. 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., Ginsberg, L., Filsfils, C., Bashandy, A.,
Litkowski, S., Decraene, B., and j. jefftant@gmail.com, 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-13 (work in progress), June segment-routing-extensions-15 (work in progress), December
2017. 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-09 (work in progress), March segment-routing-extensions-10 (work in progress),
2017. September 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-18 (work in progress), July 2017. routing-extensions-24 (work in progress), December 2017.
[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>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005,
<http://www.rfc-editor.org/info/rfc4202>. <https://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>. <https://www.rfc-editor.org/info/rfc4271>.
[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
<https://www.rfc-editor.org/info/rfc5340>.
[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, <https://www.rfc-editor.org/info/rfc7684>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<http://www.rfc-editor.org/info/rfc7752>. <https://www.rfc-editor.org/info/rfc7752>.
[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, <https://www.rfc-editor.org/info/rfc7794>.
10.2. Informative References 9.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., Ginsberg, L., Decraene, B.,
and R. Shakir, "Segment Routing Architecture", draft-ietf- Litkowski, S., and R. Shakir, "Segment Routing
spring-segment-routing-12 (work in progress), June 2017. Architecture", draft-ietf-spring-segment-routing-15 (work
in progress), January 2018.
[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>. <https://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>. <https://www.rfc-editor.org/info/rfc5706>.
[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
BGP, LDP, PCEP, and MSDP Issues According to the Keying BGP, LDP, PCEP, and MSDP Issues According to the Keying
and Authentication for Routing Protocols (KARP) Design and Authentication for Routing Protocols (KARP) Design
Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,
<http://www.rfc-editor.org/info/rfc6952>. <https://www.rfc-editor.org/info/rfc6952>.
[RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running
Code: The Implementation Status Section", BCP 205, Code: The Implementation Status Section", BCP 205,
RFC 7942, DOI 10.17487/RFC7942, July 2016, RFC 7942, DOI 10.17487/RFC7942, July 2016,
<http://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
10.3. URIs 9.3. URIs
[1] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [1] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-3.1 extensions-05#section-3.1
[2] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- [2] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-05#section-3.2 extensions-05#section-3.2
[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
skipping to change at page 25, line 44 skipping to change at page 25, line 49
[13] 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
[14] 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
[15] 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
[16] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [16] http://tools.ietf.org/html/RFC7684#section-2.1
routing-extensions-05#section-3.2
[17] 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.2
[18] 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-3.1
[19] 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.1
[20] 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-7.2
[21] 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-5
[22] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-05#section-2.1 routing-extensions-05#section-2.1
[23] http://tools.ietf.org/html/RFC5340#section-A.4.1.1
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: stefano@previdi.net Email: stefano@previdi.net
Peter Psenak Ketan Talaulikar
Cisco Systems, Inc. Cisco Systems, Inc.
Apollo Business Center S.No. 154/6, Phase I, Hinjawadi
Mlynske nivy 43 Pune 411 057
Bratislava 821 09 India
Slovakia
Email: ppsenak@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
Hannes Gredler Hannes Gredler
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
 End of changes. 85 change blocks. 
157 lines changed or deleted 164 lines changed or added

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