< draft-ietf-ospf-prefix-link-attr-06.txt		draft-ietf-ospf-prefix-link-attr-07.txt >
	Network Working Group P. Psenak		Network Working Group P. Psenak
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track H. Gredler		Intended status: Standards Track H. Gredler
	Expires: December 9, 2015 Juniper Networks, Inc.		Expires: February 2, 2016 Juniper Networks, Inc.
	R. Shakir		R. Shakir
	British Telcom		Individual Contributor
	W. Henderickx		W. Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	J. Tantsura		J. Tantsura
	Ericsson		Ericsson
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	June 7, 2015		August 1, 2015
	OSPFv2 Prefix/Link Attribute Advertisement		OSPFv2 Prefix/Link Attribute Advertisement
	draft-ietf-ospf-prefix-link-attr-06.txt		draft-ietf-ospf-prefix-link-attr-07.txt
	Abstract		Abstract
	OSPFv2 requires functional extension beyond what can readily be done		OSPFv2 requires functional extension beyond what can readily be done
	with the fixed-format Link State Advertisements (LSAs) as described		with the fixed-format Link State Advertisements (LSAs) as described
	in RFC 2328. This document defines OSPF opaque LSAs based on Type-		in RFC 2328. This document defines OSPF opaque LSAs based on Type-
	Length-Value (TLV) tuples that can be used to associate additional		Length-Value (TLV) tuples that can be used to associate additional
	attributes with prefixes or links. Dependent on the application,		attributes with prefixes or links. Dependent on the application,
	these prefixes and links may or not be advertised in the fixed-format		these prefixes and links may or not be advertised in the fixed-format
	LSAs. The OSPF opaque LSAs are optional and fully backward		LSAs. The OSPF opaque LSAs are optional and fully backward
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 December 9, 2015.		This Internet-Draft will expire on February 2, 2016.
	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 38 ¶		skipping to change at page 2, line 38 ¶
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
	2. OSPFv2 Extended Prefix Opaque LSA . . . . . . . . . . . . . . 3		2. OSPFv2 Extended Prefix Opaque LSA . . . . . . . . . . . . . . 3
	2.1. OSPFv2 Extended Prefix TLV . . . . . . . . . . . . . . . 5		2.1. OSPFv2 Extended Prefix TLV . . . . . . . . . . . . . . . 5
	3. OSPFv2 Extended Link Opaque LSA . . . . . . . . . . . . . . . 7		3. OSPFv2 Extended Link Opaque LSA . . . . . . . . . . . . . . . 8
	3.1. OSPFv2 Extended Link TLV . . . . . . . . . . . . . . . . 8		3.1. OSPFv2 Extended Link TLV . . . . . . . . . . . . . . . . 9
	4. Backward Compatibility . . . . . . . . . . . . . . . . . . . 10		4. Backward Compatibility . . . . . . . . . . . . . . . . . . . 10
	5. Implementation Status . . . . . . . . . . . . . . . . . . . . 10		5. Implementation Status . . . . . . . . . . . . . . . . . . . . 10
	5.1. Implementation Survey Results . . . . . . . . . . . . . . 10		5.1. Implementation Survey Results . . . . . . . . . . . . . . 11
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 11		6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	7.1. OSPF Extended Prefix Opaque LSA TLV Registry . . . . . . 12		7.1. OSPF Extended Prefix Opaque LSA TLV Registry . . . . . . 12
	7.2. OSPF Extended Prefix TLV Sub-TLV Registry . . . . . . . . 12		7.2. OSPF Extended Prefix TLV Sub-TLV Registry . . . . . . . . 12
	7.3. OSPF Extended Link Opaque LSA TLV Registry . . . . . . . 12		7.3. OSPF Extended Link Opaque LSA TLV Registry . . . . . . . 13
	7.4. OSPF Extended Link TLV Sub-TLV Registry . . . . . . . . . 13		7.4. OSPF Extended Link TLV Sub-TLV Registry . . . . . . . . . 13
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13		8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
	9.1. Normative References . . . . . . . . . . . . . . . . . . 14		9.1. Normative References . . . . . . . . . . . . . . . . . . 14
	9.2. Informative References . . . . . . . . . . . . . . . . . 14		9.2. Informative References . . . . . . . . . . . . . . . . . 14
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
	1. Introduction		1. Introduction
	OSPFv2 requires functional extension beyond what can readily be done		OSPFv2 requires functional extension beyond what can readily be done
	with the fixed-format Link State Advertisements (LSAs) as described		with the fixed-format Link State Advertisements (LSAs) as described
	in RFC 2328 [OSPFV2]. This document defines OSPF opaque LSAs based		in RFC 2328 [OSPFV2]. This document defines OSPF opaque LSAs based
	on Type-Length-Value (TLV) tuples that can be used to associate		on Type-Length-Value (TLV) tuples that can be used to associate
	additional attributes with prefixes or links. Dependent on the		additional attributes with prefixes or links. Dependent on the
	application, these prefixes and links may or not be advertised in the		application, these prefixes and links may or not be advertised in the
	fixed-format LSAs. The OSPF opaque LSAs are optional and fully		fixed-format LSAs. The OSPF opaque LSAs are optional and fully
	skipping to change at page 4, line 9 ¶		skipping to change at page 4, line 9 ¶
	2. OSPFv2 Extended Prefix Opaque LSA		2. OSPFv2 Extended Prefix Opaque LSA
	The OSPFv2 Extended Prefix Opaque LSA will be used to advertise		The OSPFv2 Extended Prefix Opaque LSA will be used to advertise
	additional prefix attributes. Opaque LSAs are described in [OPAQUE].		additional prefix attributes. Opaque LSAs are described in [OPAQUE].
	Multiple OSPFv2 Extended Prefix Opaque LSAs can be advertised by an		Multiple OSPFv2 Extended Prefix Opaque LSAs can be advertised by an
	OSPFv2 router. The flooding scope of the OSPFv2 Extended Prefix		OSPFv2 router. The flooding scope of the OSPFv2 Extended Prefix
	Opaque LSA depends on the scope of the advertised prefixes and is		Opaque LSA depends on the scope of the advertised prefixes and is
	under the control of the advertising router. In some cases (e.g.,		under the control of the advertising router. In some cases (e.g.,
	mapping server deployment), the LSA flooding scope may be greater		mapping server deployment [SEGMENT-ROUTING]), the LSA flooding scope
	than the scope of the corresponding prefixes.		may be greater than the scope of the corresponding prefixes.
	The format of the OSPFv2 Extended Prefix Opaque LSA is as follows:		The format of the OSPFv2 Extended Prefix Opaque LSA is as follows:
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| LS age | Options | 9, 10, or 11 |		| LS age | Options | 9, 10, or 11 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Opaque type | Instance |		| Opaque type | Instance |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 4, line 33 ¶		skipping to change at page 4, line 33 ¶
	| LS sequence number |		| LS sequence number |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| LS checksum | length |		| LS checksum | length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	+- TLVs -+		+- TLVs -+
	| ... |		| ... |
	OSPFv2 Extended Prefix Opaque LSA		OSPFv2 Extended Prefix Opaque LSA
	The opaque type used by OSPFv2 Extended Prefix Opaque LSA is 7.		The opaque type used by OSPFv2 Extended Prefix Opaque LSA is 7. The
			opaque type is used to differential the various type of OSPFv2 Opaque
			LSA and is described in section 3 of [OPAQUE].
	The Instance field is an arbitrary value used to maintain multiple		The Instance field is an arbitrary value used to maintain multiple
	Extended Prefix Opaque LSAs. A maximum of 16777216 Extended Prefix		Extended Prefix Opaque LSAs. For OSPFv2 Extended Prefix Opaque LSAs,
	Opaque LSAs may be sourced by a single OSPF instance.		the Instance has no semantic significance other than to differentiate
			Extended Prefix Opaque LSAs originated by the same OSPFv2 router. If
			multiple Extended Prefix Opaque LSAs include the same prefix, the
			attributes from the Opaque LSA with the lowest Instance will be used.
	The format of the TLVs within the body of the OSPFv2 Extended Prefix		The format of the TLVs within the body of the OSPFv2 Extended Prefix
	Opaque LSA is the same as the format used by the Traffic Engineering		Opaque LSA is the same as the format used by the Traffic Engineering
	Extensions to OSPF [TE]. The variable TLV section consists of one or		Extensions to OSPF [TE]. The variable TLV section consists of one or
	more nested Type/Length/Value (TLV) tuples. Nested TLVs are also		more nested Type/Length/Value (TLV) tuples. Nested TLVs are also
	referred to as sub-TLVs. The format of each TLV is:		referred to as sub-TLVs. The format of each TLV is:
	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 6, line 6 ¶		skipping to change at page 6, line 6 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Address Prefix (variable) |		| Address Prefix (variable) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sub-TLVs (variable) |		| Sub-TLVs (variable) |
	+- -+		+- -+
	| |		| |
	OSPFv2 Extended Prefix TLV		OSPFv2 Extended Prefix TLV
	Type		Type
	The TLV type. Suggested value is 1.		The TLV type. The value is 1 for this TLV type.
	Length		Length
	Variable dependent on sub-TLVs.		Variable dependent on sub-TLVs.
	Route Type		Route Type
	Route type: type of the OSPF route. If the route type is 0		Route type: type of the OSPF route. If the route type is 0
	(Unspecified), the information inside the OSPF External Prefix TLV		(Unspecified), the information inside the OSPF External Prefix TLV
	applies to the prefix regardless of prefix's route-type. This is		applies to the prefix regardless of prefix's route-type. This is
	useful when prefix specific attributes are advertised by an		useful when prefix specific attributes are advertised by an
	external entity, which is not aware of the route-type associated		external entity that is not aware of the route-type associated
	with the prefix. Supported types are:		with the prefix. Supported types are:
	0 - Unspecified		0 - Unspecified
	1 - Intra-Area		1 - Intra-Area
	3 - Inter-Area		3 - Inter-Area
	5 - AS External		5 - AS External
	7 - NSSA External		7 - NSSA External
			These route types correspond directly to the OSPFv2 LSAs types as
			defined in http://www.iana.org/assignments/ospfv2-parameters/
			ospfv2-parameters.xhtml#ospfv2-parameters-5.
	Prefix Length		Prefix Length
	Length in of the prefix in bits.		Length in of the prefix in bits.
	AF		AF
	Address family for the prefix. Currently, the only supported		Address family for the prefix. Currently, the only supported
	value is 0 for IPv4 unicast.		value is 0 for IPv4 unicast. OSPFv3 [OSPFV3] is used for OSPF
			advertisement of IPv6 prefixes so this address family is not
			applicable. The inclusion of address family in this TLV allows
			for future extension.
	Flags: 1 octet field. The following flags are defined:		Flags: 1 octet field. The following flags are defined:
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+--+--+--+--+--+--+--+--+		+--+--+--+--+--+--+--+--+
	|A |N | | | | | | |		|A |N | | | | | | |
	+--+--+--+--+--+--+--+--+		+--+--+--+--+--+--+--+--+
	where:		where:
	A-Flag: Attach flag. An ABR generating Extended Prefix TLV for		A-Flag: Attach flag. An Area Border Router (ABR) generating an
	inter-area prefix that is locally connected or attached in		Extended Prefix TLV for inter-area prefix that is locally
	other connected area SHOULD set this flag.		connected or attached in other connected area SHOULD set this
			flag.
	N-Flag: Set when the prefix identifies the advertising router		N-Flag: Set when the prefix identifies the advertising router
	i.e., the prefix is a host prefix advertising a globally		i.e., the prefix is a host prefix advertising a globally
	reachable address typically associated with a loopback address.		reachable address typically associated with a loopback address.
	The advertising router MAY choose to NOT set this flag even		The advertising router MAY choose to NOT set this flag even
	when the above conditions are met. If the flag is set and the		when the above conditions are met. If the flag is set and the
	prefix length is NOT a host prefix then the flag MUST be		prefix length is NOT a host prefix then the flag MUST be
	ignored. The flag is preserved when OSPFv2 Extended Prefix		ignored. The flag is preserved when the OSPFv2 Extended Prefix
	Opaque LSA is propagated between areas.		Opaque LSA is propagated between areas.
	Address Prefix		Address Prefix
	The prefix itself encoded as an even multiple of 32-bit words,		The prefix itself encoded as an even multiple of 32-bit words,
	padded with zeroed bits as necessary. This encoding consumes		padded with zeroed bits as necessary. This encoding consumes
	((PrefixLength + 31) / 32) 32-bit words. The default route is		((PrefixLength + 31) / 32) 32-bit words. The default route is
	represented by a prefix of length 0.		represented by a prefix of length 0.
	If this TLV is advertised multiple times for the same prefix in the		If this TLV is advertised multiple times for the same prefix in the
	same OSPFv2 Extended Prefix Opaque LSA, only the first instance is		same OSPFv2 Extended Prefix Opaque LSA, only the first instance is
	skipping to change at page 8, line 26 ¶		skipping to change at page 8, line 35 ¶
	| LS sequence number |		| LS sequence number |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| LS checksum | length |		| LS checksum | length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	+- TLVs -+		+- TLVs -+
	| ... |		| ... |
	OSPFv2 Extended Link Opaque LSA		OSPFv2 Extended Link Opaque LSA
	The Opaque type used by OSPFv2 Extended Link Opaque LSA is 8.		The Opaque type used by OSPFv2 Extended Link Opaque LSA is 8. The
			opaque type is used to differential the various type of OSPFv2 Opaque
			LSA and is described in section 3 of [OPAQUE].
	The Instance field is an arbitrary value used to maintain multiple		The Instance field is an arbitrary value used to maintain multiple
	Extended Link Opaque LSAs. A maximum of 16777216 Extended Link		Extended Prefix Opaque LSAs. For OSPFv2 Extended Link Opaque LSAs,
	Opaque LSAs may be sourced by a single OSPF instance.		the Instance has no semantic significance other than to differentiate
			Extended Link Opaque LSAs originated by the same OSPFv2 router. If
			multiple Extended Link Opaque LSAs include the same link, the
			attributes from the Opaque LSA with the lowest Instance will be used.
	The format of the TLVs within the body of the OSPFv2 Extended Link		The format of the TLVs within the body of the OSPFv2 Extended Link
	Opaque LSA is the same as described in Section 2.		Opaque LSA is the same as described in Section 2.
	3.1. OSPFv2 Extended Link TLV		3.1. OSPFv2 Extended Link TLV
	The OSPFv2 Extended Link TLV is used to advertise various attributes		The OSPFv2 Extended Link TLV is used to advertise various attributes
	of the link. It describes a single link and is constructed of a set		of the link. It describes a single link and is constructed of a set
	of Sub-TLVs. There are no ordering requirements for the Sub-TLVs.		of Sub-TLVs. There are no ordering requirements for the Sub-TLVs.
	Only one Extended Link TLV SHALL be advertised in each Extended Link		Only one Extended Link TLV SHALL be advertised in each Extended Link
	skipping to change at page 9, line 23 ¶		skipping to change at page 9, line 33 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Link Data |		| Link Data |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sub-TLVs (variable) |		| Sub-TLVs (variable) |
	+- -+		+- -+
	| |		| |
	OSPFv2 Extended Link TLV		OSPFv2 Extended Link TLV
	Type		Type
	The TLV type. Suggested value is 1.		The TLV type. The value is 1 for this TLV type.
	Length		Length
	Variable dependent on sub-TLVs.		Variable dependent on sub-TLVs.
	Link-Type		Link-Type
	Link-Type is defined in section A.4.2 of [OSPFV2].		Link-Type is defined in section A.4.2 of [OSPFV2] and
			http://www.iana.org/assignments/ospfv2-parameters/
			ospfv2-parameters.xhtml#ospfv2-parameters-6.
	Link-ID		Link-ID
	Link-ID is defined in section A.4.2 of [OSPFV2].		Link-ID is defined in section A.4.2 of [OSPFV2].
	Link Data		Link Data
	Link-Data is defined in section A.4.2 of [OSPFV2].		Link-Data is defined in section A.4.2 of [OSPFV2].
	If this TLV is advertised multiple times in the same OSPFv2 Extended		If this TLV is advertised multiple times in the same OSPFv2 Extended
	Link Opaque LSA, only the first instance is used by receiving OSPFv2		Link Opaque LSA, only the first instance is used by receiving OSPFv2
	Routers. This situation SHOULD be logged as an error.		Routers. This situation SHOULD be logged as an error.
	skipping to change at page 10, line 11 ¶		skipping to change at page 10, line 25 ¶
	It is RECOMMENDED that OSPF routers advertising Extended Link TLVs in		It is RECOMMENDED that OSPF routers advertising Extended Link TLVs in
	different Extended Link Opaque LSAs re-originate these LSAs in		different Extended Link Opaque LSAs re-originate these LSAs in
	ascending order of Instance to minimize the disruption.		ascending order of Instance to minimize the disruption.
	This document creates a registry for OSPF Extended Link sub-TLVs in		This document creates a registry for OSPF Extended Link sub-TLVs in
	Section 7.		Section 7.
	4. Backward Compatibility		4. Backward Compatibility
	Since opaque OSPFv2 LSAs are optional and backward compatible		Since opaque OSPFv2 LSAs are optional and backward compatible
	[OPAQUE], the extensions described herein is fully backward		[OPAQUE], the extensions described herein are fully backward
	compatible. However, future OSPFv2 extensions utilizing these		compatible. However, future OSPFv2 extensions utilizing these
	extensions must address backward compatibility of the corresponding		extensions must address backward compatibility of the corresponding
	functionality.		functionality.
	5. Implementation Status		5. Implementation Status
			Note to RFC Editor: this section may be removed on publication as an
			RFC.
	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 RFC 6982.		Internet-Draft, and is based on a proposal described in RFC 6982.
	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
	here does not imply endorsement by the IETF. Furthermore, no effort		here does not imply endorsement by the IETF. Furthermore, no effort
	has been spent to verify the information presented here that was		has been spent to verify the information presented here that was
	supplied by IETF contributors. This is not intended as, and must not		supplied by IETF contributors. This is not intended as, and must not
	be construed to be, a catalog of available implementations or their		be construed to be, a catalog of available implementations or their
	skipping to change at page 14, line 30 ¶		skipping to change at page 14, line 45 ¶
	[BIER] Psenak, P., Kumar, N., Wijnands, I., Dolganow, A.,		[BIER] Psenak, P., Kumar, N., Wijnands, I., Dolganow, A.,
	Przygienda, T., Zhang, J., and S. Aldrin, "OSPF Extensions		Przygienda, T., Zhang, J., and S. Aldrin, "OSPF Extensions
	for BIER", draft-ietf-bier-ospf-bier-extensions-00.txt		for BIER", draft-ietf-bier-ospf-bier-extensions-00.txt
	(work in progress), April 2015.		(work in progress), April 2015.
	[I-D.ietf-ospf-ospfv3-lsa-extend]		[I-D.ietf-ospf-ospfv3-lsa-extend]
	Lindem, A., Mirtorabi, S., Roy, A., and F. Baker, "OSPFv3		Lindem, A., Mirtorabi, S., Roy, A., and F. Baker, "OSPFv3
	LSA Extendibility", draft-ietf-ospf-ospfv3-lsa-extend-06		LSA Extendibility", draft-ietf-ospf-ospfv3-lsa-extend-06
	(work in progress), February 2015.		(work in progress), February 2015.
			[OSPFV3] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
			for IPv6", RFC 5340, July 2008.
	[RFC7120] Cotton, M., "Early IANA Allocation of Standards Track Code		[RFC7120] Cotton, M., "Early IANA Allocation of Standards Track Code
	Points", BCP 100, RFC 7120, January 2014.		Points", BCP 100, RFC 7120, January 2014.
	[SEGMENT-ROUTING]		[SEGMENT-ROUTING]
	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-04.txt (work in progress), February		routing-extensions-04.txt (work in progress), February
	2015.		2015.
	skipping to change at page 15, line 4 ¶		skipping to change at page 15, line 18 ¶
	Extensions for Segment Routing", draft-ietf-ospf-segment-		Extensions for Segment Routing", draft-ietf-ospf-segment-
	routing-extensions-04.txt (work in progress), February		routing-extensions-04.txt (work in progress), February
	2015.		2015.
	[TI-LFA] Francois, P., Filsfils, C., Bashandy, A., Decraene, B.,		[TI-LFA] Francois, P., Filsfils, C., Bashandy, A., Decraene, B.,
	and S. Litkowski, "Topology Independent Fast Reroute using		and S. Litkowski, "Topology Independent Fast Reroute using
	Segment Routing", draft-francois-spring-segment-routing-		Segment Routing", draft-francois-spring-segment-routing-
	ti-lfa-01.txt (work in progress), October 2014.		ti-lfa-01.txt (work in progress), October 2014.
	Authors' Addresses		Authors' Addresses
	Peter Psenak		Peter Psenak
	Cisco Systems		Cisco Systems
	Apollo Business Center		Apollo Business Center
	Mlynske nivy 43		Mlynske nivy 43
	Bratislava, 821 09		Bratislava, 821 09
	Slovakia		Slovakia
	Email: ppsenak@cisco.com		Email: ppsenak@cisco.com
	Hannes Gredler		Hannes Gredler
	Juniper Networks, Inc.		Juniper Networks, Inc.
	1194 N. Mathilda Ave.		1194 N. Mathilda Ave.
	Sunnyvale, CA 94089		Sunnyvale, CA 94089
	USA		USA
	Email: hannes@juniper.net		Email: hannes@juniper.net
	Rob Shakir		Rob Shakir
	British Telcom		Individual Contributor
	London		London
	UK		UK
	Email: rob.shakir@bt.com		Email: rjs@rob.sh
	Wim Henderickx		Wim Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	Copernicuslaan		Copernicuslaan
	Antwerp, 2018 94089		Antwerp, 2018 94089
	Belgium		Belgium
	Email: wim.henderickx@alcatel-lucent.com		Email: wim.henderickx@alcatel-lucent.com
	Jeff Tantsura		Jeff Tantsura
	Ericsson		Ericsson
	300 Holger Way		300 Holger Way
	San Jose, CA 95134		San Jose, CA 95134
	USA		USA
	Email: jeff.tantsura@ericsson.com		Email: jeff.tantsura@ericsson.com
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		USA
	Email: acee@cisco.com		Email: acee@cisco.com
End of changes. 33 change blocks.
	35 lines changed or deleted		61 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/