draft-ietf-idr-bgp-ls-segment-routing-ext-07.txt   draft-ietf-idr-bgp-ls-segment-routing-ext-08.txt 
Inter-Domain Routing S. Previdi, Ed. Inter-Domain Routing S. Previdi, Ed.
Internet-Draft Internet-Draft
Intended status: Standards Track K. Talaulikar Intended status: Standards Track K. Talaulikar
Expires: November 16, 2018 C. Filsfils Expires: November 24, 2018 C. Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
M. Chen M. Chen
Huawei Technologies Huawei Technologies
May 15, 2018 May 23, 2018
BGP Link-State extensions for Segment Routing BGP Link-State extensions for Segment Routing
draft-ietf-idr-bgp-ls-segment-routing-ext-07 draft-ietf-idr-bgp-ls-segment-routing-ext-08
Abstract Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end Segment Routing (SR) allows for a flexible definition of end-to-end
paths by encoding paths as sequences of topological sub-paths, called paths by encoding paths as sequences of topological sub-paths, called
"segments". These segments are advertised by routing protocols e.g. "segments". These segments are advertised by routing protocols e.g.
by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within
IGP topologies. IGP topologies.
This draft defines extensions to the BGP Link-state address-family in This draft defines extensions to the BGP Link-state address-family in
skipping to change at page 1, line 49 skipping to change at page 1, line 49
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 16, 2018. This Internet-Draft will expire on November 24, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
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 . . . . . . . . . . . . . . . . . . 6 2.1.1. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . 8
2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 8 2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 8
2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 9 2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 9
2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 9 2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 10
2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 10 2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 10
2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 11 2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 11
2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 12 2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 12
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. Prefix Attribute Flags TLV . . . . . . . . . . . . . 15 2.3.2. Prefix Attribute Flags TLV . . . . . . . . . . . . . 15
2.3.3. Source Router Identifier (Source Router-ID) TLV . . . 16 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 . . . . . 18 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 18
2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs . 18 2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs . 19
3. Implementation Status . . . . . . . . . . . . . . . . . . . . 19 3. Implementation Status . . . . . . . . . . . . . . . . . . . . 20
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
4.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 20 4.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 21
5. Manageability Considerations . . . . . . . . . . . . . . . . 21 5. Manageability Considerations . . . . . . . . . . . . . . . . 22
5.1. Operational Considerations . . . . . . . . . . . . . . . 21 5.1. Operational Considerations . . . . . . . . . . . . . . . 22
5.2. Management Considerations . . . . . . . . . . . . . . . . 21 5.2. Management Considerations . . . . . . . . . . . . . . . . 22
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 22
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.1. Normative References . . . . . . . . . . . . . . . . . . 22 9.1. Normative References . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . 23 9.2. Informative References . . . . . . . . . . . . . . . . . 25
9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 24 9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
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, OSPFv2 and advertised by the link-state routing protocols (IS-IS, OSPFv2 and
skipping to change at page 5, line 30 skipping to change at page 5, line 30
Section 2.5 illustrates the equivalent TLVs and sub-TLVs in IS-IS, Section 2.5 illustrates the equivalent TLVs and sub-TLVs in IS-IS,
OSPFv2 and OSPFv3 protocols. 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.
Some of the TLVs defined in this document contain fields (e.g. flags)
whose semantics need to be interpreted accordingly to the respective
underlying IS-IS, OSPFv2 or OSPFv3 protocol. The receiver of the
BGP-LS update for any of the NLRIs MUST check the Protocol-ID of the
NLRI and refer to the underlying protocol specification in order to
parse such fields. The individual field descriptions in the sub-
sections below point to the relevant underlying protocol
specifications for such fields.
2.1. Node Attributes TLVs 2.1. Node Attributes TLVs
The following Node Attribute TLVs are defined: The following Node Attribute TLVs are defined:
+-----------------+----------+---------------+ +-----------------+----------+---------------+
| Description | Length | Section | | Description | Length | Section |
+-----------------+----------+---------------+ +-----------------+----------+---------------+
| SID/Label | variable | Section 2.1.1 | | SID/Label | variable | Section 2.1.1 |
| SR Capabilities | variable | Section 2.1.2 | | SR Capabilities | variable | Section 2.1.2 |
| SR Algorithm | variable | Section 2.1.3 | | SR Algorithm | variable | Section 2.1.3 |
| SR Local Block | variable | Section 2.1.4 | | SR Local Block | variable | Section 2.1.4 |
| SRMS Preference | variable | Section 2.1.5 | | SRMS Preference | variable | Section 2.1.5 |
+-----------------+----------+---------------+ +-----------------+----------+---------------+
Table 1: Node Attribute TLVs Table 1: Node Attribute TLVs
These TLVs can ONLY be added to the Node Attribute associated with These TLVs can ONLY be added to the Node Attribute associated with
the Node NLRI that originates the corresponding SR TLV. the Node NLRI that originates the corresponding underlying IGP TLV/
sub-TLV described below.
2.1.1. SID/Label Sub-TLV 2.1.1. SID/Label Sub-TLV
The SID/Label TLV is used as sub-TLV by the SR-Capabilities The SID/Label TLV is used as sub-TLV by the SR-Capabilities
(Section 2.1.2) and SRLB (Section 2.1.4) TLVs and has the following (Section 2.1.2) and SRLB (Section 2.1.4) TLVs and has the following
format: format:
0 1 2 3 0 1 2 3
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 9, line 52 skipping to change at page 10, line 22
| Adjacency Segment Identifier (Adj-SID) | variable | Section 2.2.1 | | Adjacency Segment Identifier (Adj-SID) | variable | Section 2.2.1 |
| TLV | | | | TLV | | |
| LAN Adjacency Segment Identifier (Adj- | variable | Section 2.2.2 | | LAN Adjacency Segment Identifier (Adj- | variable | Section 2.2.2 |
| SID) TLV | | | | SID) TLV | | |
| L2 Bundle Member TLV | variable | Section 2.2.3 | | L2 Bundle Member TLV | variable | Section 2.2.3 |
+----------------------------------------+----------+---------------+ +----------------------------------------+----------+---------------+
Table 2: Link Attribute TLVs Table 2: Link Attribute TLVs
These TLVs can ONLY be added to the Link Attribute associated with These TLVs can ONLY be added to the Link Attribute associated with
the link whose local node originates the corresponding TLV. the link whose local node originates the corresponding underlying IGP
TLV/sub-TLV described below.
For a LAN, normally a node only announces its adjacency to the IS-IS For a LAN, normally a node only announces its adjacency to the IS-IS
pseudo-node (or the equivalent OSPF Designated and Backup Designated pseudo-node (or the equivalent OSPF Designated and Backup Designated
Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN
Adjecency Segment TLV allows a node to announce adjacencies to all Adjecency Segment TLV allows a node to announce adjacencies to all
other nodes attached to the LAN in a single instance of the BGP-LS other nodes attached to the LAN in a single instance of the BGP-LS
Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI
would need to be originated for each additional adjacency in order to would need to be originated for each additional adjacency in order to
advertise the SR TLVs for these neighbor adjacencies. advertise the SR TLVs for these neighbor adjacencies.
skipping to change at page 11, line 31 skipping to change at page 11, line 49
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label/Index (variable) | | SID/Label/Index (variable) |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
where: where:
Type: TBD, see Section 4. Type: TBD, see Section 4.
Length: Variable. For ISIS it would be 13 or 14 depending on Length: Variable. For IS-IS it would be 13 or 14 depending on
Label or Index encoding of the SID. For OSPF it would be 11 or 12 Label or Index encoding of the SID. For OSPF it would be 11 or 12
depending on Label or Index encoding of the SID. depending on Label or Index encoding of the SID.
Flags. 1 octet field of following flags as defined in Flags. 1 octet field of following flags as 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-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.
skipping to change at page 14, line 5 skipping to change at page 14, line 16
| Description | Length | Section | | Description | Length | Section |
+------------------------+----------+---------------+ +------------------------+----------+---------------+
| Prefix SID | variable | Section 2.3.1 | | Prefix SID | variable | Section 2.3.1 |
| Range | variable | Section 2.3.4 | | Range | variable | Section 2.3.4 |
| Prefix Attribute Flags | variable | Section 2.3.2 | | Prefix Attribute Flags | variable | Section 2.3.2 |
| Source Router-ID | variable | Section 2.3.3 | | Source Router-ID | variable | Section 2.3.3 |
+------------------------+----------+---------------+ +------------------------+----------+---------------+
Table 4: Prefix Attribute TLVs Table 4: Prefix Attribute TLVs
2.3.1. Prefix-SID TLV These TLVs can ONLY be added to the Prefix Attribute associated with
the prefix whose local node originates the corresponding underlying
IGP TLV/sub-TLV described below.
The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose 2.3.1. Prefix-SID TLV
local node in the corresponding Prefix NLRI is the node that
originates the corresponding SR TLV.
The Prefix-SID TLV is used in order to advertise information related The Prefix-SID TLV is used in order to advertise information related
to a Prefix-SID. This information is originated in: to a Prefix-SID. This information is originated in:
o IS-IS, as defined by the Prefix-SID TLV in o IS-IS, as defined by the Prefix-SID TLV in
[I-D.ietf-isis-segment-routing-extensions]. [I-D.ietf-isis-segment-routing-extensions].
o OSPFv2/OSPFv3, as defined by the Prefix-SID TLV in o OSPFv2 and 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] respectively.
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, see Section 4. Type: TBD, see Section 4.
Length: Variable, 7 or 8 depending on Label or Index encoding of Length: Variable, 7 or 8 depending on Label or Index encoding of
the SID the SID
Flags: 1 octet value which sould be parsed as:
* IS-IS Prefix-SID flags are defined in
[I-D.ietf-isis-segment-routing-extensions] section 2.1.
* OSPFv2 Prefix-SID flags are defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5.
* OSPFv3 Prefix-SID flags are defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5.
Algorithm: 1 octet value identify the algorithm. Algorithm: 1 octet value identify the algorithm.
Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on
receipt. receipt.
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],
* OSPFv2: 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 Flags field format and the semantic of each individual flag MUST
be taken from the corresponding source protocol (i.e.: the protocol
of origin of the Prefix-SID being advertised in BGP-LS).
IS-IS Prefix-SID flags are defined in
[I-D.ietf-isis-segment-routing-extensions] section 2.1.
OSPFv2 Prefix-SID flags are defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5.
OSPFv3 Prefix-SID flags are defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5.
2.3.2. Prefix Attribute Flags TLV 2.3.2. Prefix Attribute Flags TLV
The Prefix Attribute Flags TLV carries IPv4/IPv6 prefix attribute The Prefix Attribute Flags TLV carries IPv4/IPv6 prefix attribute
flags information. These flags are defined for OSPFv2 in [RFC7684], flags information. These flags are defined for OSPFv2 in [RFC7684],
for OSPFv3 in [RFC5340] and for ISIS in [RFC7794]. for OSPFv3 in [RFC5340] and for IS-IS in [RFC7794].
The Prefix Attribute Flags 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 4. Type: TBD, see Section 4.
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. OSPFv2 flags are field). Flags are routing protocol specific and are to be parsed
defined in [RFC7684], for OSPFv3 this maps to the Prefix Options as below:
field defined in [RFC5340] and IS-IS flags are defined in
[RFC7794]. The receiver of the BGP-LS update, when inspecting the * IS-IS flags are defined in [RFC7794]
Prefix Attribute Flags TLV, MUST check the Protocol-ID of the NLRI
and refer to the protocol specification in order to parse the * OSPFv2 flags are defined in [RFC7684]
flags.
* OSPFv3 flags map to the Prefix Options field defined in
[RFC7794] and extended via [RFC8362]
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 of the Prefix. For IS-IS protocol this is as defined in originator of the Prefix. For IS-IS protocol this is as defined in
[RFC7794]. 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:
skipping to change at page 16, line 32 skipping to change at page 16, line 43
where: where:
Type: TBD, see Section 4. Type: TBD, see Section 4.
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.
2.3.4. Range TLV 2.3.4. Range TLV
The Range TLV can ONLY be added to the Prefix Attribute whose local The range TLV is used in order to advertise a range of prefix-to-SID
node in the corresponding Prefix NLRI is the node that originates the mappings as part of the Segment Routing Mapping Server functionality
corresponding SR TLV. [I-D.ietf-spring-segment-routing-ldp-interop], as defined in the
respective underlying IGP SR extensions
When the range TLV is used in order to advertise a range of prefix-
to-SID mappings as defined in
[I-D.ietf-ospf-segment-routing-extensions], [I-D.ietf-ospf-segment-routing-extensions],
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] and [I-D.ietf-ospf-ospfv3-segment-routing-extensions] and
[I-D.ietf-isis-segment-routing-extensions]. The Prefix-NLRI the [I-D.ietf-isis-segment-routing-extensions]. The Prefix-NLRI to which
Range TLV is attached to MUST be advertised as a non-routing prefix the Range TLV is attached MUST be advertised as a non-routing prefix
where no IGP metric TLV (TLV 1095) is attached. 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 |
skipping to change at page 17, line 36 skipping to change at page 17, line 38
Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on
receipt. receipt.
Range Size: 2 octets as defined in Range Size: 2 octets as defined in
[I-D.ietf-ospf-segment-routing-extensions]. [I-D.ietf-ospf-segment-routing-extensions].
Within the Range TLV, the prefix-to-SID mappings are advertised using Within the Range TLV, the prefix-to-SID mappings are advertised using
sub-TLVs as below: sub-TLVs as below:
Range TLV
Prefix-SID TLV (used as a sub-TLV in this context)
where:
o The Range TLV is defined in Section 2.3.4.
o The Prefix-SID TLV (used as sub-TLV in this context) is defined in
Section 2.3.1.
2.3.4.1. Advertisement Procedure for OSPF 2.3.4.1. Advertisement Procedure for OSPF
The OSPFv2/OSPFv3 Extended Prefix Range TLV is encoded in the Range The OSPFv2/OSPFv3 Extended Prefix Range TLV is encoded in the Range
TLV. The flags of the Range TLV have the semantic mapped to the TLV. The flags of the Range TLV have the semantic mapped to the
definition in [I-D.ietf-ospf-segment-routing-extensions] section 4 or definition 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.
Prefix-SID from the original OSPF Prefix SID sub-TLV is encoded using
the BGP-LS Prefix Attribute Prefix-SID as defined in Section 2.3.1 Then the prefix-to-SID mapping from the OSPF Prefix SID sub-TLV is
encoded using the BGP-LS Prefix-SID TLV as defined in Section 2.3.1
with the flags set according to the definition in 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.
2.3.4.2. Advertisement Procedure for IS-IS 2.3.4.2. Advertisement Procedure for IS-IS
The advertisement of a range of IS-IS Mapping Server bindings The IS-IS SID/Label Binding TLV, when used to signal mapping server
([I-D.ietf-isis-segment-routing-extensions]) is encoded in the Range label bindings, is encoded in the Range TLV. The flags of the Range
TLV using the following TLV/sub-TLV structure: TLV have the sematic mapped to the definition in
[I-D.ietf-isis-segment-routing-extensions] section 2.4.1.
Range TLV
Prefix-SID TLV (used as a sub-TLV in this context)
where:
o The Range TLV is defined in Section 2.3.4.
o The Prefix-SID TLV (used as sub-TLV in this context) is defined in Then the prefix-to-SID mappings from the IS-IS Prefix SID sub-TLV is
Section 2.3.1. encoded using the BGP-LS Prefix-SID TLV as defined in Section 2.3.1
with the flags set according to the definition in
[I-D.ietf-isis-segment-routing-extensions] section 2.4.4.1.
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.
+----------------------------------------+----------+---------------+ +---------------------------------------+----------+----------------+
| Description | Length | IS-IS TLV | | Description | Length | IS-IS TLV/sub- |
| | | /sub-TLV | | | | 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] | | SR Local Block | variable | 22 [3] |
| TLV | | | | SRMS Preference | 1 | 19 [4] |
| LAN Adjacency Segment Identifier (LAN- | variable | 32 [4] | | Adjacency Segment Identifier (Adj- | variable | 31 [5] |
| Adj-SID) TLV | | | | SID) | | |
| Prefix SID | variable | 3 [5] | | LAN Adjacency Segment Identifier | variable | 32 [6] |
| SID/Label TLV | variable | 1 [6] | | (LAN-Adj-SID) | | |
| Prefix Attribute Flags | variable | 4 [7] | | Prefix SID | variable | 3 [7] |
| Source Router ID | variable | 11/12 [8] | | Range | variable | 149 [8] |
| L2 Bundle Member TLV | variable | 25 [9] | | SID/Label TLV | variable | 1 [9] |
+----------------------------------------+----------+---------------+ | Prefix Attribute Flags | variable | 4 [10] |
| Source Router ID | variable | 11/12 [11] |
| L2 Bundle Member TLV | variable | 25 [12] |
+---------------------------------------+----------+----------------+
Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs
2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs 2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs
This section illustrate the OSPFv2 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 OSPFv2 and OSPFv3. in OSPFv2 and OSPFv3.
+--------------------------------------+----------+-----------------+ +-------------------------------------+----------+------------------+
| Description | Length | OSPFv2 TLV/sub- | | Description | Length | OSPFv2 TLV/sub- |
| | | TLV | | | | TLV |
+--------------------------------------+----------+-----------------+ +-------------------------------------+----------+------------------+
| SR Capabilities | variable | 9 [10] | | SR Capabilities | variable | 9 [13] |
| SR Algorithm | variable | 8 [11] | | SR Algorithm | variable | 8 [14] |
| Adjacency Segment Identifier (Adj- | variable | 2 [12] | | SR Local Block | variable | 14 [15] |
| SID) TLV | | | | SRMS Preference | 1 | 15 [16] |
| LAN Adjacency Segment Identifier | variable | 3 [13] | | Adjacency Segment Identifier (Adj- | variable | 2 [17] |
| (Adj-SID) TLV | | | | SID) | | |
| Prefix SID | variable | 2 [14] | | LAN Adjacency Segment Identifier | variable | 3 [18] |
| SID/Label TLV | variable | 1 [15] | | (Adj-SID) | | |
| Prefix Attribute Flags | variable | 4 [16] | | Prefix SID | variable | 2 [19] |
+--------------------------------------+----------+-----------------+ | Range | variable | 2 [20] |
| SID/Label TLV | variable | 1 [21] |
| Prefix Attribute Flags | variable | 4 [22] |
+-------------------------------------+----------+------------------+
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 [17] | | SR Capabilities | variable | 9 [23] |
| SR Algorithm | variable | 8 [18] | | SR Algorithm | variable | 8 [24] |
| Adjacency Segment Identifier (Adj- | variable | 5 [19] | | SR Local Block | variable | 14 [25] |
| SID) TLV | | | | SRMS Preference | 1 | 15 [26] |
| LAN Adjacency Segment Identifier | variable | 6 [20] | | Adjacency Segment Identifier (Adj- | variable | 5 [27] |
| (Adj-SID) TLV | | | | SID) | | |
| Prefix SID | variable | 4 [21] | | LAN Adjacency Segment Identifier | variable | 6 [28] |
| SID/Label TLV | variable | 3 [22] | | (Adj-SID) | | |
| Prefix Attribute Flags | variable | 4 [23] | | Prefix SID | variable | 4 [29] |
+--------------------------------------+----------+-----------------+ | Range | variable | 9 [30] |
| SID/Label TLV | variable | 7 [31] |
| Prefix Attribute Flags | variable | 4 [32] |
+-------------------------------------+----------+------------------+
Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs
3. Implementation Status 3. 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
skipping to change at page 21, line 36 skipping to change at page 22, line 36
5. Manageability Considerations 5. Manageability Considerations
This section is structured as recommended in [RFC5706]. This section is structured as recommended in [RFC5706].
The new protocol extensions introduced in this document augment the The new protocol extensions introduced in this document augment the
existing IGP topology information that was distributed via [RFC7752]. existing IGP topology information that was distributed via [RFC7752].
Procedures and protocol extensions defined in this document do not Procedures and protocol extensions defined in this document do not
affect the BGP protocol operations and management other than as affect the BGP protocol operations and management other than as
discussed in the Manageability Considerations section of [RFC7752]. discussed in the Manageability Considerations section of [RFC7752].
Specifically the determination of malformed attributes and their
handling follow the base BGP-LS specification [RFC7752].
5.1. Operational Considerations 5.1. Operational Considerations
No additional operation considerations are defined in this document. No additional operation considerations are defined in this document.
5.2. Management Considerations 5.2. Management Considerations
No additional management considerations are defined in this document. No additional management considerations are defined in this document.
6. Security Considerations 6. Security Considerations
skipping to change at page 23, line 48 skipping to change at page 25, line 10
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,
<https://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, <https://www.rfc-editor.org/info/rfc7794>. March 2016, <https://www.rfc-editor.org/info/rfc7794>.
[RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and
F. Baker, "OSPFv3 Link State Advertisement (LSA)
Extensibility", RFC 8362, DOI 10.17487/RFC8362, April
2018, <https://www.rfc-editor.org/info/rfc8362>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing Litkowski, S., and R. Shakir, "Segment Routing
Architecture", draft-ietf-spring-segment-routing-15 (work Architecture", draft-ietf-spring-segment-routing-15 (work
in progress), January 2018. in progress), January 2018.
[I-D.ietf-spring-segment-routing-ldp-interop]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., and
S. Litkowski, "Segment Routing interworking with LDP",
draft-ietf-spring-segment-routing-ldp-interop-11 (work in
progress), April 2018.
[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,
<https://www.rfc-editor.org/info/rfc5706>. <https://www.rfc-editor.org/info/rfc5706>.
[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,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
9.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-16#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-16#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-16#section-3.3
[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-3.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-16#section-2.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.3 extensions-16#section-2.2.2
[7] http://tools.ietf.org/html/RFC7794 [7] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-16#section-2.1
[8] http://tools.ietf.org/html/RFC7794 [8] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-16#section-2.4
[9] http://tools.ietf.org/html/draft-ietf-isis-l2bundles-05 [9] http://tools.ietf.org/html/draft-ietf-isis-segment-routing-
extensions-16#section-2.3
[10] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [10] http://tools.ietf.org/html/RFC7794
extensions-05#section-3.2
[11] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [11] http://tools.ietf.org/html/RFC7794
extensions-05#section-3.1
[12] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- [12] http://tools.ietf.org/html/draft-ietf-isis-l2bundles-07
extensions-05#section-7.1
[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-25#section-3.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-25#section-3.1
[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-25#section-3.3
[16] http://tools.ietf.org/html/RFC7684#section-2.1 [16] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
extensions-25#section-3.4
[17] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [17] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
routing-extensions-05#section-3.2 extensions-25#section-6.1
[18] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [18] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
routing-extensions-05#section-3.1 extensions-25#section-6.2
[19] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [19] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
routing-extensions-05#section-7.1 extensions-25#section-5
[20] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [20] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
routing-extensions-05#section-7.2 extensions-25#section-4
[21] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [21] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing-
routing-extensions-05#section-5 extensions-25#section-2.1
[22] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- [22] http://tools.ietf.org/html/RFC7684#section-2.1
routing-extensions-05#section-2.1
[23] http://tools.ietf.org/html/RFC5340#section-A.4.1.1 [23] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-3.2
[24] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-3.1
[25] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-3.3
[26] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-3.4
[27] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-6.1
[28] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-6.2
[29] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-5
[30] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-4
[31] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment-
routing-extensions-12#section-2.1
[32] http://tools.ietf.org/html/RFC8362#section-3.1
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi (editor)
Via Del Serafico, 200 Via Del Serafico, 200
Rome 00142 Rome 00142
Italy Italy
Email: stefano@previdi.net Email: stefano@previdi.net
Ketan Talaulikar Ketan Talaulikar
Cisco Systems, Inc. Cisco Systems, Inc.
S.No. 154/6, Phase I, Hinjawadi S.No. 154/6, Phase I, Hinjawadi
Pune 411 057 Pune 411 057
India India
Email: ketant@cisco.com Email: ketant@cisco.com
Clarence Filsfils Clarence Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
Brussels Brussels
Belgium Belgium
Email: cfilsfil@cisco.com Email: cfilsfil@cisco.com
Hannes Gredler Hannes Gredler
RtBrick Inc. RtBrick Inc.
 End of changes. 56 change blocks. 
152 lines changed or deleted 216 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/