< draft-ietf-ospf-prefix-link-attr-11.txt		draft-ietf-ospf-prefix-link-attr-12.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: February 19, 2016 Juniper Networks, Inc.		Expires: February 20, 2016 Juniper Networks, Inc.
	R. Shakir		R. Shakir
	Individual Contributor		Individual Contributor
	W. Henderickx		W. Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	J. Tantsura		J. Tantsura
	Ericsson		Ericsson
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	August 18, 2015		August 19, 2015
	OSPFv2 Prefix/Link Attribute Advertisement		OSPFv2 Prefix/Link Attribute Advertisement
	draft-ietf-ospf-prefix-link-attr-11.txt		draft-ietf-ospf-prefix-link-attr-12.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 February 19, 2016.		This Internet-Draft will expire on February 20, 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 4, line 17 ¶		skipping to change at page 4, line 17 ¶
	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 [SEGMENT-ROUTING]), the LSA flooding scope		mapping server deployment [SEGMENT-ROUTING]), the LSA flooding scope
	may be greater 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 | LS Type |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Opaque type | Opaque ID |		| Opaque type | Opaque ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Advertising Router |		| Advertising Router |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| 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		The opaque type used by OSPFv2 Extended Prefix Opaque LSA is 7. The
	opaque type is used to differentiate the various type of OSPFv2		opaque type is used to differentiate the various type of OSPFv2
	Opaque LSA and is described in section 3 of [OPAQUE]. The LSA		Opaque LSA and is described in section 3 of [OPAQUE]. The LS Type
	"Length" field [OSPFV2] represents the total length (in octets) of		may be 10 or 11 indicating that the Opaque LSA flooding scope is
	the Opaque LSA including the LSA header and all TLVs (including		area-local (10) or AS-wide (11) [OPAQUE]. The LSA "Length" field
	padding).		[OSPFV2] represents the total length (in octets) of the Opaque LSA
			including the LSA header and all TLVs (including padding).
	The Opaque ID field is an arbitrary value used to maintain multiple		The Opaque ID field is an arbitrary value used to maintain multiple
	Extended Prefix Opaque LSAs. For OSPFv2 Extended Prefix Opaque LSAs,		Extended Prefix Opaque LSAs. For OSPFv2 Extended Prefix Opaque LSAs,
	the Opaque ID has no semantic significance other than to		the Opaque ID has no semantic significance other than to
	differentiate Extended Prefix Opaque LSAs originated by the same		differentiate Extended Prefix Opaque LSAs originated by the same
	OSPFv2 router. If multiple Extended Prefix Opaque LSAs include the		OSPFv2 router. If multiple Extended Prefix Opaque LSAs include the
	same prefix, the attributes from the Opaque LSA with the lowest		same prefix, the attributes from the Opaque LSA with the lowest
	Opaque ID SHOULD be used.		Opaque ID SHOULD 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
	skipping to change at page 5, line 26 ¶		skipping to change at page 5, line 28 ¶
	TLV Format		TLV Format
	The Length field defines the length of the value portion in octets		The Length field defines the length of the value portion in octets
	(thus a TLV with no value portion would have a length of 0). The TLV		(thus a TLV with no value portion would have a length of 0). The TLV
	is padded to 4-octet alignment; padding is not included in the length		is padded to 4-octet alignment; padding is not included in the length
	field (so a 3-octet value would have a length of 3, but the total		field (so a 3-octet value would have a length of 3, but the total
	size of the TLV would be 8 octets). Nested TLVs are also 32-bit		size of the TLV would be 8 octets). Nested TLVs are also 32-bit
	aligned. For example, a 1-byte value would have the length field set		aligned. For example, a 1-byte value would have the length field set
	to 1, and 3 octets of padding would be added to the end of the value		to 1, and 3 octets of padding would be added to the end of the value
	portion of the TLV.		portion of the TLV. The padding is composed of zeros.
	2.1. OSPFv2 Extended Prefix TLV		2.1. OSPFv2 Extended Prefix TLV
	The OSPF Extended Prefix TLV is used to advertise additional		The OSPF Extended Prefix TLV is used to advertise additional
	attributes associated with the prefix. Multiple OSPF Extended Prefix		attributes associated with the prefix. Multiple OSPF Extended Prefix
	TLVs MAY be advertised in each OSPFv2 Extended Prefix Opaque LSA.		TLVs MAY be advertised in each OSPFv2 Extended Prefix Opaque LSA.
	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:
	skipping to change at page 8, line 29 ¶		skipping to change at page 8, line 29 ¶
	The OSPFv2 Extended Link Opaque LSA has an area flooding scope.		The OSPFv2 Extended Link Opaque LSA has an area flooding scope.
	Multiple OSPFv2 Extended Link Opaque LSAs can be advertised by a		Multiple OSPFv2 Extended Link Opaque LSAs can be advertised by a
	single router in an area.		single router in an area.
	The format of the OSPFv2 Extended Link Opaque LSA is as follows:		The format of the OSPFv2 Extended Link 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 | 10 |		| LS age | Options | LS Type |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Opaque type | Opaque ID |		| Opaque type | Opaque ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Advertising Router |		| Advertising Router |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| 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		The Opaque type used by OSPFv2 Extended Link Opaque LSA is 8. The LS
	opaque type is used to differentiate the various type of OSPFv2		Type is 10 indicating that the Opaque LSA flooding scope is area-
	Opaque LSA and is described in section 3 of [OPAQUE]. The LSA		local [OPAQUE]. The opaque type is used to differentiate the various
	"Length" field [OSPFV2] represents the total length (in octets) of		type of OSPFv2 Opaque LSA and is described in section 3 of [OPAQUE].
	the Opaque LSA including the LSA header and all TLVs (including		The LSA "Length" field [OSPFV2] represents the total length (in
	padding).		octets) of the Opaque LSA including the LSA header and all TLVs
			(including padding).
	The Opaque ID field is an arbitrary value used to maintain multiple		The Opaque ID field is an arbitrary value used to maintain multiple
	Extended Prefix Opaque LSAs. For OSPFv2 Extended Link Opaque LSAs,		Extended Prefix Opaque LSAs. For OSPFv2 Extended Link Opaque LSAs,
	the Opaque ID has no semantic significance other than to		the Opaque ID has no semantic significance other than to
	differentiate Extended Link Opaque LSAs originated by the same OSPFv2		differentiate Extended Link Opaque LSAs originated by the same OSPFv2
	router. If multiple Extended Link Opaque LSAs include the same link,		router. If multiple Extended Link Opaque LSAs include the same link,
	the attributes from the Opaque LSA with the lowest Opaque ID will be		the attributes from the Opaque LSA with the lowest Opaque ID will be
	used.		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
End of changes. 9 change blocks.
	17 lines changed or deleted		19 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/