< draft-ietf-ospf-prefix-link-attr-01.txt		draft-ietf-ospf-prefix-link-attr-02.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: March 12, 2015 Juniper Networks, Inc.		Expires: June 18, 2015 Juniper Networks, Inc.
	R. Shakir		R. Shakir
	British Telcom		British Telcom
	W. Henderickx		W. Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	J. Tantsura		J. Tantsura
	Ericsson		Ericsson
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	September 8, 2014		December 15, 2014
	OSPFv2 Prefix/Link Attribute Advertisement		OSPFv2 Prefix/Link Attribute Advertisement
	draft-ietf-ospf-prefix-link-attr-01.txt		draft-ietf-ospf-prefix-link-attr-02.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
	compatible.		compatible.
	Status of this Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 March 12, 2015.		This Internet-Draft will expire on June 18, 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	skipping to change at page 3, line 7 ¶		skipping to change at page 2, line 34 ¶
	modifications of such material outside the IETF Standards Process.		modifications of such material outside the IETF Standards Process.
	Without obtaining an adequate license from the person(s) controlling		Without obtaining an adequate license from the person(s) controlling
	the copyright in such materials, this document may not be modified		the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may		outside the IETF Standards Process, and derivative works of it may
	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 . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements notation . . . . . . . . . . . . . . . . . . 4		1.1. Requirements notation . . . . . . . . . . . . . . . . . . 3
	1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 4		1.2. Acknowledgments . . . . . . . . . . . . . . . . . . . . . 3
	2. OSPFv2 Extended Prefix Opaque LSA . . . . . . . . . . . . . . 5		2. OSPFv2 Extended Prefix Opaque LSA . . . . . . . . . . . . . . 4
	2.1. OSPFv2 Extended Prefix TLV . . . . . . . . . . . . . . . . 6		2.1. OSPFv2 Extended Prefix TLV . . . . . . . . . . . . . . . 5
	3. OSPFv2 Extended Link Opaque LSA . . . . . . . . . . . . . . . 8		3. OSPFv2 Extended Link Opaque LSA . . . . . . . . . . . . . . . 7
	3.1. OSPFv2 Extended Link TLV . . . . . . . . . . . . . . . . . 9		3.1. OSPFv2 Extended Link TLV . . . . . . . . . . . . . . . . 8
	4. Backward Compatibility . . . . . . . . . . . . . . . . . . . . 10		4. Backward Compatibility . . . . . . . . . . . . . . . . . . . 9
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	6.1. OSPF Extended Prefix LSA TLV Registry . . . . . . . . . . 11		6.1. OSPF Extended Prefix LSA TLV Registry . . . . . . . . . . 10
	6.2. OSPF Extended Prefix TLV Sub-TLV Registry . . . . . . . . 11		6.2. OSPF Extended Prefix TLV Sub-TLV Registry . . . . . . . . 11
	6.3. OSPF Extended Link LSA TLV Registry . . . . . . . . . . . 11		6.3. OSPF Extended Link LSA TLV Registry . . . . . . . . . . . 11
	6.4. OSPF Extended Link TLV Sub-TLV Registry . . . . . . . . . 12		6.4. OSPF Extended Link TLV Sub-TLV Registry . . . . . . . . . 11
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
	7.1. Normative References . . . . . . . . . . . . . . . . . . . 12		7.1. Normative References . . . . . . . . . . . . . . . . . . 12
	7.2. Informative References . . . . . . . . . . . . . . . . . . 13		7.2. Informative References . . . . . . . . . . . . . . . . . 12
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
	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
	backward compatible. This is in contrast to the approach taken in		backward compatible. This is in contrast to the approach taken in
	OSPFv3 [OSPFV3-LSA-EXTEND] where the existing LSAs will be replaced		OSPFv3 [I-D.ietf-ospf-ospfv3-lsa-extend] where the existing LSAs will
	by TLV-based extended LSAs.		be replaced by TLV-based extended LSAs.
	New requirements such as source/destination routing, route tagging,		New requirements such as source/destination routing, route tagging,
	and segment routing necessitate this extension.		and segment routing necessitate this extension.
	This specification defines the following OSPFv2 opaque LSAs:		This specification defines the following OSPFv2 opaque LSAs:
	1. OSPFv2 Extended Prefix LSA - Allows advertisement of additional		1. OSPFv2 Extended Prefix LSA - Allows advertisement of additional
	attributes for prefixes advertised in Router-LSAs, Network-LSAs,		attributes for prefixes advertised in Router-LSAs, Network-LSAs,
	Network-Summary-LSAs, NSSA-LSAs, and AS-External-LSAs [OSPFV2]		Network-Summary-LSAs, NSSA-LSAs, and AS-External-LSAs [OSPFV2]
	skipping to change at page 6, line 39 ¶		skipping to change at page 5, line 39 ¶
	However, since the opaque LSA type defines the flooding scope, the		However, since the opaque LSA type defines the flooding scope, the
	LSA flooding scope MUST satisfy the application specific requirements		LSA flooding scope MUST satisfy the application specific requirements
	for all the prefixes included in a single OSPFv2 Extended Prefix		for all the prefixes included in a single OSPFv2 Extended Prefix
	Opaque LSA. The OSPF Extended Prefix TLV has the following format:		Opaque LSA. The OSPF Extended Prefix 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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Route Type | Prefix Length | AF | Reserved |		| Route Type | Prefix Length | AF | Flags |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Address Prefix (variable) |		| Address Prefix (variable) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Sub-TLVs (variable) |		| Sub-TLVs (variable) |
	+- -+		+- -+
	| |		| |
	OSPFv2 Extended Prefix TLV		OSPFv2 Extended Prefix TLV
	Type		Type
	skipping to change at page 7, line 36 ¶		skipping to change at page 6, line 36 ¶
	7 - NSSA External		7 - NSSA External
	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.
			Flags: 1 octet field. The following flags are defined:
			0 1 2 3 4 5 6 7
			+--+--+--+--+--+--+--+--+
			|A | | | | | | | |
			+--+--+--+--+--+--+--+--+
			where:
			A-Flag: Attach flag. An ABR generating Extended Prefix TLV for
			inter-area prefix that is locally connected or attached in
			other connected area SHOULD set this flag.
	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
	used by receiving OSPFv2 Routers. This situation SHOULD be logged as		used by receiving OSPFv2 Routers. This situation SHOULD be logged as
	an error.		an error.
	skipping to change at page 10, line 34 ¶		skipping to change at page 10, line 17 ¶
	In general, new LSAs defined in this document are subject to the same		In general, new LSAs defined in this document are subject to the same
	security concerns as those described in [OSPFV2]. Additionally,		security concerns as those described in [OSPFV2]. Additionally,
	implementations must assure that malformed TLV and Sub-TLV		implementations must assure that malformed TLV and Sub-TLV
	permutations do not result in errors that cause hard OSPF failures.		permutations do not result in errors that cause hard OSPF failures.
	6. IANA Considerations		6. IANA Considerations
	This specification updates the Opaque Link-State Advertisements (LSA)		This specification updates the Opaque Link-State Advertisements (LSA)
	Option Types with the following values:		Option Types with the following values:
	o 7 (IANA Early Allocation [EARLY-ALLOCATION]) - OSPFv2 Extended		o 7 (IANA Early Allocation [RFC7120]) - OSPFv2 Extended Prefix
	Prefix Opaque LSA		Opaque LSA
	o 8 (IANA Early Allocation [EARLY-ALLOCATION]) - OSPFv2 Extended		o 8 (IANA Early Allocation [RFC7120]) - OSPFv2 Extended Link Opaque
	Link Opaque LSA		LSA
	This specification also creates four new registries:		This specification also creates four new registries:
	o OSPF Extended Prefix LSA TLVs		o OSPF Extended Prefix LSA TLVs
	o OSPF Extended Prefix TLV Sub-TLVs		o OSPF Extended Prefix TLV Sub-TLVs
	o OSPF Extended Link LSA TLVs		o OSPF Extended Link LSA TLVs
	o OSPF Extended Link TLV Sub-TLVs		o OSPF Extended Link TLV Sub-TLVs
	skipping to change at page 11, line 28 ¶		skipping to change at page 11, line 7 ¶
	Types in the range 32768-33023 are for experimental use; these will		Types in the range 32768-33023 are for experimental use; these will
	not be registered with IANA, and MUST NOT be mentioned by RFCs.		not be registered with IANA, and MUST NOT be mentioned by RFCs.
	Types in the range 33024-65535 are not to be assigned at this time.		Types in the range 33024-65535 are not to be assigned at this time.
	Before any assignments can be made in the 33024-65535 range, there		Before any assignments can be made in the 33024-65535 range, there
	MUST be an IETF specification that specifies IANA Considerations that		MUST be an IETF specification that specifies IANA Considerations that
	covers the range being assigned.		covers the range being assigned.
	6.2. OSPF Extended Prefix TLV Sub-TLV Registry		6.2. OSPF Extended Prefix TLV Sub-TLV Registry
	The OSPF Extended Link LSA sub-TLV registry will define will define		The OSPF Extended Link LSA sub-TLV registry will define sub-TLVs at
	sub-TLVs at any level of nesting for Extended Link LSAs and should be		any level of nesting for Extended Link LSAs and should be placed in
	placed in the existing OSPF IANA registry. New values can be		the existing OSPF IANA registry. New values can be allocated via
	allocated via IETF Consensus or IESG Approval.		IETF Consensus or IESG Approval.
	The following initial values are allocated:		The following initial values are allocated:
	o 0 - Reserved		o 0 - Reserved
	Types in the range 32768-33023 are for experimental use; these will		Types in the range 32768-33023 are for experimental use; these will
	not be registered with IANA, and MUST NOT be mentioned by RFCs.		not be registered with IANA, and MUST NOT be mentioned by RFCs.
	Types in the range 33024-65535 are not to be assigned at this time.		Types in the range 33024-65535 are not to be assigned at this time.
	Before any assignments can be made in the 33024-65535 range, there		Before any assignments can be made in the 33024-65535 range, there
	skipping to change at page 13, line 7 ¶		skipping to change at page 12, line 32 ¶
	[RFC-KEYWORDS]		[RFC-KEYWORDS]
	Bradner, S., "Key words for use in RFCs to Indicate		Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", RFC 2119, March 1997.		Requirement Levels", RFC 2119, March 1997.
	[TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering		[TE] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering
	Extensions to OSPF", RFC 3630, September 2003.		Extensions to OSPF", RFC 3630, September 2003.
	7.2. Informative References		7.2. Informative References
	[EARLY-ALLOCATION]		[I-D.ietf-ospf-ospfv3-lsa-extend]
	Cotton, M., "Early Allocation of Standards Track Code
	Points", RFC 7120, January 2014.
	[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",		LSA Extendibility", draft-ietf-ospf-ospfv3-lsa-extend-05
	draft-ietf-ospf-ospfv3-lsa-extend-02.txt (work in		(work in progress), November 2014.
	progress).
			[RFC7120] Cotton, M., "Early IANA Allocation of Standards Track Code
			Points", BCP 100, RFC 7120, January 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
End of changes. 15 change blocks.
	42 lines changed or deleted		54 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/