< draft-ietf-isis-segment-routing-extensions-21.txt   draft-ietf-isis-segment-routing-extensions-22.txt >
IS-IS for IP Internets S. Previdi, Ed. IS-IS for IP Internets S. Previdi, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track L. Ginsberg, Ed. Intended status: Standards Track L. Ginsberg, Ed.
Expires: June 6, 2019 C. Filsfils Expires: June 16, 2019 C. Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
A. Bashandy A. Bashandy
Individual Individual
H. Gredler H. Gredler
RtBrick Inc. RtBrick Inc.
B. Decraene B. Decraene
Orange Orange
December 3, 2018 December 13, 2018
IS-IS Extensions for Segment Routing IS-IS Extensions for Segment Routing
draft-ietf-isis-segment-routing-extensions-21 draft-ietf-isis-segment-routing-extensions-22
Abstract Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end Segment Routing (SR) allows for a flexible definition of end-to-end
paths within IGP topologies by encoding paths as sequences of paths within IGP topologies by encoding paths as sequences of
topological sub-paths, called "segments". These segments are topological sub-paths, called "segments". These segments are
advertised by the link-state routing protocols (IS-IS and OSPF). advertised by the link-state routing protocols (IS-IS and OSPF).
This draft describes the necessary IS-IS extensions that need to be This draft describes the necessary IS-IS extensions that need to be
introduced for Segment Routing operating on an MPLS data-plane. introduced for Segment Routing operating on an MPLS data-plane.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 June 6, 2019. This Internet-Draft will expire on June 16, 2019.
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 3, line 33 skipping to change at page 3, line 33
represent a hop over a specific adjacency between two nodes in the represent a hop over a specific adjacency between two nodes in the
IGP. A prefix segment is typically a multi-hop path while an IGP. A prefix segment is typically a multi-hop path while an
adjacency segment, in most of the cases, is a one-hop path. SR's adjacency segment, in most of the cases, is a one-hop path. SR's
control-plane can be applied to both IPv6 and MPLS data-planes, and control-plane can be applied to both IPv6 and MPLS data-planes, and
do not require any additional signaling (other than the regular IGP). do not require any additional signaling (other than the regular IGP).
For example, when used in MPLS networks, SR paths do not require any For example, when used in MPLS networks, SR paths do not require any
LDP or RSVP-TE signaling. Still, SR can interoperate in the presence LDP or RSVP-TE signaling. Still, SR can interoperate in the presence
of LSPs established with RSVP or LDP. of LSPs established with RSVP or LDP.
There are additional segment types, e.g., Binding SID defined in There are additional segment types, e.g., Binding SID defined in
[I-D.ietf-spring-segment-routing]. This draft also defines an [RFC8402]. This draft also defines an advertisement for one type of
advertisement for one type of BindingSID: the Mirror Context segment. BindingSID: the Mirror Context segment.
This draft describes the necessary IS-IS extensions that need to be This draft describes the necessary IS-IS extensions that need to be
introduced for Segment Routing operating on an MPLS data-plane. introduced for Segment Routing operating on an MPLS data-plane.
Segment Routing architecture is described in Segment Routing architecture is described in [RFC8402].
[I-D.ietf-spring-segment-routing].
Segment Routing use cases are described in [RFC7855]. Segment Routing use cases are described in [RFC7855].
2. Segment Routing Identifiers 2. Segment Routing Identifiers
Segment Routing architecture ([I-D.ietf-spring-segment-routing]) Segment Routing architecture ([RFC8402]) defines different types of
defines different types of Segment Identifiers (SID). This document Segment Identifiers (SID). This document defines the IS-IS encodings
defines the IS-IS encodings for the IGP-Prefix-SID, the IGP- for the IGP-Prefix-SID, the IGP-Adjacency-SID, the IGP-LAN-Adjacency-
Adjacency-SID, the IGP-LAN-Adjacency-SID and the Binding-SID. SID and the Binding-SID.
2.1. Prefix Segment Identifier (Prefix-SID Sub-TLV) 2.1. Prefix Segment Identifier (Prefix-SID Sub-TLV)
A new IS-IS sub-TLV is defined: the Prefix Segment Identifier sub-TLV A new IS-IS sub-TLV is defined: the Prefix Segment Identifier sub-TLV
(Prefix-SID sub-TLV). (Prefix-SID sub-TLV).
The Prefix-SID sub-TLV carries the Segment Routing IGP-Prefix-SID as The Prefix-SID sub-TLV carries the Segment Routing IGP-Prefix-SID as
defined in [I-D.ietf-spring-segment-routing]. The 'Prefix SID' MUST defined in [RFC8402]. The 'Prefix SID' MUST be unique within a given
be unique within a given IGP domain (when the L-flag is not set). IGP domain (when the L-flag is not set). The 'Prefix SID' MUST carry
The 'Prefix SID' MUST carry an index (when the V-flag is not set) an index (when the V-flag is not set) that determines the actual SID/
that determines the actual SID/label value inside the set of all label value inside the set of all advertised SID/label ranges of a
advertised SID/label ranges of a given router. A receiving router given router. A receiving router uses the index to determine the
uses the index to determine the actual SID/label value in order to actual SID/label value in order to construct forwarding state to a
construct forwarding state to a particular destination router. particular destination router.
In many use-cases a 'stable transport' IP Address is overloaded as an In many use-cases a 'stable transport' IP Address is overloaded as an
identifier of a given node. Because the IP Prefixes may be re- identifier of a given node. Because the IP Prefixes may be re-
advertised into other levels there may be some ambiguity (e.g. advertised into other levels there may be some ambiguity (e.g.
Originating router vs. L1L2 router) for which node a particular IP Originating router vs. L1L2 router) for which node a particular IP
prefix serves as identifier. The Prefix-SID sub-TLV contains the prefix serves as identifier. The Prefix-SID sub-TLV contains the
necessary flags to disambiguate IP Prefix to node mappings. necessary flags to disambiguate IP Prefix to node mappings.
Furthermore if a given node has several 'stable transport' IP Furthermore if a given node has several 'stable transport' IP
addresses there are flags to differentiate those among other IP addresses there are flags to differentiate those among other IP
Prefixes advertised from a given node. Prefixes advertised from a given node.
skipping to change at page 5, line 38 skipping to change at page 5, line 38
R-Flag: Re-advertisement flag. If set, then the prefix to R-Flag: Re-advertisement flag. If set, then the prefix to
which this Prefix-SID is attached, has been propagated by the which this Prefix-SID is attached, has been propagated by the
router either from another level (i.e., from level-1 to level-2 router either from another level (i.e., from level-1 to level-2
or the opposite) or from redistribution (e.g.: from another or the opposite) or from redistribution (e.g.: from another
protocol). protocol).
N-Flag: Node-SID flag. If set, then the Prefix-SID refers to N-Flag: Node-SID flag. If set, then the Prefix-SID refers to
the router identified by the prefix. Typically, the N-Flag is the router identified by the prefix. Typically, the N-Flag is
set on Prefix-SIDs attached to a router loopback address. The set on Prefix-SIDs attached to a router loopback address. The
N-Flag is set when the Prefix-SID is a Node-SID as described in N-Flag is set when the Prefix-SID is a Node-SID as described in
[I-D.ietf-spring-segment-routing]. [RFC8402].
P-Flag: no-PHP flag. If set, then the penultimate hop MUST NOT P-Flag: no-PHP flag. If set, then the penultimate hop MUST NOT
pop the Prefix-SID before delivering the packet to the node pop the Prefix-SID before delivering the packet to the node
that advertised the Prefix-SID. that advertised the Prefix-SID.
E-Flag: Explicit-Null Flag. If set, any upstream neighbor of E-Flag: Explicit-Null Flag. If set, any upstream neighbor of
the Prefix-SID originator MUST replace the Prefix-SID with a the Prefix-SID originator MUST replace the Prefix-SID with a
Prefix-SID having an Explicit-NULL value (0 for IPv4 and 2 for Prefix-SID having an Explicit-NULL value (0 for IPv4 and 2 for
IPv6) before forwarding the packet. IPv6) before forwarding the packet.
skipping to change at page 9, line 23 skipping to change at page 9, line 23
levels MAY change the setting of the L and V flags in case a local levels MAY change the setting of the L and V flags in case a local
label value is encoded in the Prefix-SID instead of the received label value is encoded in the Prefix-SID instead of the received
value. value.
2.2. Adjacency Segment Identifier 2.2. Adjacency Segment Identifier
A new IS-IS sub-TLV is defined: the Adjacency Segment Identifier sub- A new IS-IS sub-TLV is defined: the Adjacency Segment Identifier sub-
TLV (Adj-SID sub-TLV). TLV (Adj-SID sub-TLV).
The Adj-SID sub-TLV is an optional sub-TLV carrying the Segment The Adj-SID sub-TLV is an optional sub-TLV carrying the Segment
Routing IGP-Adjacency-SID as defined in Routing IGP-Adjacency-SID as defined in [RFC8402] with flags and
[I-D.ietf-spring-segment-routing] with flags and fields that may be fields that may be used, in future extensions of Segment Routing, for
used, in future extensions of Segment Routing, for carrying other carrying other types of SIDs.
types of SIDs.
IS-IS adjacencies are advertised using one of the IS-Neighbor TLVs IS-IS adjacencies are advertised using one of the IS-Neighbor TLVs
below: below:
TLV-22 (Extended IS reachability)[RFC5305] TLV-22 (Extended IS reachability)[RFC5305]
TLV-222 (Multitopology IS)[RFC5120] TLV-222 (Multitopology IS)[RFC5120]
TLV-23 (IS Neighbor Attribute)[RFC5311] TLV-23 (IS Neighbor Attribute)[RFC5311]
skipping to change at page 11, line 10 skipping to change at page 11, line 10
P-Flag. Persistent flag. When set, the P-Flag indicates that P-Flag. Persistent flag. When set, the P-Flag indicates that
the Adj-SID is persistently allocated, i.e., the Adj-SID value the Adj-SID is persistently allocated, i.e., the Adj-SID value
remains consistent across router restart and/or interface flap. remains consistent across router restart and/or interface flap.
Other bits: MUST be zero when originated and ignored when Other bits: MUST be zero when originated and ignored when
received. received.
Weight: 1 octet. The value represents the weight of the Adj-SID Weight: 1 octet. The value represents the weight of the Adj-SID
for the purpose of load balancing. The use of the weight is for the purpose of load balancing. The use of the weight is
defined in [I-D.ietf-spring-segment-routing]. defined in [RFC8402].
SID/Index/Label as defined in Section 2.1.1.1. SID/Index/Label as defined in Section 2.1.1.1.
An SR capable router MAY allocate an Adj-SID for each of its An SR capable router MAY allocate an Adj-SID for each of its
adjacencies and SHOULD set the B-Flag when the adjacency is adjacencies and SHOULD set the B-Flag when the adjacency is
eligible for protection (IP or MPLS). eligible for protection (IP or MPLS).
An SR capable router MAY allocate more than one Adj-SID to an An SR capable router MAY allocate more than one Adj-SID to an
adjacency. adjacency.
An SR capable router MAY allocate the same Adj-SID to different An SR capable router MAY allocate the same Adj-SID to different
adjacencies. adjacencies.
When the P-flag is not set, the Adj-SID MAY be persistent. When When the P-flag is not set, the Adj-SID MAY be persistent. When
the P-flag is set, the Adj-SID MUST be persistent. the P-flag is set, the Adj-SID MUST be persistent.
Examples of use of the Adj-SID sub-TLV are described in Examples of use of the Adj-SID sub-TLV are described in [RFC8402].
[I-D.ietf-spring-segment-routing].
The F-flag is used in order for the router to advertise the The F-flag is used in order for the router to advertise the
outgoing encapsulation of the adjacency the Adj-SID is attached outgoing encapsulation of the adjacency the Adj-SID is attached
to. to.
2.2.2. Adjacency Segment Identifiers in LANs 2.2.2. Adjacency Segment Identifiers in LANs
In LAN subnetworks, the Designated Intermediate System (DIS) is In LAN subnetworks, the Designated Intermediate System (DIS) is
elected and originates the Pseudonode-LSP (PN-LSP) including all elected and originates the Pseudonode-LSP (PN-LSP) including all
neighbors of the DIS. neighbors of the DIS.
skipping to change at page 12, line 40 skipping to change at page 12, line 40
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|F|B|V|L|S|P| | |F|B|V|L|S|P| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
where F, B, V, L, S and P flags are defined in Section 2.2.1. where F, B, V, L, S and P flags are defined in Section 2.2.1.
Other bits: MUST be zero when originated and ignored when Other bits: MUST be zero when originated and ignored when
received. received.
Weight: 1 octet. The value represents the weight of the Adj-SID Weight: 1 octet. The value represents the weight of the Adj-SID
for the purpose of load balancing. The use of the weight is for the purpose of load balancing. The use of the weight is
defined in [I-D.ietf-spring-segment-routing]. defined in [RFC8402].
System-ID: 6 octets of IS-IS System-ID of length "ID Length" as System-ID: 6 octets of IS-IS System-ID of length "ID Length" as
defined in [ISO10589]. defined in [ISO10589].
SID/Index/Label as defined in Section 2.1.1.1. SID/Index/Label as defined in Section 2.1.1.1.
Multiple LAN-Adj-SID sub-TLVs MAY be encoded. Note that this sub-TLV Multiple LAN-Adj-SID sub-TLVs MAY be encoded. Note that this sub-TLV
MUST NOT appear in TLV 141. MUST NOT appear in TLV 141.
When the P-flag is not set, the LAN-Adj-SID MAY be persistent. When When the P-flag is not set, the LAN-Adj-SID MAY be persistent. When
skipping to change at page 14, line 17 skipping to change at page 14, line 17
2.4. SID/Label Binding TLV 2.4. SID/Label Binding TLV
The SID/Label Binding TLV MAY be originated by any router in an IS-IS The SID/Label Binding TLV MAY be originated by any router in an IS-IS
domain. There are multiple uses of the SID/Label Binding TLV. domain. There are multiple uses of the SID/Label Binding TLV.
The SID/Label Binding TLV may be used to advertise prefixes to SID/ The SID/Label Binding TLV may be used to advertise prefixes to SID/
Label mappings. This functionality is called the Segment Routing Label mappings. This functionality is called the Segment Routing
Mapping Server (SRMS). The behavior of the SRMS is defined in Mapping Server (SRMS). The behavior of the SRMS is defined in
[I-D.ietf-spring-segment-routing-ldp-interop]. [I-D.ietf-spring-segment-routing-ldp-interop].
The SID/Label BInding TLV may also be used to advertise a Mirror SID The SID/Label Binding TLV may also be used to advertise a Mirror SID
to advertise the ability to process traffic originally destined to to advertise the ability to process traffic originally destined to
another IGP node. This behavior is defined in another IGP node. This behavior is defined in [RFC8402].
[I-D.ietf-spring-segment-routing].
The SID/Label Binding TLV has Type TBD (suggested value 149), and has The SID/Label Binding TLV has Type TBD (suggested value 149), and has
the following format: 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 | Flags | RESERVED | | Type | Length | Flags | RESERVED |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Range | Prefix Length | Prefix | | Range | Prefix Length | Prefix |
skipping to change at page 15, line 28 skipping to change at page 15, line 28
|F|M|S|D|A| | |F|M|S|D|A| |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
where: where:
F-Flag: Address Family flag. If unset, then the Prefix carries an F-Flag: Address Family flag. If unset, then the Prefix carries an
IPv4 Prefix. If set then the Prefix carries an IPv6 Prefix. IPv4 Prefix. If set then the Prefix carries an IPv6 Prefix.
M-Flag: Mirror Context flag. Set if the advertised SID M-Flag: Mirror Context flag. Set if the advertised SID
corresponds to a mirrored context. The use of the M flag is corresponds to a mirrored context. The use of the M flag is
described in [I-D.ietf-spring-segment-routing]. described in [RFC8402].
S-Flag: If set, the SID/Label Binding TLV SHOULD be flooded across S-Flag: If set, the SID/Label Binding TLV SHOULD be flooded across
the entire routing domain. If the S flag is not set, the SID/ the entire routing domain. If the S flag is not set, the SID/
Label Binding TLV MUST NOT be leaked between levels. This bit Label Binding TLV MUST NOT be leaked between levels. This bit
MUST NOT be altered during the TLV leaking. MUST NOT be altered during the TLV leaking.
D-Flag: when the SID/Label Binding TLV is leaked from level-2 to D-Flag: when the SID/Label Binding TLV is leaked from level-2 to
level-1, the D bit MUST be set. Otherwise, this bit MUST be level-1, the D bit MUST be set. Otherwise, this bit MUST be
clear. SID/Label Binding TLVs with the D bit set MUST NOT be clear. SID/Label Binding TLVs with the D bit set MUST NOT be
leaked from level-1 to level-2. This is to prevent TLV looping leaked from level-1 to level-2. This is to prevent TLV looping
skipping to change at page 18, line 13 skipping to change at page 18, line 13
length 25 up to 32, ...., 16 octets for prefix length 113 up to 128). length 25 up to 32, ...., 16 octets for prefix length 113 up to 128).
2.4.4. Mapping Server Prefix-SID 2.4.4. Mapping Server Prefix-SID
The Prefix-SID sub-TLV (suggested value 3) is defined in Section 2.1 The Prefix-SID sub-TLV (suggested value 3) is defined in Section 2.1
and contains the SID/index/label value associated with the prefix and and contains the SID/index/label value associated with the prefix and
range. The Prefix-SID SubTLV MUST be present in the SID/Label range. The Prefix-SID SubTLV MUST be present in the SID/Label
Binding TLV unless the M-flag is set in the Flags field of the parent Binding TLV unless the M-flag is set in the Flags field of the parent
TLV. TLV.
A node receiving a MS entry for a prefix MUST check the existence of A node receiving an SRMS entry for a prefix MUST check the existence
such prefix in its link-state database prior to consider and use the of such prefix in its link-state database prior to consider and use
associated SID. the associated SID.
2.4.4.1. Prefix-SID Flags 2.4.4.1. Prefix-SID Flags
The Prefix-SID flags are defined in Section 2.1. The Mapping Server The Prefix-SID flags are defined in Section 2.1. The Mapping Server
MAY advertise a mapping with the N flag set when the prefix being MAY advertise a mapping with the N flag set when the prefix being
mapped is known in the link-state topology with a mask length of 32 mapped is known in the link-state topology with a mask length of 32
(IPv4) or 128 (IPv6) and when the prefix represents a node. The (IPv4) or 128 (IPv6) and when the prefix represents a node. The
mechanisms through which the operator defines that a prefix mechanisms through which the operator defines that a prefix
represents a node are outside the scope of this document (typically represents a node are outside the scope of this document (typically
it will be through configuration). it will be through configuration).
skipping to change at page 21, line 33 skipping to change at page 21, line 33
Range: 3 octets. Range: 3 octets.
SID/Label sub-TLV (as defined in Section 2.3). SID/Label sub-TLV (as defined in Section 2.3).
SID/Label sub-TLV contains the first value of the SRGB while the SID/Label sub-TLV contains the first value of the SRGB while the
range contains the number of SRGB elements. The range value MUST be range contains the number of SRGB elements. The range value MUST be
higher than 0. higher than 0.
The SR-Capabilities sub-TLV MAY be advertised in an LSP of any number The SR-Capabilities sub-TLV MAY be advertised in an LSP of any number
but a router MUST NOT advertise more than one SR-Capabilities sub- but a router MUST NOT advertise more than one SR-Capabilities sub-
TLV. A router receiving multiple SR-Capabilities sub-TLVs, from the TLV. A router receiving multiple SR-Capabilities sub-TLVs from the
same originator, SHOULD select the first advertisement in the lowest same originator SHOULD select the first advertisement in the lowest
numbered LSP. numbered LSP.
When multiple SRGB Descriptors are advertised the entries define an When multiple SRGB Descriptors are advertised the entries define an
ordered set of ranges on which a SID index is to be applied. For ordered set of ranges on which a SID index is to be applied. For
this reason changing the order in which the descriptors are this reason changing the order in which the descriptors are
advertised will have a disruptive effect on forwarding. advertised will have a disruptive effect on forwarding.
When a router adds a new SRGB Descriptor to an existing SR- When a router adds a new SRGB Descriptor to an existing SR-
Capabilities sub-TLV the new Descriptor SHOULD add the newly Capabilities sub-TLV the new Descriptor SHOULD add the newly
configured block at the end of the sub-TLV and SHOULD NOT change the configured block at the end of the sub-TLV and SHOULD NOT change the
skipping to change at page 31, line 30 skipping to change at page 31, line 30
Email: sluong@cisco.com Email: sluong@cisco.com
9. References 9. References
9.1. Normative References 9.1. Normative References
[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-26 (work in progress), November 2018. routing-extensions-27 (work in progress), December 2018.
[I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing
Architecture", draft-ietf-spring-segment-routing-15 (work
in progress), January 2018.
[I-D.ietf-spring-segment-routing-ldp-interop] [I-D.ietf-spring-segment-routing-ldp-interop]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., and Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., and
S. Litkowski, "Segment Routing interworking with LDP", S. Litkowski, "Segment Routing interworking with LDP",
draft-ietf-spring-segment-routing-ldp-interop-15 (work in draft-ietf-spring-segment-routing-ldp-interop-15 (work in
progress), September 2018. progress), September 2018.
[I-D.ietf-spring-segment-routing-mpls] [I-D.ietf-spring-segment-routing-mpls]
Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., Bashandy, A., Filsfils, C., Previdi, S., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing with MPLS Litkowski, S., and R. Shakir, "Segment Routing with MPLS
data plane", draft-ietf-spring-segment-routing-mpls-16 data plane", draft-ietf-spring-segment-routing-mpls-18
(work in progress), November 2018. (work in progress), December 2018.
[ISO10589] [ISO10589]
International Organization for Standardization, International Organization for Standardization,
"Intermediate system to Intermediate system intra-domain "Intermediate system to Intermediate system intra-domain
routeing information exchange protocol for use in routeing information exchange protocol for use in
conjunction with the protocol for providing the conjunction with the protocol for providing the
connectionless-mode Network Service (ISO 8473)", ISO/ connectionless-mode Network Service (ISO 8473)", ISO/
IEC 10589:2002, Second Edition, Nov 2002. IEC 10589:2002, Second Edition, Nov 2002.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 33, line 14 skipping to change at page 33, line 5
[RFC7981] Ginsberg, L., Previdi, S., and M. Chen, "IS-IS Extensions [RFC7981] Ginsberg, L., Previdi, S., and M. Chen, "IS-IS Extensions
for Advertising Router Information", RFC 7981, for Advertising Router Information", RFC 7981,
DOI 10.17487/RFC7981, October 2016, DOI 10.17487/RFC7981, October 2016,
<https://www.rfc-editor.org/info/rfc7981>. <https://www.rfc-editor.org/info/rfc7981>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>.
9.2. Informative References 9.2. Informative References
[RFC5311] McPherson, D., Ed., Ginsberg, L., Previdi, S., and M. [RFC5311] McPherson, D., Ed., Ginsberg, L., Previdi, S., and M.
Shand, "Simplified Extension of Link State PDU (LSP) Space Shand, "Simplified Extension of Link State PDU (LSP) Space
for IS-IS", RFC 5311, DOI 10.17487/RFC5311, February 2009, for IS-IS", RFC 5311, DOI 10.17487/RFC5311, February 2009,
<https://www.rfc-editor.org/info/rfc5311>. <https://www.rfc-editor.org/info/rfc5311>.
[RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in
Support of Inter-Autonomous System (AS) MPLS and GMPLS Support of Inter-Autonomous System (AS) MPLS and GMPLS
Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316,
 End of changes. 21 change blocks. 
46 lines changed or deleted 41 lines changed or added

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