< draft-ietf-ospf-prefix-link-attr-07.txt		draft-ietf-ospf-prefix-link-attr-08.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 2, 2016 Juniper Networks, Inc.		Expires: February 5, 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 1, 2015		August 4, 2015
	OSPFv2 Prefix/Link Attribute Advertisement		OSPFv2 Prefix/Link Attribute Advertisement
	draft-ietf-ospf-prefix-link-attr-07.txt		draft-ietf-ospf-prefix-link-attr-08.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 2, 2016.		This Internet-Draft will expire on February 5, 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 12, line 28 ¶		skipping to change at page 12, line 28 ¶
	o OSPF Extended Prefix Opaque LSA TLVs		o OSPF Extended Prefix Opaque LSA TLVs
	o OSPF Extended Prefix TLV Sub-TLVs		o OSPF Extended Prefix TLV Sub-TLVs
	o OSPF Extended Link Opaque LSA TLVs		o OSPF Extended Link Opaque LSA TLVs
	o OSPF Extended Link TLV Sub-TLVs		o OSPF Extended Link TLV Sub-TLVs
	7.1. OSPF Extended Prefix Opaque LSA TLV Registry		7.1. OSPF Extended Prefix Opaque LSA TLV Registry
	The OSPF Extend Prefix Opaque LSA TLV registry will define top-level		The "OSPF Extend Prefix Opaque LSA TLV" registry will define top-
	TLVs for Extended Prefix Opaque LSA and should be placed in the		level TLVs for the Extended Prefix Opaque LSAs and should be added to
	existing OSPF IANA registry. New values can be allocated via IETF		the "Open Shortest Path First v2 (OSPFv2) Parameters" registries
	Consensus or IESG Approval.		group. New values can be allocated via IETF Consensus or IESG
			Approval.
	The following initial values are allocated:		The following initial values are allocated:
	o 0 - Reserved		o 0 - Reserved
	o 1 - OSPF Extended Prefix TLV		o 1 - OSPF Extended Prefix TLV
	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.
	7.2. OSPF Extended Prefix TLV Sub-TLV Registry		7.2. OSPF Extended Prefix TLV Sub-TLV Registry
	The OSPF Extended Prefix TLV sub-TLV registry will define sub-TLVs at		The "OSPF Extended Prefix TLV sub-TLV" registry will define sub-TLVs
	any level of nesting for Extended Prefix TLV and should be placed in		at any level of nesting for Extended Prefix TLVs and should be added
	the existing OSPF IANA registry. New values can be allocated via		to the "Open Shortest Path First v2 (OSPFv2) Parameters" registries
	IETF Consensus or IESG Approval.		group. New values can be allocated via 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
	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.
	7.3. OSPF Extended Link Opaque LSA TLV Registry		7.3. OSPF Extended Link Opaque LSA TLV Registry
	The OSPF Extended Link Opaque LSA TLV registry will define top-level		The "OSPF Extended Link Opaque LSA TLV" registry will define top-
	TLVs for Extended Link Opaque LSAs and should be placed in the		level TLVs for Extended Link Opaque LSAs and should be added to the
	existing OSPF IANA registry. New values can be allocated via IETF		"Open Shortest Path First v2 (OSPFv2) Parameters" registries group.
	Consensus or IESG Approval.		New values can be allocated via IETF Consensus or IESG Approval.
	Following initial values are allocated:		Following initial values are allocated:
	o 0 - Reserved		o 0 - Reserved
	o 1 - OSPFv2 Extended Link TLV		o 1 - OSPFv2 Extended Link TLV
	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 am IETF specification that specifies IANA Considerations that		MUST be am IETF specification that specifies IANA Considerations that
	covers the range being assigned.		covers the range being assigned.
	7.4. OSPF Extended Link TLV Sub-TLV Registry		7.4. OSPF Extended Link TLV Sub-TLV Registry
	The OSPF Extended Link TLV sub-TLV registry will define sub-TLVs at		The OSPF Extended Link TLV sub-TLV registry will define sub-TLVs at
	any level of nesting for Extended Link TLV and should be placed in		any level of nesting for Extended Link TLVs and should be added to
	the existing OSPF IANA registry. New values can be allocated via		the "Open Shortest Path First v2 (OSPFv2) Parameters" registries
	IETF Consensus or IESG Approval.		group. New values can be allocated via 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
	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.
	8. Acknowledgments		8. Acknowledgments
	We would like to thank Anton Smirnov for his contribution.		We would like to thank Anton Smirnov for his contribution.
	Thanks to Tony Przygienda for his review and comments.		Thanks to Tony Przygienda for his review and comments.
	Thanks to Wim Henderickx, Greg Harkins, Peter Psenak, Eric Wu,		Thanks to Wim Henderickx, Greg Harkins, Peter Psenak, Eric Wu,
	Shraddha Hegde, and Csaba Mate for their responses to the		Shraddha Hegde, and Csaba Mate for their responses to the
	implementation survey.		implementation survey.
			Thanks to Alia Atlas for AD review and comments.
			Thanks to Tom Petch for review and comments.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The		[OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The
	OSPF Opaque LSA Option", RFC 5250, July 2008.		OSPF Opaque LSA Option", RFC 5250, July 2008.
	[OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.		[OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
	[RFC-KEYWORDS]		[RFC-KEYWORDS]
End of changes. 10 change blocks.
	20 lines changed or deleted		26 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/