draft-ietf-idr-bgp-ls-segment-routing-ext-05.txt   draft-ietf-idr-bgp-ls-segment-routing-ext-06.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: October 12, 2018 Cisco Systems, Inc. Expires: October 13, 2018 Cisco Systems, Inc.
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
M. Chen M. Chen
Huawei Technologies Huawei Technologies
April 10, 2018 April 11, 2018
BGP Link-State extensions for Segment Routing BGP Link-State extensions for Segment Routing
draft-ietf-idr-bgp-ls-segment-routing-ext-05 draft-ietf-idr-bgp-ls-segment-routing-ext-06
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 October 12, 2018. This Internet-Draft will expire on October 13, 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 32 skipping to change at page 2, line 32
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 . . . . . . . . . . . . . . . . . 9 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 . . . . . . . . . . . . . . . . 11
2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 11 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 . . . . . 17 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 . 18
3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19 3. Implementation Status . . . . . . . . . . . . . . . . . . . . 19
3.1. Advertisement of an IS-IS Prefix SID TLV . . . . . . . . 19 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
3.2. Advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV . . . . 19 4.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 20
3.3. Advertisement of a range of prefix-to-SID mappings in 5. Manageability Considerations . . . . . . . . . . . . . . . . 21
OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.1. Operational Considerations . . . . . . . . . . . . . . . 21
3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 20 5.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 21
4. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 21 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
6. Manageability Considerations . . . . . . . . . . . . . . . . 22 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Operational Considerations . . . . . . . . . . . . . . . 22 9.1. Normative References . . . . . . . . . . . . . . . . . . 22
6.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 22 9.2. Informative References . . . . . . . . . . . . . . . . . 23
9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23
10.1. Normative References . . . . . . . . . . . . . . . . . . 23
10.2. Informative References . . . . . . . . . . . . . . . . . 24
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25
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, OSPFv2 and advertised by the link-state routing protocols (IS-IS, OSPFv2 and
skipping to change at page 6, line 15 skipping to change at page 6, line 15
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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 4.
Length: Variable, 3 or 4 bytes Length: Variable, 3 or 4.
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
skipping to change at page 7, line 19 skipping to change at page 7, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 4.
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 Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on
receipt. 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) which encodes
the first label in the range.
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 | |
+- -+ +- -+
| | | |
+ + + +
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 4.
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(s) of labels the The SR Local Block (SRLB) TLV contains the range(s) of labels the
node has reserved for local SIDs. Local SIDs are used, e.g., in IGP node has reserved for local SIDs. Local SIDs are used, e.g., in IGP
(IS-IS, OSPF) for Adjacency-SIDs, and may also be allocated by (IS-IS, OSPF) for Adjacency-SIDs, and may also be allocated by
skipping to change at page 8, line 36 skipping to change at page 8, line 38
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 4.
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 Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on
receipt. 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) which encodes
the first label in the range.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Preference | | Preference |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Type: TBD, see Section 5. Type: TBD, see Section 4.
Length: 1. Length: 1.
Preference: 1 octet. Unsigned 8 bit SRMS preference. Preference: 1 octet. Unsigned 8 bit SRMS preference.
The use of the SRMS Preference TLV is defined in The use of the SRMS Preference TLV is defined in
[I-D.ietf-isis-segment-routing-extensions], [I-D.ietf-isis-segment-routing-extensions],
[I-D.ietf-ospf-segment-routing-extensions] and [I-D.ietf-ospf-segment-routing-extensions] and
[I-D.ietf-ospf-ospfv3-segment-routing-extensions]. [I-D.ietf-ospf-ospfv3-segment-routing-extensions].
skipping to change at page 10, line 27 skipping to change at page 10, line 30
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Weight | Reserved | | Flags | Weight | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label/Index (variable) | | SID/Label/Index (variable) |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 4.
Length: Variable. Length: Variable, 7 or 8 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.
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.
skipping to change at page 11, line 25 skipping to change at page 11, line 29
+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Label/Index (variable) | | SID/Label/Index (variable) |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 4.
Length: Variable. Length: Variable. For ISIS it would be 13 or 14 depending on
Label or Index encoding of the SID. For OSPF it would be 11 or 12
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.
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.
skipping to change at page 12, line 23 skipping to change at page 12, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| L2 Bundle Member Descriptor | | L2 Bundle Member Descriptor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// Link attribute sub-TLVs(variable) // // Link attribute sub-TLVs(variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 4.
Length: Variable. Length: Variable.
L2 Bundle Member Descriptor: A Link Local Identifier as defined in L2 Bundle Member Descriptor: A Link Local Identifier as defined in
[RFC4202]. [RFC4202].
Link attributes for L2 Bundle Member Links are advertised as sub-TLVs Link attributes for L2 Bundle Member Links are advertised as sub-TLVs
of the L2Bundle Member Attribute TLV. The sub-TLVs are identical to of the L2Bundle Member Attribute TLV. The sub-TLVs are identical to
existing BGP-LS TLVs as identified in the table below. existing BGP-LS TLVs as identified in the table below.
skipping to change at page 14, line 35 skipping to change at page 14, line 35
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Algorithm | Reserved | | Flags | Algorithm | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SID/Index/Label (variable) | | SID/Index/Label (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, see Section 5. Type: TBD, see Section 4.
Length: Variable Length: Variable, 7 or 8 depending on Label or Index encoding of
the SID
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],
skipping to change at page 15, line 40 skipping to change at page 15, line 40
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 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. OSPFv2 flags are
defined in [RFC7684], for OSPFv3 this maps to the Prefix Options defined in [RFC7684], for OSPFv3 this maps to the Prefix Options
field defined in [RFC5340] and IS-IS flags are defined in 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
Prefix Attribute Flags 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
skipping to change at page 16, line 24 skipping to change at page 16, line 24
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) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD, see Section 5. 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.
The semantic of the Source Router-ID TLV is defined in [RFC7794]. The semantic of the Source Router-ID TLV is defined in [RFC7794].
2.3.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
skipping to change at page 17, line 19 skipping to change at page 17, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 4.
Length is 4. Length: variable
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 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-SID TLV (used as sub-TLV in this Within the Range TLV, the prefix-to-SID mappings are advertised using
context) MAY be present. sub-TLVs as below:
2.3.4.1. Advertisement Procedure for OSPF
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
definition in [I-D.ietf-ospf-segment-routing-extensions] section 4 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The
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
with the flags set according to the definition in
[I-D.ietf-ospf-segment-routing-extensions] section 5 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5.
2.3.4.2. Advertisement Procedure for IS-IS
The advertisement of a range of IS-IS Mapping Server bindings
([I-D.ietf-isis-segment-routing-extensions]) is encoded in the Range
TLV using the following TLV/sub-TLV structure:
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.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.
+----------------------------------------+----------+---------------+ +----------------------------------------+----------+---------------+
skipping to change at page 19, line 22 skipping to change at page 19, line 39
| SID) TLV | | | | SID) TLV | | |
| LAN Adjacency Segment Identifier | variable | 6 [20] | | LAN Adjacency Segment Identifier | variable | 6 [20] |
| (Adj-SID) TLV | | | | (Adj-SID) TLV | | |
| Prefix SID | variable | 4 [21] | | Prefix SID | variable | 4 [21] |
| SID/Label TLV | variable | 3 [22] | | SID/Label TLV | variable | 3 [22] |
| Prefix Attribute Flags | variable | 4 [23] | | 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. Implementation Status
The following sections describe the different operations for the
propagation of SR TLVs into BGP-LS from OSPFv2, OSPFv3 and ISIS
protocols.
3.1. Advertisement of an IS-IS Prefix SID TLV
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
Prefix-SID as defined in Section 2.3.1. The flags in the Prefix-
SID TLV have the semantic defined in
[I-D.ietf-isis-segment-routing-extensions] section 2.1.
3.2. Advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV
The advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV has following
rules:
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
the Prefix-SID TLV have the semantic defined in
[I-D.ietf-ospf-segment-routing-extensions] section 5 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5.
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
following rules:
The OSPFv2/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-
LS Prefix Attribute Range TLV as defined in Section 2.3.4. The
flags of the Range TLV have the semantic mapped to the definition
in [I-D.ietf-ospf-segment-routing-extensions] section 4 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The
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 with the flags set according to the definition in
[I-D.ietf-ospf-segment-routing-extensions] section 5 or
[I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5.
3.4. Advertisement of a range of IS-IS SR bindings
The advertisement of a range of IS-IS Mapping Server bindings
([I-D.ietf-isis-segment-routing-extensions]) is encoded using the
following TLV/sub-TLV structure:
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.
4. Implementation Status
Note to RFC Editor: Please remove this section prior to publication, Note to RFC Editor: Please remove this section prior to publication,
as well as the reference to RFC 7942. as well as the reference to RFC 7942.
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC7942]. Internet-Draft, and is based on a proposal described in [RFC7942].
The description of implementations in this section is intended to The description of implementations in this section is intended to
assist the IETF in its decision processes in progressing drafts to assist the IETF in its decision processes in progressing drafts to
RFCs. Please note that the listing of any individual implementation RFCs. Please note that the listing of any individual implementation
skipping to change at page 21, line 18 skipping to change at page 20, line 25
Several early implementations exist and will be reported in detail in Several early implementations exist and will be reported in detail in
a forthcoming version of this document. For purposes of early a forthcoming version of this document. For purposes of early
interoperability testing, when no FCFS code point was available, interoperability testing, when no FCFS code point was available,
implementations have made use of the values described in Table 8. implementations have made use of the values described in Table 8.
It will ease implementation interoperability and deployment if the It will ease implementation interoperability and deployment if the
value could be preserved also due to the large amount of codepoints value could be preserved also due to the large amount of codepoints
this draft requires. However, when IANA-assigned values are this draft requires. However, when IANA-assigned values are
available, implementations will be updated to use them. available, implementations will be updated to use them.
5. IANA Considerations 4. IANA Considerations
This document requests assigning code-points from the registry "BGP- This document requests assigning code-points from the registry "BGP-
LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute
TLVs" based on table Table 8. The column "IS-IS TLV/Sub-TLV" defined TLVs" based on table Table 8. The column "IS-IS TLV/Sub-TLV" defined
in the registry does not require any value and should be left empty. in the registry does not require any value and should be left empty.
5.1. TLV/Sub-TLV Code Points Summary 4.1. TLV/Sub-TLV Code Points Summary
This section contains the global table of all TLVs/sub-TLVs defined This section contains the global table of all TLVs/sub-TLVs defined
in this document. in this document.
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| TLV Code | Description | Reference | | TLV Code | Description | Reference |
| Point | | | | Point | | |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| 1034 | SR Capabilities | Section 2.1.2 | | 1034 | SR Capabilities | Section 2.1.2 |
| 1035 | SR Algorithm | Section 2.1.3 | | 1035 | SR Algorithm | Section 2.1.3 |
skipping to change at page 22, line 5 skipping to change at page 21, line 27
| 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 | Prefix Attribute Flags | 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 5. Manageability Considerations
This section is structured as recommended in [RFC5706]. This section is structured as recommended in [RFC5706].
6.1. Operational Considerations 5.1. Operational Considerations
6.1.1. Operations 5.1.1. Operations
Existing BGP and BGP-LS operational procedures apply. No additional Existing BGP and BGP-LS operational procedures apply. No additional
operation procedures are defined in this document. operation procedures are defined in this document.
7. Security Considerations 6. Security Considerations
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 7. 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 Peter Psenak
Cisco Systems Cisco Systems
Email: ppsenak@cisco.com 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
skipping to change at page 22, line 48 skipping to change at page 22, line 20
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. Acknowledgements 8. Acknowledgements
The authors would like to thank Jeffrey Haas for his review of this The authors would like to thank Jeffrey Haas and Aijun Wang for their
document. review of this document and their comments.
10. References 9. References
10.1. Normative References 9.1. Normative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C. Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C.
Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering
Performance Metric Extensions", draft-ietf-idr-te-pm- Performance Metric Extensions", draft-ietf-idr-te-pm-
bgp-10 (work in progress), March 2018. bgp-10 (work in progress), March 2018.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,
skipping to change at page 24, line 21 skipping to change at page 23, line 46
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>.
10.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.
[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 24, line 25
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>.
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
 End of changes. 42 change blocks. 
123 lines changed or deleted 91 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/