< draft-ietf-ospf-segment-routing-extensions-04.txt		draft-ietf-ospf-segment-routing-extensions-05.txt >
	Open Shortest Path First IGP P. Psenak, Ed.		Open Shortest Path First IGP P. Psenak, Ed.
	Internet-Draft S. Previdi, Ed.		Internet-Draft S. Previdi, Ed.
	Intended status: Standards Track C. Filsfils		Intended status: Standards Track C. Filsfils
	Expires: August 5, 2015 Cisco Systems, Inc.		Expires: December 28, 2015 Cisco Systems, Inc.
	H. Gredler		H. Gredler
	Juniper Networks, Inc.		Juniper Networks, Inc.
	R. Shakir		R. Shakir
	British Telecom		British Telecom
	W. Henderickx		W. Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	J. Tantsura		J. Tantsura
	Ericsson		Ericsson
	February 1, 2015		June 26, 2015
	OSPF Extensions for Segment Routing		OSPF Extensions for Segment Routing
	draft-ietf-ospf-segment-routing-extensions-04		draft-ietf-ospf-segment-routing-extensions-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 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 OSPF extensions required for Segment		This draft describes the OSPF extensions required for Segment
	Routing.		Routing.
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 August 5, 2015.		This Internet-Draft will expire on December 28, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 31 ¶		skipping to change at page 2, line 31 ¶
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Segment Routing Identifiers . . . . . . . . . . . . . . . . . 3		2. Segment Routing Identifiers . . . . . . . . . . . . . . . . . 3
	2.1. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . . . 4		2.1. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . . . 4
	3. Segment Routing Capabilities . . . . . . . . . . . . . . . . 4		3. Segment Routing Capabilities . . . . . . . . . . . . . . . . 4
	3.1. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . . . 4		3.1. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . . . 4
	3.2. SID/Label Range TLV . . . . . . . . . . . . . . . . . . . 5		3.2. SID/Label Range TLV . . . . . . . . . . . . . . . . . . . 5
	4. OSPF Extended Prefix Range TLV . . . . . . . . . . . . . . . 7		4. OSPF Extended Prefix Range TLV . . . . . . . . . . . . . . . 7
	5. Prefix SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 9		5. Prefix SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 9
	6. SID/Label Binding Sub-TLV . . . . . . . . . . . . . . . . . . 12		6. SID/Label Binding Sub-TLV . . . . . . . . . . . . . . . . . . 13
	6.1. ERO Metric Sub-TLV . . . . . . . . . . . . . . . . . . . 14		6.1. ERO Metric Sub-TLV . . . . . . . . . . . . . . . . . . . 14
	6.2. ERO Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . 14		6.2. ERO Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . 15
	6.2.1. IPv4 ERO Sub-TLV . . . . . . . . . . . . . . . . . . 15		6.2.1. IPv4 ERO Sub-TLV . . . . . . . . . . . . . . . . . . 15
	6.2.2. Unnumbered Interface ID ERO Sub-TLV . . . . . . . . . 16		6.2.2. Unnumbered Interface ID ERO Sub-TLV . . . . . . . . . 16
	6.2.3. IPv4 Backup ERO Sub-TLV . . . . . . . . . . . . . . . 17		6.2.3. IPv4 Backup ERO Sub-TLV . . . . . . . . . . . . . . . 17
	6.2.4. Unnumbered Interface ID Backup ERO Sub-TLV . . . . . 18		6.2.4. Unnumbered Interface ID Backup ERO Sub-TLV . . . . . 18
	7. Adjacency Segment Identifier (Adj-SID) . . . . . . . . . . . 19		7. Adjacency Segment Identifier (Adj-SID) . . . . . . . . . . . 19
	7.1. Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 19		7.1. Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 19
	7.2. LAN Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . 20		7.2. LAN Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . 21
	8. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 22		8. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 22
	8.1. Intra-area Segment routing in OSPFv2 . . . . . . . . . . 22		8.1. Intra-area Segment routing in OSPFv2 . . . . . . . . . . 22
	8.2. Inter-area Segment routing in OSPFv2 . . . . . . . . . . 23		8.2. Inter-area Segment routing in OSPFv2 . . . . . . . . . . 23
	8.3. SID for External Prefixes . . . . . . . . . . . . . . . . 24		8.3. SID for External Prefixes . . . . . . . . . . . . . . . . 24
	8.4. Advertisement of Adj-SID . . . . . . . . . . . . . . . . 24		8.4. Advertisement of Adj-SID . . . . . . . . . . . . . . . . 24
	8.4.1. Advertisement of Adj-SID on Point-to-Point Links . . 24		8.4.1. Advertisement of Adj-SID on Point-to-Point Links . . 24
	8.4.2. Adjacency SID on Broadcast or NBMA Interfaces . . . . 25		8.4.2. Adjacency SID on Broadcast or NBMA Interfaces . . . . 25
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
	9.1. OSPF OSPF Router Information (RI) TLVs Registry . . . . . 25		9.1. OSPF OSPF Router Information (RI) TLVs Registry . . . . . 25
	9.2. OSPF Extended Prefix LSA TLV Registry . . . . . . . . . . 25		9.2. OSPF Extended Prefix LSA TLV Registry . . . . . . . . . . 25
	9.3. OSPF Extended Prefix LSA Sub-TLV Registry . . . . . . . . 25		9.3. OSPF Extended Prefix LSA Sub-TLV Registry . . . . . . . . 25
	9.4. OSPF Extended Link LSA Sub-TLV Registry . . . . . . . . . 26		9.4. OSPF Extended Link LSA Sub-TLV Registry . . . . . . . . . 26
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 26		10. Security Considerations . . . . . . . . . . . . . . . . . . . 26
	11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 26		11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 26
	12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26		12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 26
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 26		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 26
	13.1. Normative References . . . . . . . . . . . . . . . . . . 26		13.1. Normative References . . . . . . . . . . . . . . . . . . 27
	13.2. Informative References . . . . . . . . . . . . . . . . . 27		13.2. Informative References . . . . . . . . . . . . . . . . . 27
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28
	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 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).
	Prefix segments represent an ecmp-aware shortest-path to a prefix (or		Prefix segments represent an ecmp-aware shortest-path to a prefix (or
	skipping to change at page 5, line 27 ¶		skipping to change at page 5, line 27 ¶
	| |		| |
	+ +		+ +
	where:		where:
	Type: TBD, suggested value 8		Type: TBD, suggested value 8
	Length: variable		Length: variable
	Algorithm: Single octet identifying the algorithm. The following		Algorithm: Single octet identifying the algorithm. The following
	value is defined by this document:		values are defined by this document:
	0: IGP metric based Shortest Path Tree (SPT)		0: Shortest Path First (SPF) algorithm based on link metric.
			This is the standard shortest path algorithm as computed by the
			OSPF protocol. Consistent with the deployed practice for link-
			state protocols, Algorithm 0 permits any node to overwrite the
			SPF path with a different path based on its local policy.
			1: Strict Shortest Path First (SPF) algorithm based on link
			metric. The algorithm is identical to Algorithm 0 but
			Algorithm 1 requires that all nodes along the path will honor
			the SPF routing decision. Local policy at the node claiming
			the support of Algorithm 1 MUST NOT alter the forwarding
			decision computed by Algorithm 1.
	The RI LSA can be advertised at any of the defined opaque flooding		The RI LSA can be advertised at any of the defined opaque flooding
	scopes (link, area, or Autonomous System (AS)). For the purpose of		scopes (link, area, or Autonomous System (AS)). For the purpose of
	the SR-Algorithm TLV propagation, area scope flooding is required.		the SR-Algorithm TLV propagation, area scope flooding is required.
	3.2. SID/Label Range TLV		3.2. SID/Label Range TLV
	The SID/Label Range TLV is a top-level TLV of the Router Information		The SID/Label Range TLV is a top-level TLV of the Router Information
	Opaque LSA (defined in [RFC4970]).		Opaque LSA (defined in [RFC4970]).
	skipping to change at page 11, line 48 ¶		skipping to change at page 11, line 48 ¶
	If the E-flag is set then any upstream neighbor of the Prefix-SID		If the E-flag is set then any upstream neighbor of the Prefix-SID
	originator MUST replace the Prefix-SID with a Prefix-SID having an		originator MUST replace the Prefix-SID with a Prefix-SID having an
	Explicit-NULL value. This is useful, e.g., when the originator of		Explicit-NULL value. This is useful, e.g., when the originator of
	the Prefix-SID is the final destination for the related prefix and		the Prefix-SID is the final destination for the related prefix and
	the originator wishes to receive the packet with the original EXP		the originator wishes to receive the packet with the original EXP
	bits.		bits.
	When M-Flag is set, NP-flag MUST be set and E-bit MUST NOT be set.		When M-Flag is set, NP-flag MUST be set and E-bit MUST NOT be set.
			As the Mapping Server does not specify the originator of a prefix
			advertisement it is not possible to determine PHP behavior solely
			based on the Mapping Server advertisement. However, PHP behavior may
			safely be done in following cases:
			Prefix is of intra-area type and the downstream neighbor is the
			originator of the prefix.
			Prefix is of inter-area type and downstream neighbor is an ABR,
			which is advertising the prefix reachability and is also
			generating the Extended Prefix TLV with A-flag set for this prefix
			as described in section 2.1 of [I-D.ietf-ospf-prefix-link-attr].
			Prefix is of external type and downstream neighbor is an ASBR,
			which is advertising the prefix reachability and is also
			generating the Extended Prefix TLV with A-flag set for this prefix
			as described in section 2.1 of [I-D.ietf-ospf-prefix-link-attr].
	When a Prefix-SID is advertised in an Extended Prefix Range TLV, then		When a Prefix-SID is advertised in an Extended Prefix Range TLV, then
	the value advertised in Prefix SID Sub-TLV is interpreted as a		the value advertised in Prefix SID Sub-TLV is interpreted as a
	starting SID value.		starting SID value.
	Example 1: if the following router addresses (loopback addresses)		Example 1: if the following router addresses (loopback addresses)
	need to be mapped into the corresponding Prefix SID indexes:		need to be mapped into the corresponding Prefix SID indexes:
	Router-A: 192.0.2.1/32, Prefix-SID: Index 1		Router-A: 192.0.2.1/32, Prefix-SID: Index 1
	Router-B: 192.0.2.2/32, Prefix-SID: Index 2		Router-B: 192.0.2.2/32, Prefix-SID: Index 2
	Router-C: 192.0.2.3/32, Prefix-SID: Index 3		Router-C: 192.0.2.3/32, Prefix-SID: Index 3
	skipping to change at page 19, line 50 ¶		skipping to change at page 20, line 15 ¶
	Flags. 1 octet field of following flags:		Flags. 1 octet field of following flags:
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	|B|V|L|S| |		|B|V|L|S| |
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	where:		where:
	B-Flag: Backup Flag. If set, the Adj-SID refers to an		B-Flag: Backup Flag. If set, the Adj-SID refers to an
	adjacency being protected (e.g.: using IPFRR or MPLS-FRR) as		adjacency that is eligible for protection (e.g.: using IPFRR or
	described in section 3.1 of		MPLS-FRR) as described in section 3.5 of
	[I-D.filsfils-spring-segment-routing-use-cases].		[I-D.ietf-spring-segment-routing].
	The V-Flag: Value/Index Flag. If set, then the Adj-SID carries		The V-Flag: Value/Index Flag. If set, then the Adj-SID carries
	an absolute value. If not set, then the Adj-SID carries an		an absolute value. If not set, then the Adj-SID carries an
	index.		index.
	The L-Flag: Local/Global Flag. If set, then the value/index		The L-Flag: Local/Global Flag. If set, then the value/index
	carried by the Adj-SID has local significance. If not set,		carried by the Adj-SID has local significance. If not set,
	then the value/index carried by this Sub-TLV has global		then the value/index carried by this Sub-TLV has global
	significance.		significance.
	skipping to change at page 20, line 36 ¶		skipping to change at page 20, line 50 ¶
	SID/Index/Label: according to the V and L flags, it contains		SID/Index/Label: according to the V and L flags, it contains
	either:		either:
	A 32 bit index defining the offset in the SID/Label space		A 32 bit index defining the offset in the SID/Label space
	advertised by this router.		advertised by this router.
	A 24 bit label where the 20 rightmost bits are used for		A 24 bit label where the 20 rightmost bits are used for
	encoding the label value.		encoding the label value.
	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 set the B-Flag when the adjacency is protected by an		adjacencies and set the B-Flag when the adjacency is eligible for
	FRR mechanism (IP or MPLS) as described in section 3.1 of		protection by an FRR mechanism (IP or MPLS) as described in section
	[I-D.filsfils-spring-segment-routing-use-cases].		3.5 of [I-D.ietf-spring-segment-routing].
	7.2. LAN Adj-SID Sub-TLV		7.2. LAN Adj-SID Sub-TLV
	LAN Adj-SID is an optional Sub-TLV of the Extended Link TLV defined		LAN Adj-SID is an optional Sub-TLV of the Extended Link TLV defined
	in [I-D.ietf-ospf-prefix-link-attr]. It MAY appear multiple times in		in [I-D.ietf-ospf-prefix-link-attr]. It MAY appear multiple times in
	the Extended-Link TLV. It is used to advertise a SID/Label for an		the Extended-Link TLV. It is used to advertise a SID/Label for an
	adjacency to a non-DR node on a broadcast or NBMA network.		adjacency to a non-DR node on a broadcast or NBMA network.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	skipping to change at page 21, line 33 ¶		skipping to change at page 21, line 40 ¶
	Flags. 1 octet field of following flags:		Flags. 1 octet field of following flags:
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	|B|V|L|S| |		|B|V|L|S| |
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	where:		where:
	B-Flag: Backup-flag: set if the LAN-Adj-SID refer to an		B-Flag: Backup-flag: set if the LAN-Adj-SID refer to an
	adjacency being protected (e.g.: using IPFRR or MPLS-FRR) as		adjacency that is eligible for protection (e.g.: using IPFRR or
	described in section 3.1 of		MPLS-FRR) as described in section 3.5 of
	[I-D.filsfils-spring-segment-routing-use-cases].		[I-D.ietf-spring-segment-routing].
	The V-Flag: Value/Index Flag. If set, then the Prefix-SID		The V-Flag: Value/Index Flag. If set, then the Prefix-SID
	carries an absolute value. If not set, then the Prefix-SID		carries an absolute value. If not set, then the Prefix-SID
	carries an index.		carries an index.
	The L-Flag: Local/Global Flag. If set, then the value/index		The L-Flag: Local/Global Flag. If set, then the value/index
	carried by the Prefix-SID has local significance. If not set,		carried by the Prefix-SID has local significance. If not set,
	then the value/index carried by this Sub-TLV has global		then the value/index carried by this Sub-TLV has global
	significance.		significance.
	skipping to change at page 24, line 16 ¶		skipping to change at page 24, line 19 ¶
	area and find the advertising router associated with the best path		area and find the advertising router associated with the best path
	to that prefix.		to that prefix.
	The ABR will then determine if such router advertised a Prefix-SID		The ABR will then determine if such router advertised a Prefix-SID
	for the prefix and use it when advertising the Prefix-SID to other		for the prefix and use it when advertising the Prefix-SID to other
	connected areas.		connected areas.
	If no Prefix-SID was advertised for the prefix in the source area		If no Prefix-SID was advertised for the prefix in the source area
	by the ABR that contributes to the best path to the prefix, the		by the ABR that contributes to the best path to the prefix, the
	originating ABR will use the Prefix-SID advertised by any other		originating ABR will use the Prefix-SID advertised by any other
	router (e.g.: a Prefix-SID coming from an SR Mapping Server as		router when propagating the Prefix-SID for the prefix to other
	defined in [I-D.filsfils-spring-segment-routing-ldp-interop]) when		areas.
	propagating the Prefix-SID for the prefix to other areas.
	8.3. SID for External Prefixes		8.3. SID for External Prefixes
	Type-5 LSAs are flooded domain wide. When an ASBR, which supports		Type-5 LSAs are flooded domain wide. When an ASBR, which supports
	SR, generates Type-5 LSAs, it should also originate an Extended		SR, generates Type-5 LSAs, it should also originate an Extended
	Prefix Opaque LSAs, as described in [I-D.ietf-ospf-prefix-link-attr].		Prefix Opaque LSAs, as described in [I-D.ietf-ospf-prefix-link-attr].
	The flooding scope of the Extended Prefix Opaque LSA type is set to		The flooding scope of the Extended Prefix Opaque LSA type is set to
	AS-scope. The route-type in the OSPF Extended Prefix TLV is set to		AS-scope. The route-type in the OSPF Extended Prefix TLV is set to
	external. The Prefix-SID Sub-TLV is included in this LSA and the		external. The Prefix-SID Sub-TLV is included in this LSA and the
	Prefix-SID value will be set to the SID that has been reserved for		Prefix-SID value will be set to the SID that has been reserved for
	that prefix.		that prefix.
	When an NSSA ABR translates Type-7 LSAs into Type-5 LSAs, it should		When an NSSA ABR translates Type-7 LSAs into Type-5 LSAs, it should
	also advertise the Prefix-SID for the prefix. The NSSA ABR		also advertise the Prefix-SID for the prefix. The NSSA ABR
	determines its best path to the prefix advertised in the translated		determines its best path to the prefix advertised in the translated
	Type-7 LSA and finds the advertising router associated with that		Type-7 LSA and finds the advertising router associated with that
	path. If the advertising router has advertised a Prefix-SID for the		path. If the advertising router has advertised a Prefix-SID for the
	prefix, then the NSSA ABR uses it when advertising the Prefix-SID for		prefix, then the NSSA ABR uses it when advertising the Prefix-SID for
	the Type-5 prefix. Otherwise, the Prefix-SID advertised by any other		the Type-5 prefix. Otherwise, the Prefix-SID advertised by any other
	router will be used (e.g.: a Prefix-SID coming from an SR Mapping		router will be used.
	Server as defined in
	[I-D.filsfils-spring-segment-routing-ldp-interop]).
	8.4. Advertisement of Adj-SID		8.4. Advertisement of Adj-SID
	The Adjacency Segment Routing Identifier (Adj-SID) is advertised		The Adjacency Segment Routing Identifier (Adj-SID) is advertised
	using the Adj-SID Sub-TLV as described in Section 7.		using the Adj-SID Sub-TLV as described in Section 7.
	8.4.1. Advertisement of Adj-SID on Point-to-Point Links		8.4.1. Advertisement of Adj-SID on Point-to-Point Links
	An Adj-SID MAY be advertised for any adjacency on a p2p link that is		An Adj-SID MAY be advertised for any adjacency on a p2p link that is
	in neighbor state 2-Way or higher. If the adjacency on a p2p link		in neighbor state 2-Way or higher. If the adjacency on a p2p link
	skipping to change at page 28, line 8 ¶		skipping to change at page 28, line 13 ¶
	October 2014.		October 2014.
	[I-D.gredler-ospf-label-advertisement]		[I-D.gredler-ospf-label-advertisement]
	Gredler, H., Amante, S., Scholl, T., and L. Jalil,		Gredler, H., Amante, S., Scholl, T., and L. Jalil,
	"Advertising MPLS labels in OSPF", draft-gredler-ospf-		"Advertising MPLS labels in OSPF", draft-gredler-ospf-
	label-advertisement-03 (work in progress), May 2013.		label-advertisement-03 (work in progress), May 2013.
	[I-D.ietf-ospf-prefix-link-attr]		[I-D.ietf-ospf-prefix-link-attr]
	Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,		Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
	Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute		Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
	Advertisement", draft-ietf-ospf-prefix-link-attr-02 (work		Advertisement", draft-ietf-ospf-prefix-link-attr-06 (work
	in progress), December 2014.		in progress), June 2015.
	[I-D.ietf-spring-segment-routing]		[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,		Filsfils, C., Previdi, S., Bashandy, A., Decraene, B.,
	Litkowski, S., Horneffer, M., Shakir, R., Tantsura, J.,		Litkowski, S., Horneffer, M., Shakir, R., Tantsura, J.,
	and E. Crabbe, "Segment Routing Architecture", draft-ietf-		and E. Crabbe, "Segment Routing Architecture", draft-ietf-
	spring-segment-routing-00 (work in progress), December		spring-segment-routing-00 (work in progress), December
	2014.		2014.
	[I-D.minto-rsvp-lsp-egress-fast-protection]		[I-D.minto-rsvp-lsp-egress-fast-protection]
	Jeganathan, J., Gredler, H., and Y. Shen, "RSVP-TE LSP		Jeganathan, J., Gredler, H., and Y. Shen, "RSVP-TE LSP
End of changes. 17 change blocks.
	27 lines changed or deleted		53 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/