draft-ietf-idr-bgp-ls-segment-routing-ext-04.txt   draft-ietf-idr-bgp-ls-segment-routing-ext-05.txt 
Inter-Domain Routing S. Previdi, Ed. Inter-Domain Routing S. Previdi, Ed.
Internet-Draft K. Talaulikar Internet-Draft K. Talaulikar
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: July 29, 2018 Cisco Systems, Inc. Expires: October 12, 2018 Cisco Systems, Inc.
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
M. Chen M. Chen
Huawei Technologies Huawei Technologies
January 25, 2018 April 10, 2018
BGP Link-State extensions for Segment Routing BGP Link-State extensions for Segment Routing
draft-ietf-idr-bgp-ls-segment-routing-ext-04 draft-ietf-idr-bgp-ls-segment-routing-ext-05
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 48 skipping to change at page 1, line 48
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 July 29, 2018. This Internet-Draft will expire on October 12, 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 29 skipping to change at page 2, line 29
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 . . . . . . . . . . . . . . . . . 8 2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 8
2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 8 2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 9
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. 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 . . . . . 17 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 17
skipping to change at page 3, line 7 skipping to change at page 3, line 7
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. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
9.1. Normative References . . . . . . . . . . . . . . . . . . 23 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.2. Informative References . . . . . . . . . . . . . . . . . 24 10.1. Normative References . . . . . . . . . . . . . . . . . . 23
9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25 10.2. Informative References . . . . . . . . . . . . . . . . . 24
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25
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
skipping to change at page 7, line 10 skipping to change at page 7, line 10
[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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | RESERVED | | Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Range Size | | Range Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// SID/Label sub-TLV (variable) // // SID/Label sub-TLV (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD, see Section 5. Type: TBD, see Section 5.
Length: Variable. Length: Variable.
Flags: 1 octet of flags as defined in Flags: 1 octet of flags as defined in
[I-D.ietf-isis-segment-routing-extensions]. [I-D.ietf-isis-segment-routing-extensions].
Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on
receipt.
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).
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:
skipping to change at page 8, line 25 skipping to change at page 8, line 27
range of local SIDs available, it is required that the node range of local SIDs available, it is required that the node
advertises its SRLB. advertises its SRLB.
The SRLB TLV has the following format: The SRLB TLV has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | RESERVED | | Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Range Size | | Range Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// SID/Label sub-TLV (variable) // // SID/Label sub-TLV (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBD, see Section 5. Type: TBD, see Section 5.
Length: Variable. Length: Variable.
Flags: 1 octet of flags. None are defined at this stage. Flags: 1 octet of flags. None are defined at this stage.
Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on
receipt.
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).
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
skipping to change at page 10, line 32 skipping to change at page 10, line 38
Length: Variable. Length: Variable.
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.
Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on
receipt.
SID/Index/Label: Label or index value depending on the flags SID/Index/Label: Label or index value depending on the flags
setting as defined in [I-D.ietf-isis-segment-routing-extensions], setting as defined in [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and [I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-ospf-ospfv3-segment-routing-extensions].
2.2.2. LAN Adjacency SID TLV 2.2.2. LAN Adjacency SID TLV
The LAN Adjacency SID (LAN-Adj-SID-SID) TLV has the following format: The LAN Adjacency SID (LAN-Adj-SID-SID) TLV has the following format:
0 1 2 3 0 1 2 3
skipping to change at page 11, line 36 skipping to change at page 11, line 36
Length: Variable. Length: Variable.
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.
Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on
receipt.
SID/Index/Label: Label or index value depending on the flags SID/Index/Label: Label or index value depending on the flags
setting as defined in [I-D.ietf-isis-segment-routing-extensions], setting as defined in [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and [I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-ospf-ospfv3-segment-routing-extensions].
2.2.3. L2 Bundle Member 2.2.3. L2 Bundle Member
The L2 Bundle Member Attribute TLV identifies an L2 Bundle Member The L2 Bundle Member Attribute TLV identifies an L2 Bundle Member
link which in turn is associated with a parent L3 link. The L3 link link which in turn is associated with a parent L3 link. The L3 link
is described by the Link NLRI defined in [RFC7752] and the L2 Bundle is described by the Link NLRI defined in [RFC7752] and the L2 Bundle
skipping to change at page 14, line 41 skipping to change at page 14, line 41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 5.
Length: Variable Length: Variable
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
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],
skipping to change at page 16, line 41 skipping to change at page 16, line 41
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 can ONLY be added to the Prefix Attribute whose local
node in the corresponding Prefix NLRI is the node that originates the node in the corresponding Prefix NLRI is the node that originates the
corresponding SR TLV. corresponding SR TLV.
When the range TLV is used in order to advertise a range of prefix- When the range TLV is used in order to advertise a range of prefix-
to-SID mappings as defined in 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 the
Range TLV is attached to MUST be advertised as a non-routing prefix Range TLV is attached to 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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// sub-TLVs // // sub-TLVs //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Figure 2: Range TLV format Figure 2: Range TLV format
Type: TBD, see Section 5. Type: TBD, see Section 5.
Length is 4. Length is 4.
Flags: as defined in [I-D.ietf-ospf-segment-routing-extensions], Flags: as defined in [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]. [I-D.ietf-isis-segment-routing-extensions].
Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on
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-SID TLV (used as sub-TLV in this Within the Range TLV, the Prefix-SID TLV (used as sub-TLV in this
context) MAY be present. context) MAY be present.
2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs
This section illustrate the IS-IS Segment Routing Extensions TLVs and This section illustrate the IS-IS Segment Routing Extensions TLVs and
sub-TLVs mapped to the ones defined in this document. sub-TLVs mapped to the ones defined in this document.
skipping to change at page 22, line 48 skipping to change at page 22, line 48
Email: acee@cisco.com Email: acee@cisco.com
Saikat Ray Saikat Ray
Individual Individual
Email: raysaikat@gmail.com Email: raysaikat@gmail.com
Jeff Tantsura Jeff Tantsura
Nuage Networks Nuage Networks
Email: jefftant.ietf@gmail.com Email: jefftant.ietf@gmail.com
9. References 9. Acknowledgements
9.1. Normative References
The authors would like to thank Jeffrey Haas for his review of this
document.
10. References
10.1. Normative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Ginsberg, L., Previdi, S., Wu, Q., Gredler, H., Ray, S., Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C.
Tantsura, J., and C. Filsfils, "BGP-LS Advertisement of Filsfils, "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-10 (work in progress), March 2018.
2017.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-15 (work in progress), December 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., Filsfils, C., Previdi, S., 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-10 (work in progress), segment-routing-extensions-11 (work in progress), January
September 2017. 2018.
[I-D.ietf-ospf-segment-routing-extensions] [I-D.ietf-ospf-segment-routing-extensions]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., and J. Tantsura, "OSPF Shakir, R., Henderickx, W., and J. Tantsura, "OSPF
Extensions for Segment Routing", draft-ietf-ospf-segment- Extensions for Segment Routing", draft-ietf-ospf-segment-
routing-extensions-24 (work in progress), December 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,
skipping to change at page 24, line 21 skipping to change at page 24, line 21
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>.
9.2. Informative References 10.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.
[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,
<https://www.rfc-editor.org/info/rfc4272>. <https://www.rfc-editor.org/info/rfc4272>.
skipping to change at page 25, line 5 skipping to change at page 25, line 5
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,
<https://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,
<https://www.rfc-editor.org/info/rfc7942>. <https://www.rfc-editor.org/info/rfc7942>.
9.3. URIs 10.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
 End of changes. 22 change blocks. 
25 lines changed or deleted 49 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/