< draft-ietf-lsr-ospf-prefix-originator-08.txt		draft-ietf-lsr-ospf-prefix-originator-09.txt >
	LSR Working Group A. Wang		LSR Working Group A. Wang
	Internet-Draft China Telecom		Internet-Draft China Telecom
	Intended status: Standards Track A. Lindem		Intended status: Standards Track A. Lindem
	Expires: September 9, 2021 Cisco Systems		Expires: September 20, 2021 Cisco Systems
	J. Dong		J. Dong
	Huawei Technologies		Huawei Technologies
	P. Psenak		P. Psenak
	K. Talaulikar		K. Talaulikar
	Cisco Systems		Cisco Systems
	March 8, 2021		March 19, 2021
	OSPF Prefix Originator Extensions		OSPF Prefix Originator Extensions
	draft-ietf-lsr-ospf-prefix-originator-08		draft-ietf-lsr-ospf-prefix-originator-09
	Abstract		Abstract
	This document defines OSPF extensions to include information		This document defines OSPF extensions to include information
	associated with the node originating a prefix along with the prefix		associated with the node originating a prefix along with the prefix
	advertisement.		advertisement.
	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
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 September 9, 2021.		This Internet-Draft will expire on September 20, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 14 ¶		skipping to change at page 2, line 14 ¶
	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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
	2. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3		2. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3
	2.1. Prefix Source Router-ID Sub-TLV . . . . . . . . . . . . . 3		2.1. Prefix Source OSPF Router-ID Sub-TLV . . . . . . . . . . 3
	2.2. Prefix Originator Sub-TLV . . . . . . . . . . . . . . . . 4		2.2. Prefix Source Router Address Sub-TLV . . . . . . . . . . 4
	3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 5		3. Elements of Procedure . . . . . . . . . . . . . . . . . . . . 5
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 6		4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7		6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
	7.1. Normative References . . . . . . . . . . . . . . . . . . 7		7.1. Normative References . . . . . . . . . . . . . . . . . . 8
	7.2. Informative References . . . . . . . . . . . . . . . . . 8		7.2. Informative References . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	Prefix attributes are advertised in OSPFv2 [RFC2328] using the		Prefix attributes are advertised in OSPFv2 [RFC2328] using the
	Extended Prefix Opaque Link State Advertisement (LSA) [RFC7684] and		Extended Prefix Opaque Link State Advertisement (LSA) [RFC7684] and
	in OSPFv3 [RFC5340] using the various Extended Prefix LSA types		in OSPFv3 [RFC5340] using the various Extended Prefix LSA types
	[RFC8362].		[RFC8362].
	skipping to change at page 3, line 38 ¶		skipping to change at page 3, line 38 ¶
	1.1. Requirements Language		1.1. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	2. Protocol Extensions		2. Protocol Extensions
	This document defines the Prefix Source Router-ID and the Prefix		This document defines the Prefix Source OSPF Router-ID and the Prefix
	Originator Sub-TLVs for inclusion of the Router ID and a reachable		Source Router Address Sub-TLVs for inclusion of the Router ID and a
	address information for the router originating the prefix as a prefix		reachable address information for the router originating the prefix
	attribute.		as a prefix attribute.
	2.1. Prefix Source Router-ID Sub-TLV		2.1. Prefix Source OSPF Router-ID Sub-TLV
	For OSPFv2, the Prefix Source Router-ID Sub-TLV is an optional Sub-		For OSPFv2, the Prefix Source OSPF Router-ID Sub-TLV is an optional
	TLV of the OSPFv2 Extended Prefix TLV [RFC7684]. For OSPFv3, the		Sub-TLV of the OSPFv2 Extended Prefix TLV [RFC7684]. For OSPFv3, the
	Prefix Source Router-ID Sub-TLV is an optional Sub-TLV of the Intra-		Prefix Source OSPF Router-ID Sub-TLV is an optional Sub-TLV of the
	Area-Prefix TLV, Inter-Area-Prefix TLV, and External-Prefix TLV		Intra-Area-Prefix TLV, Inter-Area-Prefix TLV, and External-Prefix TLV
	[RFC8362] when originating either an IPv4 [RFC5838] or an IPv6 prefix		[RFC8362] when originating either an IPv4 [RFC5838] or an IPv6 prefix
	advertisement.		advertisement.
	The Prefix Source Router-ID Sub-TLV has the following format:		The Prefix Source OSPF Router-ID Sub-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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| OSPF Router ID |		| OSPF Router ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: Prefix Source Router-ID Sub-TLV Format		Figure 1: Prefix Source OSPF Router-ID Sub-TLV Format
	Where:		Where:
	o Type: 4 for OSPFv2 and 27 for OSPFv3		o Type: 4 for OSPFv2 and 27 for OSPFv3
	o Length: 4		o Length: 4
	o OSPF Router ID : the OSPF Router ID of the OSPF router that		o OSPF Router ID : the OSPF Router ID of the OSPF router that
	originated the prefix advertisement in the OSPF domain.		originated the prefix advertisement in the OSPF domain.
	The parent TLV of a prefix advertisement MAY include more than one		The parent TLV of a prefix advertisement MAY include more than one
	Prefix Source Router-ID sub-TLV, one corresponding to each of the		Prefix Source OSPF Router-ID sub-TLV, one corresponding to each of
	Equal-Cost Multi-Path (ECMP) nodes that originated the given prefix.		the Equal-Cost Multi-Path (ECMP) nodes that originated the given
			prefix.
	For intra-area prefix advertisements, the Prefix Source Router-ID		For intra-area prefix advertisements, the Prefix Source OSPF Router-
	Sub-TLV MUST be considered invalid and ignored if it is not the same		ID Sub-TLV MUST be considered invalid and ignored if the OSPF Router
	as Advertising Router ID for the prefix advertisement.		ID field is not the same as Advertising Router field in the
			containing LSA. Similar validation cannot be reliably performed for
			inter-area and external prefix advertisements.
	A received Prefix Source Router-ID Sub-TLV with OSPF Router ID set to		A received Prefix Source OSPF Router-ID Sub-TLV with OSPF Router ID
	0 MUST be considered invalid and ignored. Additionally, reception of		set to 0 MUST be considered invalid and ignored. Additionally,
	such Sub-TLV SHOULD be logged as an error (subject to rate-limiting).		reception of such Sub-TLV SHOULD be logged as an error (subject to
			rate-limiting).
	2.2. Prefix Originator Sub-TLV		2.2. Prefix Source Router Address Sub-TLV
	For OSPFv2, the Prefix Originator Sub-TLV is an optional Sub-TLV of		For OSPFv2, the Prefix Source Router Address Sub-TLV is an optional
	the OSPFv2 Extended Prefix TLV [RFC7684]. For OSPFv3, the Prefix		Sub-TLV of the OSPFv2 Extended Prefix TLV [RFC7684]. For OSPFv3, the
	Originator Sub-TLV is an optional Sub-TLV of the Intra-Area-Prefix		Prefix Source Router Address Sub-TLV is an optional Sub-TLV of the
	TLV, Inter-Area-Prefix TLV, and External-Prefix TLV [RFC8362] when		Intra-Area-Prefix TLV, Inter-Area-Prefix TLV, and External-Prefix TLV
	originating either an IPv4 [RFC5838] or an IPv6 prefix advertisement.		[RFC8362] when originating either an IPv4 [RFC5838] or an IPv6 prefix
			advertisement.
	The Prefix Originator Sub-TLV has the following format:		The Prefix Source Router Address Sub-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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Router Address (4 or 16 octets) |		| Router Address (4 or 16 octets) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: Prefix Originator Sub-TLV Format		Figure 2: Prefix Source Router Address Sub-TLV Format
	Where:		Where:
	o Type: TBD1 for OSPFv2 and TBD2 for OSPFv3		o Type: TBD1 for OSPFv2 and TBD2 for OSPFv3
	o Length: 4 or 16		o Length: 4 or 16
	o Router Address: A reachable IPv4 or IPv6 router address for the		o Router Address: A reachable IPv4 or IPv6 router address for the
	router that originated the IPv4 or IPv6 prefix advertisement		router that originated the IPv4 or IPv6 prefix advertisement
	respectively. Such an address would be semantically equivalent to		respectively. Such an address would be semantically equivalent to
	what may be advertised in the OSPFv2 Router Address TLV [RFC3630]		what may be advertised in the OSPFv2 Router Address TLV [RFC3630]
	or in the OSPFv3 Router IPv6 Address TLV [RFC5329].		or in the OSPFv3 Router IPv6 Address TLV [RFC5329].
	A prefix advertisement MAY include more than one Prefix Originator		The parent TLV of a prefix advertisement MAY include more than one
	sub-TLV, one corresponding to each of the Equal-Cost Multi-Path		Prefix Source Router Address Sub-TLV, one corresponding to each of
	(ECMP) nodes that originated the given prefix.		the Equal-Cost Multi-Path (ECMP) nodes that originated the given
			prefix.
	A received Prefix Originator Sub-TLV that has an invalid length (i.e.		A received Prefix Source Router Address Sub-TLV that has an invalid
	not consistent with the prefix's address family) or a Router Address		length (i.e. not consistent with the prefix's address family) or a
	containing an invalid IPv4 or IPv6 address (dependent on address		Router Address containing an invalid IPv4 or IPv6 address (dependent
	family of the associated prefix) MUST be considered invalid and		on address family of the associated prefix) MUST be considered
	ignored. Additionally, reception of such Sub-TLV SHOULD be logged as		invalid and ignored. Additionally, reception of such Sub-TLV SHOULD
	an error (subject to rate-limiting).		be logged as an error (subject to rate-limiting).
	3. Elements of Procedure		3. Elements of Procedure
	This section describes the procedure for advertisement of the Prefix		This section describes the procedure for advertisement of the Prefix
	Source Router-ID and Prefix Originator Sub-TLVs along with the prefix		Source OSPF Router-ID and Prefix Source Router Address Sub-TLVs along
	advertisement.		with the prefix advertisement.
	The OSPF Router ID of the Prefix Source Router-ID is set to the OSPF		The OSPF Router ID of the Prefix Source OSPF Router-ID is set to the
	Router ID of the node originating the prefix in the OSPF domain.		OSPF Router ID of the node originating the prefix in the OSPF domain.
	If the originating node is advertising an OSPFv2 Router Address TLV		If the originating node is advertising an OSPFv2 Router Address TLV
	[RFC3630] or an OSPFv3 Router IPv6 Address TLV [RFC5329], then the		[RFC3630] or an OSPFv3 Router IPv6 Address TLV [RFC5329], then the
	same address SHOULD be used in the Router Address field of the Prefix		same address MUST be used in the Router Address field of the Prefix
	Originator Sub-TLV. When the originating node is not advertising		Source Router Address Sub-TLV. When the originating node is not
	such an address, implementations MAY support mechanisms to determine		advertising such an address, implementations can determine a unique
	a reachable address (e.g., advertised with the N-flag set [RFC7684]		and reachable address (i.e., advertised with the N-flag set [RFC7684]
	or N-bit set [RFC8362] and either matching the OSPF Router ID or the		or N-bit set [RFC8362]) belonging to the originating node to set in
	highest IP address) belonging to the originating node to set in the		the Router Address field.
	Router Address field.
	Implementations MAY support the selection of specific prefixes for		Implementations MAY support the selection of specific prefixes for
	which the originating node information needs to be included with		which the originating node information needs to be included with
	their prefix advertisements.		their prefix advertisements.
	When an ABR generates inter-area prefix advertisements into its non-		When an ABR generates inter-area prefix advertisements into its non-
	backbone areas corresponding to an inter-area prefix advertisement		backbone areas corresponding to an inter-area prefix advertisement
	from the backbone area, the only way to determine the originating		from the backbone area, the only way to determine the originating
	node information is based on the Prefix Source Router-ID and Prefix		node information is based on the Prefix Source OSPF Router-ID and
	Originator Sub-TLVs present in the inter-area prefix advertisement		Prefix Source Router Address Sub-TLVs present in the inter-area
	originated into the backbone area by an ABR from another non-backbone		prefix advertisement originated into the backbone area by an ABR from
	area. The ABR performs its prefix calculation to determine the set		another non-backbone area. The ABR performs its prefix calculation
	of nodes that contribute to the best prefix reachability. It MUST		to determine the set of nodes that contribute to the best prefix
	use the prefix originator information only from this set of nodes.		reachability. It MUST use the prefix originator information only
	The ABR MUST NOT include the Prefix Source Router-ID or the Prefix		from this set of nodes. The ABR MUST NOT include the Prefix Source
	Originator Sub-TLVs when it is unable to determine the information of		OSPF Router-ID or the Prefix Source Router Address Sub-TLVs when it
	the best originating node.		is unable to determine the information of the best originating node.
	Implementations MAY provide control on ABRs to selectively disable		Implementations MAY provide control on ABRs to selectively disable
	the propagation of the originating node information across area		the propagation of the originating node information across area
	boundaries.		boundaries.
	Implementations may support the propagation of the originating node		Implementations may support the propagation of the originating node
	information along with a redistributed prefix into the OSPF domain		information along with a redistributed prefix into the OSPF domain
	from another routing domain. The details of such mechanisms are		from another routing domain. The details of such mechanisms are
	outside the scope of this document. Such implementations may also		outside the scope of this document. Such implementations may also
	provide control on whether the Router Address in the Prefix		provide control on whether the Router Address in the Prefix Source
	Originator Sub-TLV is set as the ABSR node address or as the address		Router Address Sub-TLV is set as the ABSR node address or as the
	of the actual node outside the OSPF domain that owns the prefix.		address of the actual node outside the OSPF domain that owns the
			prefix.
	When translating the NSSA prefix advertisements [RFC3101] to the AS		When translating the NSSA prefix advertisements [RFC3101] to the AS
	external prefix advertisements, the NSSA ABR, follows the same		external prefix advertisements, the NSSA ABR, follows the same
	procedures as an ABR generating inter-area prefix advertisements for		procedures as an ABR generating inter-area prefix advertisements for
	the propagation of the originating node information.		the propagation of the originating node information.
	4. Security Considerations		4. Security Considerations
	Since this document extends the OSPFv2 Extended Prefix LSA, the		Since this document extends the OSPFv2 Extended Prefix LSA, the
	security considerations for [RFC7684] are applicable. Similarly,		security considerations for [RFC7684] are applicable. Similarly,
	since this document extends the OSPFv3 E-Intra-Area-Prefix-LSA, E-		since this document extends the OSPFv3 E-Intra-Area-Prefix-LSA, E-
	Inter-Area-Prefix-LSA, E-AS-External LSA and E-NSSA-LSA, the security		Inter-Area-Prefix-LSA, E-AS-External LSA and E-NSSA-LSA, the security
	considerations for [RFC8362] are applicable. The new sub-TLVs		considerations for [RFC8362] are applicable. The new sub-TLVs
	introduced in this document are optional and do not affect the OSPF		introduced in this document are optional and do not affect the OSPF
	route computation and therefore do not affect the security aspects of		route computation and therefore do not affect the security aspects of
	OSPF protocol operations.		OSPF protocol operations. A rogue node that can inject prefix
			advertisements may use the new extensions introduced in this document
			to indicate incorrect prefix source information.
	5. IANA Considerations		5. IANA Considerations
	This document requests IANA for the allocation of the codepoints from		This document requests IANA for the allocation of the codepoints from
	the "OSPFv2 Extended Prefix TLV Sub-TLVs" registry under the "Open		the "OSPFv2 Extended Prefix TLV Sub-TLVs" registry under the "Open
	Shortest Path First v2 (OSPFv2) Parameters" registry.		Shortest Path First v2 (OSPFv2) Parameters" registry.
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Code | Description | IANA Allocation |		|Code | Description | IANA Allocation |
	| Point | | Status |		|Point| | Status |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| 4 | Prefix Source Router-ID Sub-TLV | early allocation done |		| 4 | Prefix Source OSPF Router-ID Sub-TLV| early allocation done |
	| TBD1 | Prefix Originator Sub-TLV | pending |		| TBD1| Prefix Source Router Address Sub-TLV| pending |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 3: Codepoints in OSPFv2 Extended Prefix TLV Sub-TLVs		Figure 3: Codepoints in OSPFv2 Extended Prefix TLV Sub-TLVs
	This document requests IANA for the allocation of the codepoints from		This document requests IANA for the allocation of the codepoints from
	the "OSPFv3 Extended Prefix TLV Sub-TLVs" registry under the "Open		the "OSPFv3 Extended Prefix TLV Sub-TLVs" registry under the "Open
	Shortest Path First v3 (OSPFv3) Parameters" registry.		Shortest Path First v3 (OSPFv3) Parameters" registry.
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Code | Description | IANA Allocation |		|Code | Description | IANA Allocation |
	| Point | | Status |		|Point| | Status |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| 27 | Prefix Source Router-ID Sub-TLV | early allocation done |		| 27 | Prefix Source OSPF Router-ID Sub-TLV| early allocation done |
	| TBD2 | Prefix Originator Sub-TLV | pending |		|TBD2 | Prefix Source Router Address Sub-TLV| pending |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 4: Codepoints in OSPFv3 Extended-LSA Sub-TLVs		Figure 4: Codepoints in OSPFv3 Extended-LSA Sub-TLVs
	6. Acknowledgement		6. Acknowledgement
	Many thanks to Les Ginsberg for his suggestions on this draft. Also		Many thanks to Les Ginsberg for his suggestions on this draft. Also
	thanks to Jeff Tantsura, Rob Shakir, Gunter Van De Velde, Goethals		thanks to Jeff Tantsura, Rob Shakir, Gunter Van De Velde, Goethals
	Dirk, Smita Selot, Shaofu Peng, John E Drake and Baalajee S for their		Dirk, Smita Selot, Shaofu Peng, John E Drake and Baalajee S for their
	review and valuable comments.		review and valuable comments. The authors would also like to thank
			Alvaro Retana for his detailed review and suggestions for the
			improvement of this document.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
End of changes. 31 change blocks.
	85 lines changed or deleted		95 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/