< draft-ietf-ospf-segment-routing-extensions-11.txt		draft-ietf-ospf-segment-routing-extensions-12.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: September 1, 2017 Cisco Systems, Inc.		Expires: September 9, 2017 Cisco Systems, Inc.
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	R. Shakir		R. Shakir
	Google, Inc.		Google, Inc.
	W. Henderickx		W. Henderickx
	Nokia		Nokia
	J. Tantsura		J. Tantsura
	Individual		Individual
	February 28, 2017		March 8, 2017
	OSPF Extensions for Segment Routing		OSPF Extensions for Segment Routing
	draft-ietf-ospf-segment-routing-extensions-11		draft-ietf-ospf-segment-routing-extensions-12
	Abstract		Abstract
	Segment Routing (SR) allows a flexible definition of end-to-end paths		Segment Routing (SR) allows a flexible definition of end-to-end paths
	within IGP topologies by encoding paths as sequences of topological		within IGP topologies by encoding paths as sequences of topological
	sub-paths, called "segments". These segments are advertised by the		sub-paths, called "segments". These segments are advertised by the
	link-state routing protocols (IS-IS and OSPF).		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 September 1, 2017.		This Internet-Draft will expire on September 9, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 34 ¶		skipping to change at page 2, line 34 ¶
	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 . . . . . . . . . . . . . . . . . . . 6		3.2. SID/Label Range TLV . . . . . . . . . . . . . . . . . . . 6
	3.3. SR Local Block Sub-TLV . . . . . . . . . . . . . . . . . 8		3.3. SR Local Block Sub-TLV . . . . . . . . . . . . . . . . . 8
	3.4. SRMS Preference Sub-TLV . . . . . . . . . . . . . . . . . 9		3.4. SRMS Preference Sub-TLV . . . . . . . . . . . . . . . . . 9
	4. OSPF Extended Prefix Range TLV . . . . . . . . . . . . . . . 10		4. OSPF Extended Prefix Range TLV . . . . . . . . . . . . . . . 10
	5. Prefix SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 12		5. Prefix SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 12
	6. SID/Label Binding Sub-TLV . . . . . . . . . . . . . . . . . . 16		6. SID/Label Binding Sub-TLV . . . . . . . . . . . . . . . . . . 16
	6.1. ERO Metric Sub-TLV . . . . . . . . . . . . . . . . . . . 18		6.1. ERO Metric Sub-TLV . . . . . . . . . . . . . . . . . . . 17
	6.2. ERO Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . 18		6.2. ERO Sub-TLVs . . . . . . . . . . . . . . . . . . . . . . 18
	6.2.1. IPv4 ERO Sub-TLV . . . . . . . . . . . . . . . . . . 19		6.2.1. IPv4 ERO Sub-TLV . . . . . . . . . . . . . . . . . . 18
	6.2.2. Unnumbered Interface ID ERO Sub-TLV . . . . . . . . . 19		6.2.2. Unnumbered Interface ID ERO Sub-TLV . . . . . . . . . 19
	6.2.3. IPv4 Backup ERO Sub-TLV . . . . . . . . . . . . . . . 21		6.2.3. IPv4 Backup ERO Sub-TLV . . . . . . . . . . . . . . . 20
	6.2.4. Unnumbered Interface ID Backup ERO Sub-TLV . . . . . 21		6.2.4. Unnumbered Interface ID Backup ERO Sub-TLV . . . . . 21
	7. Adjacency Segment Identifier (Adj-SID) . . . . . . . . . . . 23		7. Adjacency Segment Identifier (Adj-SID) . . . . . . . . . . . 22
	7.1. Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 23		7.1. Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 23
	7.2. LAN Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . 25		7.2. LAN Adj-SID Sub-TLV . . . . . . . . . . . . . . . . . . . 24
	8. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 26		8. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 26
	8.1. Intra-area Segment routing in OSPFv2 . . . . . . . . . . 26		8.1. Intra-area Segment routing in OSPFv2 . . . . . . . . . . 26
	8.2. Inter-area Segment routing in OSPFv2 . . . . . . . . . . 27		8.2. Inter-area Segment routing in OSPFv2 . . . . . . . . . . 27
	8.3. SID for External Prefixes . . . . . . . . . . . . . . . . 28		8.3. SID for External Prefixes . . . . . . . . . . . . . . . . 28
	8.4. Advertisement of Adj-SID . . . . . . . . . . . . . . . . 29		8.4. Advertisement of Adj-SID . . . . . . . . . . . . . . . . 28
	8.4.1. Advertisement of Adj-SID on Point-to-Point Links . . 29		8.4.1. Advertisement of Adj-SID on Point-to-Point Links . . 28
	8.4.2. Adjacency SID on Broadcast or NBMA Interfaces . . . . 29		8.4.2. Adjacency SID on Broadcast or NBMA Interfaces . . . . 29
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
	9.1. OSPF OSPF Router Information (RI) TLVs Registry . . . . . 29		9.1. OSPF OSPF Router Information (RI) TLVs Registry . . . . . 29
	9.2. OSPF Extended Prefix LSA TLV Registry . . . . . . . . . . 30		9.2. OSPF Extended Prefix LSA TLV Registry . . . . . . . . . . 29
	9.3. OSPF Extended Prefix LSA Sub-TLV Registry . . . . . . . . 30		9.3. OSPF Extended Prefix LSA Sub-TLV Registry . . . . . . . . 29
	9.4. OSPF Extended Link LSA Sub-TLV Registry . . . . . . . . . 30		9.4. OSPF Extended Link LSA Sub-TLV Registry . . . . . . . . . 30
	10. Implementation Status . . . . . . . . . . . . . . . . . . . . 30		10. Implementation Status . . . . . . . . . . . . . . . . . . . . 30
	11. Security Considerations . . . . . . . . . . . . . . . . . . . 32		11. Security Considerations . . . . . . . . . . . . . . . . . . . 32
	12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 32		12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 32
	13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32		13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 32
	14. References . . . . . . . . . . . . . . . . . . . . . . . . . 32		14. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
	14.1. Normative References . . . . . . . . . . . . . . . . . . 32		14.1. Normative References . . . . . . . . . . . . . . . . . . 32
	14.2. Informative References . . . . . . . . . . . . . . . . . 33		14.2. Informative References . . . . . . . . . . . . . . . . . 33
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
	skipping to change at page 8, line 19 ¶		skipping to change at page 8, line 19 ¶
	Adjacency-SIDs, and may also be allocated by other components than		Adjacency-SIDs, and may also be allocated by other components than
	OSPF protocol. As an example, an application or a controller may		OSPF protocol. As an example, an application or a controller may
	instruct the router to allocate a specific local SID. Therefore, in		instruct the router to allocate a specific local SID. Therefore, in
	order for such applications or controllers to know what are the local		order for such applications or controllers to know what are the local
	SIDs available in the router, it is required that the router		SIDs available in the router, it is required that the router
	advertises its SRLB. The SRLB Sub-TLV is used for that purpose.		advertises its SRLB. The SRLB Sub-TLV is used for that purpose.
	The SR Local Block (SRLB) Sub-TLV is a top-level TLV of the Router		The SR Local Block (SRLB) Sub-TLV is a top-level TLV of the Router
	Information Opaque LSA (defined in [RFC7770]).		Information Opaque LSA (defined in [RFC7770]).
	The SR Local Block Sub-TLV MAY only be advertised once in the Router		The SR Local Block Sub-TLV MAY appear multiple times in the Router
	Information Opaque LSA and has the following format:		Information Opaque LSA and 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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Range Size | Reserved |		| Range Size | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sub-TLVs (variable) |		| Sub-TLVs (variable) |
	skipping to change at page 8, line 47 ¶		skipping to change at page 8, line 47 ¶
	Length: variable		Length: variable
	Range Size: 3 octets of the SID/label range. MUST be higher then		Range Size: 3 octets of the SID/label range. MUST be higher then
	0.		0.
	Initially, the only supported Sub-TLV is the SID/Label TLV as defined		Initially, the only supported Sub-TLV is the SID/Label TLV as defined
	in Section 2.1. The SID/Label advertised in the SID/Label TLV		in Section 2.1. The SID/Label advertised in the SID/Label TLV
	represents the first SID/Label in the advertised range.		represents the first SID/Label in the advertised range.
	When multiple SRLB sub-TLVs are received from a given router the		The originating router MUST NOT advertise overlapping ranges.
	receiver SHOULD use the first occurrence of the sub-TLV in the Router
	Information LSA. If the SRLB sub-TLV appears in multiple Router
	Information LSAs that have different flooding scopes, the SRLB sub-
	TLV in the Router Information LSA with the lowest flooding scope
	SHOULD be used. If the SRLB sub-TLV appears in multiple Router
	Information LSAs that have the same flooding scope, the SRLB sub-TLV
	in the Router Information LSA with the numerically smallest Instance
	ID SHOULD be used and subsequent instances of the SRLB sub-TLV SHOULD
	be ignored.
	Each time a SID from the SRLB is allocated, it SHOULD also be		Each time a SID from the SRLB is allocated, it SHOULD also be
	reported to all components (e.g.: controller or applications) in		reported to all components (e.g.: controller or applications) in
	order for these components to have an up-to-date view of the current		order for these components to have an up-to-date view of the current
	SRLB allocation. This is required to avoid collision between		SRLB allocation. This is required to avoid collision between
	allocation instructions.		allocation instructions.
	Within the context of OSPF, the reporting of local SIDs is done		Within the context of OSPF, the reporting of local SIDs is done
	through OSPF Sub-TLVs such as the Adjacency-SID (Section 7).		through OSPF Sub-TLVs such as the Adjacency-SID (Section 7).
	However, the reporting of allocated local SIDs may also be done		However, the reporting of allocated local SIDs may also be done
End of changes. 13 change blocks.
	24 lines changed or deleted		15 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/