< draft-ietf-ospf-ospfv3-lsa-extend-07.txt		draft-ietf-ospf-ospfv3-lsa-extend-08.txt >
	Network Working Group A. Lindem		Network Working Group A. Lindem
	Internet-Draft S. Mirtorabi		Internet-Draft S. Mirtorabi
	Intended status: Standards Track A. Roy		Intended status: Standards Track A. Roy
	Expires: February 12, 2016 F. Baker		Expires: April 10, 2016 F. Baker
	Cisco Systems		Cisco Systems
	August 11, 2015		October 8, 2015
	OSPFv3 LSA Extendibility		OSPFv3 LSA Extendibility
	draft-ietf-ospf-ospfv3-lsa-extend-07.txt		draft-ietf-ospf-ospfv3-lsa-extend-08.txt
	Abstract		Abstract
	OSPFv3 requires functional extension beyond what can readily be done		OSPFv3 requires functional extension beyond what can readily be done
	with the fixed-format Link State Advertisement (LSA) as described in		with the fixed-format Link State Advertisement (LSA) as described in
	RFC 5340. Without LSA extension, attributes associated with OSPFv3		RFC 5340. Without LSA extension, attributes associated with OSPFv3
	links and advertised IPv6 prefixes must be advertised in separate		links and advertised IPv6 prefixes must be advertised in separate
	LSAs and correlated to the fixed-format LSAs. This document extends		LSAs and correlated to the fixed-format LSAs. This document extends
	the LSA format by encoding the existing OSPFv3 LSA information in		the LSA format by encoding the existing OSPFv3 LSA information in
	Type-Length-Value (TLV) tuples and allowing advertisement of		Type-Length-Value (TLV) tuples and allowing advertisement of
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 12, 2016.		This Internet-Draft will expire on April 10, 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 42 ¶		skipping to change at page 2, line 42 ¶
	4.1. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . 16		4.1. OSPFv3 E-Router-LSA . . . . . . . . . . . . . . . . . . . 16
	4.2. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . 18		4.2. OSPFv3 E-Network-LSA . . . . . . . . . . . . . . . . . . 18
	4.3. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . 19		4.3. OSPFv3 E-Inter-Area-Prefix-LSA . . . . . . . . . . . . . 19
	4.4. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . 20		4.4. OSPFv3 E-Inter-Area-Router-LSA . . . . . . . . . . . . . 20
	4.5. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . 21		4.5. OSPFv3 E-AS-External-LSA . . . . . . . . . . . . . . . . 21
	4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 22		4.6. OSPFv3 E-NSSA-LSA . . . . . . . . . . . . . . . . . . . . 22
	4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 23		4.7. OSPFv3 E-Link-LSA . . . . . . . . . . . . . . . . . . . . 23
	4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 25		4.8. OSPFv3 E-Intra-Area-Prefix-LSA . . . . . . . . . . . . . 25
	5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 25		5. Malformed OSPFv3 Extended LSA Handling . . . . . . . . . . . 25
	6. LSA Extension Backward Compatibility . . . . . . . . . . . . 26		6. LSA Extension Backward Compatibility . . . . . . . . . . . . 26
	6.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . 27		6.1. Extended LSA Mixed-Mode Backward Compatibility . . . . . 28
	6.1.1. Area Extended LSA Mixed-Mode Backward Compatibility . 28		6.1.1. Area Extended LSA Mixed-Mode Backward Compatibility . 28
	6.2. LSA TLV Processing Backward Compatibility . . . . . . . . 29		6.2. Extended LSA Spare-Mode Backward Compatibility . . . . . 29
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 29		6.3. LSA TLV Processing Backward Compatibility . . . . . . . . 29
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29		7. Security Considerations . . . . . . . . . . . . . . . . . . . 30
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 30		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
	9.1. Normative References . . . . . . . . . . . . . . . . . . 30		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 31
	9.2. Informative References . . . . . . . . . . . . . . . . . 31		9.1. Normative References . . . . . . . . . . . . . . . . . . 31
	Appendix A. Global Configuration Parameters . . . . . . . . . . 31		9.2. Informative References . . . . . . . . . . . . . . . . . 32
	Appendix B. Area Configuration Parameters . . . . . . . . . . . 32		Appendix A. Global Configuration Parameters . . . . . . . . . . 32
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33		Appendix B. Area Configuration Parameters . . . . . . . . . . . 33
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 34
	1. Introduction		1. Introduction
	OSPFv3 requires functional extension beyond what can readily be done		OSPFv3 requires functional extension beyond what can readily be done
	with the fixed-format Link State Advertisement (LSA) as described in		with the fixed-format Link State Advertisement (LSA) as described in
	RFC 5340 [OSPFV3]. Without LSA extension, attributes associated with		RFC 5340 [OSPFV3]. Without LSA extension, attributes associated with
	OSPFv3 links and advertised IPv6 prefixes must be advertised in		OSPFv3 links and advertised IPv6 prefixes must be advertised in
	separate LSAs and correlated to the fixed-format LSAs. This document		separate LSAs and correlated to the fixed-format LSAs. This document
	extends the LSA format by encoding the existing OSPFv3 LSA		extends the LSA format by encoding the existing OSPFv3 LSA
	information in Type-Length-Value (TLV) tuples and allowing		information in Type-Length-Value (TLV) tuples and allowing
	skipping to change at page 26, line 18 ¶		skipping to change at page 26, line 18 ¶
	In the context of this document, backward compatibility is solely		In the context of this document, backward compatibility is solely
	related to the capability of an OSPFv3 router to receive, process,		related to the capability of an OSPFv3 router to receive, process,
	and originate the TLV-based LSAs defined herein. Unrecognized TLVs		and originate the TLV-based LSAs defined herein. Unrecognized TLVs
	and sub-TLVs are ignored. Backward compatibility for future OSPFv3		and sub-TLVs are ignored. Backward compatibility for future OSPFv3
	extensions utilizing the TLV-based LSAs is out of scope and must be		extensions utilizing the TLV-based LSAs is out of scope and must be
	covered in the documents describing those extensions. Both full and,		covered in the documents describing those extensions. Both full and,
	if applicable, partial deployment SHOULD be specified for future TLV-		if applicable, partial deployment SHOULD be specified for future TLV-
	based OSPFv3 LSA extensions.		based OSPFv3 LSA extensions.
	Two distinct backward compatibility modes are supported dependent on		Three distinct backward compatibility modes are supported dependent
	the OSPFv3 routing domain migration requirements. For simplicity and		on the OSPFv3 routing domain migration requirements. For simplicity
	to avoid the scaling impact of maintaining both TLV and non-TLV based		and to avoid the scaling impact of maintaining both TLV and non-TLV
	versions of the same LSA within a routing domain, the basic backward		based versions of the same LSA within a routing domain, the basic
	compatibility mode will not allow mixing of LSA formats. Different		backward compatibility mode will not allow mixing of LSA formats.
	LSA formats could still be supported with multiple OSPFv3 instances		Different LSA formats could still be supported with multiple OSPFv3
	and separate OSPFv3 routing domains. Additionally, a more flexible		instances and separate OSPFv3 routing domains. Additionally, a more
	mode is provided in Section 6.1, where both formats of LSA coexist.		flexible mode is provided in Section 6.1, where both formats of LSA
	In order to facilitate backward compatibility, the OSPFv3 options		coexist. In order to facilitate backward compatibility, the OSPFv3
	field (as described in Appendix A.2 of RFC 5340 [OSPFV3]), will		options field (as described in Appendix A.2 of RFC 5340 [OSPFV3]),
	contain two additional options bits. The EL-bits will be used to		will contain two additional options bits. The EL-bits will be used
	indicate that the OSPFv3 router's level of Extended LSA support. An		to indicate that the OSPFv3 router's level of Extended LSA support.
	OSPFv3 router configured to support extended LSAs MUST set its		An OSPFv3 router configured to support extended LSAs MUST set its
	options field EL-bits in OSPFv3 Hello and Database Description		options field EL-bits in OSPFv3 Hello and Database Description
	packets as follows:		packets as follows:
	B'00'		B'00'
	None - Extended LSAs are not originate nor used in the SPF		None - Extended LSAs are not originated nor used in the SPF
	calculation.		calculation (except for future functionalities as described in
			Section 6.2) .
	B'01'		B'01'
	MixedModeOriginateOnly - Both extended and non-extended LSAs are		MixedModeOriginateOnly - Both extended and non-extended LSAs are
	originated. Non-extended LSAs are used in the SPF computation.		originated. Non-extended LSAs are used in the SPF computation.
	B'10'		B'10'
	MixedModeOriginateSPF - Both extended and non-extended LSAs are		MixedModeOriginateSPF - Both extended and non-extended LSAs are
	originated. Extended LSAs are used in the SPF computation.		originated. Extended LSAs are used in the SPF computation.
	B'11'		B'11'
	skipping to change at page 27, line 17 ¶		skipping to change at page 27, line 17 ¶
	Database Description packets with the options field EL-bits set to		Database Description packets with the options field EL-bits set to
	MixedModeOriginateOnly or None. Similarly, if MixModeOriginateSPF is		MixedModeOriginateOnly or None. Similarly, if MixModeOriginateSPF is
	specified for ExtendedLSASupport, the OSPFv3 router MUST NOT form		specified for ExtendedLSASupport, the OSPFv3 router MUST NOT form
	adjacencies with OSPFv3 Routers sending OSPFv3 Hello and Database		adjacencies with OSPFv3 Routers sending OSPFv3 Hello and Database
	Description packets with the options field EL-bits set to None		Description packets with the options field EL-bits set to None
	(B'00'). In this manner, OSPFv3 routers using new encodings can be		(B'00'). In this manner, OSPFv3 routers using new encodings can be
	completely isolated from those OSPFv3 routers depending on the RFC		completely isolated from those OSPFv3 routers depending on the RFC
	5340 encoding and not setting their options field EL-bits since the		5340 encoding and not setting their options field EL-bits since the
	default setting indicates no support for extended LSAs.		default setting indicates no support for extended LSAs.
			Finally, a mode supporting existing OSPFv3 routing domains is
			provided. This mode, subsequently referred to as "sparse-mode", will
			use the TLV-based LSAs solely in support of new functionality
			Section 6.2. In this compatibility mode, the EL-bits will be
			advertised as B'00' since the backward compatibility with the non-
			extended LSAs is not supported or required.
	1 2		1 2
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+--+-+-+--+-+-+-+-+--+		+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+--+-+-+--+-+-+-+-+--+
	| | | | | | | | | | | | EL|AT|L|AF|*|*|DC|R|N|x|E|V6|		| | | | | | | | | | | | EL|AT|L|AF|*|*|DC|R|N|x|E|V6|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+--+-+-+--+-+-+-+-+--+		+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+--+-+-+--+-+-+-+-+--+
	The Options field		The Options field
	EL-bits		EL-bits
	These bits indicate the level of Extended LSA support.		These bits indicate the level of Extended LSA support.
	B'00' - Extended LSAs are not originate nor used in the		B'00' - Extended LSAs are not originate nor used in the
	SPF calculation.		SPF calculation (except for new functionalities
			for future functions as described in Section 6.2).
	B'01' - Both extended and non-extended LSAs are originated.		B'01' - Both extended and non-extended LSAs are originated.
	Non-extended LSAs are used in the SPF computation.		Non-extended LSAs are used in the SPF computation.
	B'10' - Both extended and non-extended LSAs are originated.		B'10' - Both extended and non-extended LSAs are originated.
	Extended LSAs are used in the SPF computation.		Extended LSAs are used in the SPF computation.
	B'11' - Only extended LSA are originated and used in the		B'11' - Only extended LSA are originated and used in the
	SPF computation.		SPF computation.
	Options Field EL-bits		Options Field EL-bits
	The EL-bits will also be set in the LSA options field in Extended and		The EL-bits will also be set in the LSA options field in Extended and
	skipping to change at page 29, line 9 ¶		skipping to change at page 29, line 19 ¶
	LSAs even when AreaExtendedLSASupport takes precedence.		LSAs even when AreaExtendedLSASupport takes precedence.
	When preforming a graceful restart [GRACEFUL-RESTART], an OSPFv3		When preforming a graceful restart [GRACEFUL-RESTART], an OSPFv3
	router configured with MixedModeOriginate will use the non-extended		router configured with MixedModeOriginate will use the non-extended
	OSPFv3 LSAs to determine whether or not the graceful restart has		OSPFv3 LSAs to determine whether or not the graceful restart has
	completed successfully. Similarly, an OSPFv3 router configured with		completed successfully. Similarly, an OSPFv3 router configured with
	MixedModeOriginateSPF will use the extended LSAs. In other words,		MixedModeOriginateSPF will use the extended LSAs. In other words,
	successful OSPFv3 graceful restart determination will follow the SPF		successful OSPFv3 graceful restart determination will follow the SPF
	calculation.		calculation.
	6.2. LSA TLV Processing Backward Compatibility		6.2. Extended LSA Spare-Mode Backward Compatibility
			In this mode, OSPFv3 will use the non-extended LSAs for the SPF
			computation and will only originate extended LSAs when LSA
			origination is required in support of addtional functionality.
			Furthermore, the extended LSAs will only include those TLVs which
			require further specification for that new functionality. Hence,
			this mode of compatibility is know as "sparse-mode". The advantage
			of sparse-mode is that functionality utilizing the OSPFv3 extended
			LSAs can be added to an existing OSFPv3 routing domain without the
			requirement for migration. In essence, this compatibility mode is
			very much like the approach taken for OSPFv2 [OSPF-PREFIX-LINK]. As
			with all the compatibility modes, backward compatibility for the
			functions utilizing the extended LSAs must be described in the IETF
			documents describing those functions.
			6.3. LSA TLV Processing Backward Compatibility
	This section defines the general rules for processing LSA TLVs. To		This section defines the general rules for processing LSA TLVs. To
	ensure compatibility of future TLV-based LSA extensions, all		ensure compatibility of future TLV-based LSA extensions, all
	implementations MUST adhere to these rules:		implementations MUST adhere to these rules:
	1. Unrecognized TLVs and sub-TLVs are ignored when parsing or		1. Unrecognized TLVs and sub-TLVs are ignored when parsing or
	processing Extended-LSAs.		processing Extended-LSAs.
	2. Whether or not partial deployment of a given TLV is supported		2. Whether or not partial deployment of a given TLV is supported
	MUST be specified.		MUST be specified.
	skipping to change at page 30, line 24 ¶		skipping to change at page 31, line 4 ¶
	o 3 - Inter-Area Prefix TLV		o 3 - Inter-Area Prefix TLV
	o 4 - Inter-Area Router TLV		o 4 - Inter-Area Router TLV
	o 5 - External Prefix TLV		o 5 - External Prefix TLV
	o 6 - Intra-Area Prefix TLV		o 6 - Intra-Area Prefix TLV
	o 7 - IPv6 Link-Local Address TLV		o 7 - IPv6 Link-Local Address TLV
	o 8 - IPv4 Link-Local Address TLV		o 8 - IPv4 Link-Local Address TLV
	The OSPFv3 Extend-LSA sub-TLV registry will define sub-TLVs at any		The OSPFv3 Extend-LSA sub-TLV registry will define sub-TLVs at any
	level of nesting for Extended-LSAs and should be placed in the		level of nesting for Extended-LSAs and should be placed in the
	existing OSPFv3 IANA registry. New values can be allocated via IETF		existing OSPFv3 IANA registry. New values can be allocated via IETF
	Consensus or IESG Approval.		Review.
	Three values are allocated by this specification:		Three values are allocated by this specification:
	o 0 - Reserved		o 0 - Reserved
	o 1 - Forwarding Address		o 1 - Forwarding Address
	o 2 - Route Tag		o 2 - Route Tag
	The OSPFv3 Prefix Options registry will define a new code point for		The OSPFv3 Prefix Options registry will define a new code point for
	skipping to change at page 31, line 34 ¶		skipping to change at page 32, line 16 ¶
	[MT-OSPFV3]		[MT-OSPFV3]
	Mirtorabi, S. and A. Roy, "Multi-topology routing in		Mirtorabi, S. and A. Roy, "Multi-topology routing in
	OSPFv3 (MT-OSPFV3)", draft-ietf-ospf-mt-ospfv3-03.txt		OSPFv3 (MT-OSPFV3)", draft-ietf-ospf-mt-ospfv3-03.txt
	(work in progress), January 2008.		(work in progress), January 2008.
	[OSPF-DIGITAL-SIGNATURE]		[OSPF-DIGITAL-SIGNATURE]
	Murphy, S., Badger, M., and B. Wellington, "OSPF with		Murphy, S., Badger, M., and B. Wellington, "OSPF with
	Digital Signatures", RFC 2154, June 1997.		Digital Signatures", RFC 2154, June 1997.
			[OSPF-PREFIX-LINK]
			Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
			Tantsura, J., and A. Lindem, "OSPF Prefix/Link
			Attributes", draft-ietf-ospf-prefix-link-attr-13.txt (work
			in progress), August 2015.
	[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-05.txt (work in progress), February
	2015.		2015.
	Appendix A. Global Configuration Parameters		Appendix A. Global Configuration Parameters
	An additional global configurable parameter will be added to the		An additional global configurable parameter will be added to the
	OSPFv3 protocol.		OSPFv3 protocol.
	ExtendedLSASupport		ExtendedLSASupport
	This is an enumeration type indicating the extent to which the		This is an enumeration type indicating the extent to which the
	OSPFv3 instance supports the TLV format described herein for		OSPFv3 instance supports the TLV format described herein for
	Extended LSAs. The valid values for the enumeration are:		Extended LSAs. The valid values for the enumeration are:
	* None - Extended LSAs will not be originated or used in the SPF		* None - Extended LSAs will not be originated or used in the SPF
	calculation. This is the default.		calculation. This is the default. When OSPFv3 functions
			requiring extended LSA are configured, and the
			ExtendedLSASuppport is "None", extended LSAs may be used as
			described in Section 6.2.
	* MixedModeOriginateOnly - Both extended and non-extended LSAs		* MixedModeOriginateOnly - Both extended and non-extended LSAs
	will be originated. OSPFv3 adjacencies will be formed with		will be originated. OSPFv3 adjacencies will be formed with
	OSPFv3 routers not supporting this specification. The non-		OSPFv3 routers not supporting this specification. The non-
	extended LSAs are used for the SPF computation.		extended LSAs are used for the SPF computation.
	* MixedModeOriginateSPF - Both extended and non-extended LSAs		* MixedModeOriginateSPF - Both extended and non-extended LSAs
	will be originated. OSPFv3 adjacencies will be formed with		will be originated. OSPFv3 adjacencies will be formed with
	OSPFv3 routers not supporting this specification. The extended		OSPFv3 routers not supporting this specification. The extended
	LSAs are used for the SPF computation.		LSAs are used for the SPF computation.
	* Full - Extended LSAs will be originated and adjacencies will		* Full - Extended LSAs will be originated and adjacencies will
	not be formed with OSPFv3 routers not supporting this		ndot be formed with OSPFv3 routers not supporting this
	specification. Only Extended LSAs will be originated.		specification. Only Extended LSAs will be originated.
	Appendix B. Area Configuration Parameters		Appendix B. Area Configuration Parameters
	An additional area configurable parameter will be added to the OSPFv3		An additional area configurable parameter will be added to the OSPFv3
	protocol.		protocol.
	AreaExtendedLSASupport		AreaExtendedLSASupport
	This is an enumeration type indicating the extent to which the		This is an enumeration type indicating the extent to which the
	OSPFv3 area supports the TLV format described herein for Extended		OSPFv3 area supports the TLV format described herein for Extended
	LSAs. The valid value for the enumeration are:		LSAs. The valid value for the enumeration are:
	* InheritGlobal - The AreaExtendedLSASupport will be inherited		* InheritGlobal - The AreaExtendedLSASupport will be inherited
	from ExtendedLSASupport. This is the default.		from ExtendedLSASupport. This is the default.
	* None - Non-extended LSAs will not be originated or used in the		* None - Extended LSAs will not be originated or used in the SPF
	SPF calculation.		calculation. This is the default. When OSPFv3 functions
			requiring extended LSA are configured, and the
			ExtendedLSASuppport is "None", the spare-mode compatability is
			in effect Section 6.2.
	* MixedModeOriginateOnly - Both extended and non-extended link		* MixedModeOriginateOnly - Both extended and non-extended link
	and area scoped LSAs will be originated. OSPFv3 adjacencies		and area scoped LSAs will be originated. OSPFv3 adjacencies
	will be formed with OSPFv3 routers not supporting this		will be formed with OSPFv3 routers not supporting this
	specification. The non-extended LSAs are used for the SPF		specification. The non-extended LSAs are used for the SPF
	computation.		computation.
	* MixedModeOriginateSPF - Both extended and non-extended link and		* MixedModeOriginateSPF - Both extended and non-extended link and
	area scoped LSAs will be originated. OSPFv3 adjacencies will		area scoped LSAs will be originated. OSPFv3 adjacencies will
	be formed with OSPFv3 routers not supporting this		be formed with OSPFv3 routers not supporting this
End of changes. 18 change blocks.
	38 lines changed or deleted		75 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/