Diff: draft-ietf-ospf-ospfv3-lsa-extend-20.txt - draft-ietf-ospf-ospfv3-lsa-extend-21.txt

	< draft-ietf-ospf-ospfv3-lsa-extend-20.txt	draft-ietf-ospf-ospfv3-lsa-extend-21.txt >

	Network Working Group A. Lindem	Network Working Group A. Lindem
	Internet-Draft A. Roy	Internet-Draft A. Roy
	Updates: 5340, 5838 (if approved) Cisco Systems	Updates: 5340, 5838 (if approved) Cisco Systems
	Intended status: Standards Track D. Goethals	Intended status: Standards Track D. Goethals

	Expires: June 29, 2018 Nokia	Expires: July 23, 2018 Nokia
	V. Reddy Vallem	V. Reddy Vallem

	F. Baker	F. Baker

	December 26, 2017	January 19, 2018

	OSPFv3 LSA Extendibility	OSPFv3 LSA Extendibility

	draft-ietf-ospf-ospfv3-lsa-extend-20.txt	draft-ietf-ospf-ospfv3-lsa-extend-21.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 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 June 29, 2018.	This Internet-Draft will expire on July 23, 2018.

	Copyright Notice	Copyright Notice


	Copyright (c) 2017 IETF Trust and the persons identified as the	Copyright (c) 2018 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
	the Trust Legal Provisions and are provided without warranty as	the Trust Legal Provisions and are provided without warranty as

	skipping to change at page 29, line 16 ¶	skipping to change at page 29, line 16 ¶
	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

	Types in the range 9-32767 are allocated via IETF Consensus or IESG	Types in the range 9-32767 are allocated via IETF Consensus or IESG
	Approval.	Approval.

	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-45055 are to be assigned on a FCFS basis	Types in the range 33024-45055 are to be assigned on a First-Come-
	subject to IETF expert review.	First-Serve (FCFS) basis.

	Types in the range 45056-65535 are not to be assigned at this time.	Types in the range 45056-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.2. OSPFv3 Extended-LSA sub-TLV Registry	8.2. OSPFv3 Extended-LSA sub-TLV Registry

	The OSPFv3 Extended-LSA sub-TLV registry will define sub-TLVs at any	The OSPFv3 Extended-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

	skipping to change at page 29, line 46 ¶	skipping to change at page 29, line 46 ¶
	o 2 - IPv4 Forwarding Address sub-TLV	o 2 - IPv4 Forwarding Address sub-TLV

	o 3 - Route Tag sub-TLV	o 3 - Route Tag sub-TLV

	Types in the range 4-32767 are allocated via IETF Consensus or IESG	Types in the range 4-32767 are allocated via IETF Consensus or IESG
	Approval.	Approval.

	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-45055 are to be assigned on a FCFS basis	Types in the range 33024-45055 are to be assigned on a First-Come-
	subject to IETF expert review.	First-Serve (FCFS) basis.

	Types in the range 45056-65535 are not to be assigned at this time.	Types in the range 45056-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.

	9. Contributors	9. Contributors

	Contributors' Addresses	Contributors' Addresses


	skipping to change at page 37, line 11 ¶	skipping to change at page 37, line 11 ¶

	Thanks to David Lamparter for review and suggestions on backward	Thanks to David Lamparter for review and suggestions on backward
	compatibility.	compatibility.

	Thanks to Karsten Thomann, Chris Bowers, Meng Zhang, and Nagendra	Thanks to Karsten Thomann, Chris Bowers, Meng Zhang, and Nagendra
	Kumar for review and editorial comments.	Kumar for review and editorial comments.

	Thanks to Alia Atlas for substantive Routing Area Director (AD)	Thanks to Alia Atlas for substantive Routing Area Director (AD)
	comments prior to IETF last call.	comments prior to IETF last call.


		Thanks to Mehmet Ersue for OPS Directorate review.

	The RFC text was produced using Marshall Rose's xml2rfc tool.	The RFC text was produced using Marshall Rose's xml2rfc tool.

	Authors' Addresses	Authors' Addresses

	Acee Lindem	Acee Lindem
	Cisco Systems	Cisco Systems
	301 Midenhall Way	301 Midenhall Way
	Cary, NC 27513	Cary, NC 27513
	USA	USA


End of changes. 8 change blocks.
	9 lines changed or deleted	11 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/