< draft-ietf-ospf-segment-routing-extensions-02.txt		draft-ietf-ospf-segment-routing-extensions-03.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: February 16, 2015 Cisco Systems, Inc.		Expires: June 5, 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
	August 15, 2014		December 2, 2014
	OSPF Extensions for Segment Routing		OSPF Extensions for Segment Routing
	draft-ietf-ospf-segment-routing-extensions-02		draft-ietf-ospf-segment-routing-extensions-03
	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 February 16, 2015.		This Internet-Draft will expire on June 5, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 30 ¶		skipping to change at page 2, line 30 ¶
	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 . . . . . . . . . . . . . . . . . . . . . 8		5. Prefix SID Sub-TLV . . . . . . . . . . . . . . . . . . . . . 9
	6. SID/Label Binding Sub-TLV . . . . . . . . . . . . . . . . . . 12		6. SID/Label Binding Sub-TLV . . . . . . . . . . . . . . . . . . 12
	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 . . . . . . . . . . . . . . . . . . . . . . 14
	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 . . . . . . . . . 15		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 . . . . . 17		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 . . . . . . . . . . . . . . . . . . . 20
	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 . . . . . . . . . . 22		8.2. Inter-area Segment routing in OSPFv2 . . . . . . . . . . 22
	8.3. SID for External Prefixes . . . . . . . . . . . . . . . . 23		8.3. SID for External Prefixes . . . . . . . . . . . . . . . . 23
	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 . . . . 24		8.4.2. Adjacency SID on Broadcast or NBMA Interfaces . . . . 24
	skipping to change at page 8, line 12 ¶		skipping to change at page 8, line 12 ¶
	single OSPF Extended Prefix Opaque LSA MUST have the same flooding		single OSPF Extended Prefix Opaque LSA MUST have the same flooding
	scope. The OSPF Extended Prefix Range TLV has the following format:		scope. The OSPF Extended Prefix Range 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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Prefix Length | AF | Range Size |		| Prefix Length | AF | Range Size |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Flags | Reserved |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Address Prefix (variable) |		| Address Prefix (variable) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sub-TLVs (variable) |		| Sub-TLVs (variable) |
	+- -+		+- -+
	| |		| |
	where:		where:
	Type: TBD, suggested value 2.		Type: TBD, suggested value 2.
	skipping to change at page 8, line 33 ¶		skipping to change at page 8, line 35 ¶
	Prefix length: length of the prefix		Prefix length: length of the prefix
	AF: 0 - IPv4 unicast		AF: 0 - IPv4 unicast
	Range size: represents the number of prefixes that are covered by		Range size: represents the number of prefixes that are covered by
	the advertisement. The Range Size MUST NOT exceed the number of		the advertisement. The Range Size MUST NOT exceed the number of
	prefixes that could be satisfied by the prefix length without		prefixes that could be satisfied by the prefix length without
	including the IPv4 multicast address range (224.0.0.0/3).		including the IPv4 multicast address range (224.0.0.0/3).
			Flags: 1 octet field. The following flags are defined:
			0 1 2 3 4 5 6 7
			+--+--+--+--+--+--+--+--+
			|IA| | | | | | | |
			+--+--+--+--+--+--+--+--+
			where:
			IA-Flag: Inter-Area flag. If set, advertisement is of inter-
			area type. ABR that is advertising the OSPF Extended Prefix
			Range TLV between areas MUST set this bit.
			This bit is used to prevent redundant flooding of Prefix Range
			TLVs between areas as follows:
			An ABR always prefers intra-area Prefix Range advertisement
			over inter-area one.
			An ABR does not consider inter-area Prefix Range
			advertisements coming from non backbone area.
			An ABR propagates inter-area Prefix Range advertisement from
			backbone area to connected non backbone areas only if such
			advertisement is considered to be the best one.
	Address Prefix: the prefix, encoded as an even multiple of 32-bit		Address Prefix: the prefix, encoded as an even multiple of 32-bit
	words, padded with zeroed bits as necessary. This encoding		words, padded with zeroed bits as necessary. This encoding
	consumes ((PrefixLength + 31) / 32) 32-bit words. The Address		consumes ((PrefixLength + 31) / 32) 32-bit words. The Address
	Prefix represents the first prefix in the prefix range.		Prefix represents the first prefix in the prefix range.
	5. Prefix SID Sub-TLV		5. Prefix SID Sub-TLV
	The Prefix SID Sub-TLV is a Sub-TLV of the OSPF Extended Prefix TLV		The Prefix SID Sub-TLV is a Sub-TLV of the OSPF Extended Prefix TLV
	described in [I-D.ietf-ospf-prefix-link-attr] and the OSPF Extended		described in [I-D.ietf-ospf-prefix-link-attr] and the OSPF Extended
	Prefix Range TLV described in Section 4. It MAY appear more than		Prefix Range TLV described in Section 4. It MAY appear more than
	skipping to change at page 27, line 33 ¶		skipping to change at page 27, line 33 ¶
	2013.		2013.
	[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-00 (work		Advertisement", draft-ietf-ospf-prefix-link-attr-01 (work
	in progress), August 2014.		in progress), September 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
	egress fast-protection", draft-minto-rsvp-lsp-egress-fast-		egress fast-protection", draft-minto-rsvp-lsp-egress-fast-
	protection-03 (work in progress), November 2013.		protection-03 (work in progress), November 2013.
	Authors' Addresses		Authors' Addresses
	Peter Psenak (editor)		Peter Psenak (editor)
	Cisco Systems, Inc.		Cisco Systems, Inc.
End of changes. 10 change blocks.
	9 lines changed or deleted		37 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/