rfc9792.original.xml		rfc9792.xml
	<?xml version='1.0' encoding='US-ASCII'?>		<?xml version='1.0' encoding='UTF-8'?>
	<!DOCTYPE rfc [		<!DOCTYPE rfc [
	<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R		<!ENTITY nbsp "&#160;">
	FC.2119.xml">		<!ENTITY zwsp "&#8203;">
	<!ENTITY RFC3630 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R		<!ENTITY nbhy "&#8209;">
	FC.3630.xml">		<!ENTITY wj "&#8288;">
	<!ENTITY RFC5340 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R		]>
	FC.5340.xml">
	<!ENTITY RFC7684 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R
	FC.7684.xml">
	<!ENTITY RFC8126 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R
	FC.8126.xml">
	<!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R
	FC.8174.xml">
	<!ENTITY RFC8362 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R
	FC.8362.xml">
	<!ENTITY RFC9513 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.R
	FC.9513.xml">
	]>
	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
	<?rfc strict="no" ?>
	<?rfc toc="yes" ?>
	<?rfc symrefs="yes" ?>
	<?rfc sortrefs="yes"?>
	<?rfc rfcedstyle="yes" ?>		<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902"
	<?rfc subcompact="no" ?>		docName="draft-ietf-lsr-ospf-prefix-extended-flags-07" number="9792" updates=""
			obsoletes="" consensus="true" submissionType="IETF" version="3" symRefs="true"
			sortRefs="true" xml:lang="en" tocInclude="true">
	<rfc category="std" ipr="trust200902" docName="draft-ietf-lsr-ospf-prefix-extend
	ed-flags-07"
	consensus="true" submissionType="IETF" version="3">
	<front>		<front>
	<!-- The abbreviated title is used in the page header - it is only necessary
	if the
	full title is longer than 39 characters -->
	<title abbrev="Prefix Flag Extension for OSPF">Prefix Flag Extension for OSPF v2 and OSPFv3</title>		<title abbrev="Prefix Flag Extension for OSPF">Prefix Flag Extension for OSPF v2 and OSPFv3</title>
	<seriesInfo name="Internet-Draft" value="draft-ietf-lsr-ospf-prefix-extended		<seriesInfo name="RFC" value="9792"/>
	-flags-07"/>		<author initials='R.' surname="Chen" fullname='Ran Chen'>
	<!-- add 'role="editor"' below for the editors if appropriate -->		<organization>ZTE Corporation</organization>
	<!-- Another author who claims to be an editor -->
	<author initials='R.' surname="Chen" fullname='Ran Chen'>
	<organization>ZTE Corporation</organization>
	<address>		<address>
	<postal>		<postal>
	<street/>		<city>Nanjing</city>
	<!-- Reorder these if your country does things differently -->
	<city>Nanjing</city>
	<region/>
	<code/>
	<country>China</country>		<country>China</country>
	</postal>		</postal>
	<email>chen.ran@zte.com.cn</email>		<email>chen.ran@zte.com.cn</email>
	<!-- uri and facsimile elements may also be added -->
	</address>		</address>
	</author>		</author>
	<author initials='D.' surname="Zhao" fullname='Detao Zhao'>		<author initials='D.' surname="Zhao" fullname='Detao Zhao'>
	<organization>ZTE Corporation</organization>		<organization>ZTE Corporation</organization>
	<address>		<address>
	<postal>		<postal>
	<street/>		<city>Nanjing</city>
	<!-- Reorder these if your country does things differently -->
	<city>Nanjing</city>
	<region/>
	<code/>
	<country>China</country>		<country>China</country>
	</postal>		</postal>
	<email>zhao.detao@zte.com.cn</email>		<email>zhao.detao@zte.com.cn</email>
	<!-- uri and facsimile elements may also be added -->
	</address>		</address>
	</author>		</author>
	<author initials='P.' surname="Psenak" fullname='Peter Psenak'>		<author initials='P.' surname="Psenak" fullname='Peter Psenak'>
	<organization>Cisco Systems</organization>		<organization>Cisco Systems</organization>
	<address>		<address>
	<postal>		<postal>
	<street>Apollo Business Center</street>		<street>Apollo Business Center</street>
	<street>Mlynske nivy 43</street>		<street>Mlynske nivy 43</street>
	<city>Bratislava 821 09</city>		<city>Bratislava</city>
	<country>Slovakia</country>		<code>821 09</code>
	<code></code>		<country>Slovakia</country>
	</postal>		</postal>
	<email>ppsenak@cisco.com</email>		<email>ppsenak@cisco.com</email>
	</address>		</address>
	</author>		</author>
	<author initials='K.' surname="Talaulikar" fullname='Ketan Talaulikar'>		<author initials='K.' surname="Talaulikar" fullname='Ketan Talaulikar'>
	<organization>Cisco Systems</organization>		<organization>Cisco Systems</organization>
	<address>		<address>
	<postal>		<postal>
	<street/>
	<!-- Reorder these if your country does things differently -->
	<city/>
	<region/>
	<code/>
	<country>India</country>		<country>India</country>
	</postal>		</postal>
	<email>ketant.ietf@gmail.com</email>		<email>ketant.ietf@gmail.com</email>
	<!-- uri and facsimile elements may also be added -->
	</address>		</address>
	</author>		</author>
	<author initials='L.' surname="Gong" fullname='Liyan Gong'>		<author initials='L.' surname="Gong" fullname='Liyan Gong'>
	<organization>China mobile</organization>		<organization>China mobile</organization>
	<address>		<address>
	<postal>		<postal>
	<street/>
	<!-- Reorder these if your country does things differently -->
	<city/>
	<region/>
	<code/>
	<country>China</country>		<country>China</country>
	</postal>		</postal>
	<email>gongliyan@chinamobile.com</email>		<email>gongliyan@chinamobile.com</email>
	<!-- uri and facsimile elements may also be added -->
	</address>		</address>
	</author>		</author>
	<date year="2025"/>		<date year="2025" month="May"/>
	<!-- If the month and year are both specified and are the current ones, xml2
	rfc will fill
	in the current day for you. If only the current year is specified, xml2r
	fc will fill
	in the current day and month for you. If the year is not the current one, i
	t is
	necessary to specify at least a month (xml2rfc assumes day="1" if not speci
	fied for the
	purpose of calculating the expiry date). With drafts it is normally suffic
	ient to
	specify just the year. -->
	<!-- Meta-data Declarations -->
	<area>Routing</area>
	<workgroup>LSR</workgroup>
	<!-- WG name at the upperleft corner of the doc,
	IETF is fine for individual submissions.
	If this element is not present, the default is "Network Working Group",
	which is used by the RFC Editor as a nod to the history of the IETF. -->
	<keyword>Internet Draft</keyword>		<area>RTG</area>
	<!-- Keywords will be incorporated into HTML output		<workgroup>lsr</workgroup>
	files in a meta tag but they have no effect on text or nroff
	output. If you submit your draft to the RFC Editor, the
	keywords will be used for the search engine. -->
	<abstract>		<abstract>
	<t>Each OSPF prefix can be advertised with an 8-bit field to indicate spec		<t>Each OSPF prefix can be advertised with an 8-bit field to indicate spec
	ific properties of that prefix. However, all the OSPFv3 Prefix Options bits have		ific properties of that prefix. However, all the OSPFv3 Prefix Options bits have
	already been assigned and only a few bits remain unassigned in the flags field		already been assigned, and only a few bits remain unassigned in the Flags field
	of the OSPFv2 Extended Prefix TLV.</t>		of the OSPFv2 Extended Prefix TLV.</t>
	<t>This document solves this problem by defining variable-length Prefix At		<t>This document solves this problem by defining a variable-length Prefix
	tribute Flags sub-TLV for OSPF. This sub-TLV is applicable to OSPFv2 and OSPFv3.		Attribute Flags sub-TLV for OSPF. This sub-TLV is applicable to OSPFv2 and OSPFv
	</t>		3.</t>
	</abstract>		</abstract>
	</front>		</front>
	<middle>		<middle>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>Introduction</name>		<name>Introduction</name>
	<t>Each OSPF prefix can be advertised with an 8-bit field to indicate spec		<t>Each OSPF prefix can be advertised with an 8-bit field to indicate spec
	ific properties of that prefix. This is done using the OSPFv3 Prefix Options (Ap		ific properties of that prefix. This is done using the OSPFv3 Prefix Options (<x
	pendix A.4.1.1 of <xref target="RFC5340" format="default"></xref>) and the flags		ref section="A.4.1.1" target="RFC5340" format="default"></xref>) and the Flags f
	field in the OSPFv2 Extended Prefix TLV (Section 2.1 of <xref target="RFC7684"		ield in the OSPFv2 Extended Prefix TLV (<xref target="RFC7684" sectionFormat="of
	format="default"></xref>). The rest of this document refers to these 8-bit field		" section="2.1"/>). The rest of this document refers to these 8-bit fields in bo
	s in both OSPFv2 and OSPFv3 as the "existing fixed-size prefix attribute flags".		th OSPFv2 and OSPFv3 as the "existing fixed-size prefix attribute flags".</t>
	</t>		<t>However, all the OSPFv3 Prefix Options bits have already been assigned
	<t>However, all the OSPFv3 Prefix Options bits have already been assigned		(see the "OSPFv3 Prefix Options (8 bits)" IANA registry <xref target="IANA-OSPFv
	(see "OSPFv3 Prefix Options (8 bits)" IANA registry <xref target="IANA-OSPFv3-P		3-PO"/>). Also, at the time of publication of this document, only 5 bits remain
	O"/>). Also, only 5 bits remain unassigned (at the time of publication of this d		unassigned in the Flags field of the OSPFv2 Extended Prefix TLV (see the "OSPFv2
	ocument) in the Flags field of the OSPFv2 Extended Prefix TLV (see "OSPFv2 Exten		Extended Prefix TLV Flags" IANA registry <xref target="IANA-OSPFv2-EPF"/>).</t>
	ded Prefix TLV Flags" IANA registry <xref target="IANA-OSPFv2-EPF"/>).</t>		<t>This document solves the problem of insufficient flag bits for the sign
	<t>This document solves the problem of insufficient flag bits for the sign		aling of prefix properties in OSPF by defining a variable-length Prefix Attribut
	aling of prefix properties in OSPF by defining variable-length Prefix Attribute		e Flags sub-TLV for OSPFv2 and OSPFv3.</t>
	Flags sub-TLVs for OSPFv2 and OSPFv3.</t>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>Requirements Language</name>		<name>Requirements Language</name>
	<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "		<t>
	SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" i		The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
	n this document are to be interpreted as described in BCP 14 <xref target="RFC21		IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
	19" format="default"></xref> <xref target="RFC8174" format="default"></xref> whe		NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
	n, and only when, they appear in all capitals, as shown here.</t>		RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
			"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
			be interpreted as
			described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/>
			when, and only when, they appear in all capitals, as shown here.
			</t>
	</section>		</section>
	</section>		</section>
	<section numbered="true" toc="default">		<section numbered="true" toc="default" anchor="vlpafsf">
	<name>Variable-Length Prefix Attribute Flags Sub-TLV</name>		<name>Variable-Length Prefix Attribute Flags Sub-TLV</name>
	<t>This document defines variable-Length Prefix Attribute Flags sub-TLV for O		<t>This document defines a variable-length Prefix Attribute Flags sub-TLV for
	SPFv2 and OSPFv3. Such sub-TLV specifies the variable-flag fields to advertise a		OSPFv2 and OSPFv3. The sub-TLV specifies the variable-length Prefix Attribute F
	dditional attributes associated with OSPF prefixes. The advertisement and proces		lags field to advertise additional attributes associated with OSPF prefixes. The
	sing of the existing fixed-size prefix attribute flags remain unchanged.</t>		advertisement and processing of the existing fixed-size prefix attribute flags
	<t>The format of OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLVs is shown in Fi		remain unchanged.</t>
	gure 1.</t>		<t>The format of the OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLV is shown in
	<figure title="Format of OSPFv2/OSPFv3 Prefix Attribute Flags Sub-TLV">		Figure 1.</t>
	<artwork>		<figure>
	<![CDATA[		<name>Format of OSPFv2/OSPFv3 Prefix Attribute Flags Sub-TLV</name>
			<artwork><![CDATA[
	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 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	// Prefix Attribute Flags (Variable) //		// Prefix Attribute Flags (Variable) //
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
	]]></artwork>
	</figure>		</figure>
	<t>where:</t>		<t>where:</t>
	<t>Type (2 octets): 11 for OSPFv2 and 37 for OSPFv3.</t>		<dl spacing="normal" newline="false">
	<t>Length (2 octets): Variable, dependent on the included Prefix Attribute		<dt>Type (2 octets):</dt>
	Flags. This indicates the length of the prefix attributes flags in octets. The		<dd>11 for OSPFv2 and 37 for OSPFv3</dd>
	length MUST be a multiple of 4 octets. If the length is not a multiple of 4 octe		<dt>Length (2 octets):</dt>
	ts, the Link State Advertisement (LSA) is malformed and MUST be ignored.</t>		<dd>Variable, dependent on the included Prefix Attribute Flags field. Thi
	<t>Prefix Attribute Flags (Variable): The extended flag field. This field		s
	contains a variable number of flags, grouped in 4-octet blocks. The bits are num		indicates the length of the Prefix Attribute Flags field in octets. The
	bered starting from bit 0 as the most significant bit of the first 32-bit block.		length <bcp14>MUST</bcp14> be a multiple of 4 octets. If the length is
	If a Prefix Attribute Flags field's length exceeds 4 octets, numbering for the		not a multiple of 4 octets, the Link State Advertisement (LSA) is
	additional bits picks up where the previous 4-octet block left off. For example,		malformed and <bcp14>MUST</bcp14> be ignored.</dd>
	the most significant bit in the fifth octet of an 8-octet Prefix Attribute Flag		<dt>Prefix Attribute Flags (Variable):</dt>
	s is referred to as bit 32. Currently, no bits are defined in this document.</t>		<dd>The extended flag field. This field contains a variable number of
	<t>Unassigned bits MUST be set to zero on transmission and MUST be ignored		flags, grouped in 4-octet blocks. The bits are numbered starting from
	on receipt.</t>		bit 0 as the most significant bit of the first 32-bit block. If the lengt
	<t>An implementation MUST limit the length of the sub-TLV so as to signal		h of the
	the bits that are set to 1. Defined prefix flags that are not transmitted due to		Prefix Attribute Flags field exceeds 4 octets, numbering for
	being beyond the transmitted length MUST be treated as being set to 0.</t>		the additional bits picks up where the previous 4-octet block left
	<t>OSPFv2 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of the		off. For example, the most significant bit in the fifth octet of an
	OSPFv2 Extended Prefix TLV defined in <xref target="RFC7684"/>. Additional OSPF		8-octet Prefix Attribute Flags field is referred to as bit 32. Currently,
	v2 prefix flags SHOULD be allocated from the unused bits in the Flags field of t		no
	he OSPFv2 Extended Prefix TLV prior to allocating flags in the OSPFv2 Prefix Att		bits are defined in this document.</dd>
	ribute Flags sub-TLV.</t>		</dl>
	<t>OSPFv3 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of the		<t>Unassigned bits <bcp14>MUST</bcp14> be set to zero on transmission and
	following OSPFv3 TLVs:</t>		<bcp14>MUST</bcp14> be ignored on receipt.</t>
			<t>An implementation <bcp14>MUST</bcp14> limit the length of the sub-TLV s
			o as to signal the bits that are set to 1. Defined prefix flags that are not tra
			nsmitted due to being beyond the transmitted length <bcp14>MUST</bcp14> be treat
			ed as being set to 0.</t>
			<t>The OSPFv2 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of
			the OSPFv2 Extended Prefix TLV defined in <xref target="RFC7684"/>. Additional
			OSPFv2 prefix flags <bcp14>SHOULD</bcp14> be allocated from the unused bits in t
			he Flags field of the OSPFv2 Extended Prefix TLV prior to allocating flags in th
			e OSPFv2 Prefix Attribute Flags sub-TLV.</t>
			<t>The OSPFv3 Prefix Attribute Flags sub-TLV is advertised as a sub-TLV of
			the following OSPFv3 TLVs:</t>
	<ul spacing="normal">		<ul spacing="normal">
	<li>Inter-Area-Prefix TLV (Section 3.4 of <xref target="RFC8362"/>).</li		<li>Inter-Area-Prefix TLV (<xref target="RFC8362" sectionFormat="of" sec
	>		tion="3.4"/>)</li>
	<li>External-Prefix TLV (Section 3.6 of <xref target="RFC8362"/>).</li>		<li>External-Prefix TLV (<xref target="RFC8362" sectionFormat="of" secti
	<li>Intra-Area-Prefix TLV (Section 3.7 of <xref target="RFC8362"/>).</li		on="3.6"/>)</li>
	>		<li>Intra-Area-Prefix TLV (<xref target="RFC8362" sectionFormat="of" sec
	<li>SRv6 Locator TLV <xref target="RFC9513"/>.</li>		tion="3.7"/>)</li>
			<li>SRv6 Locator TLV <xref target="RFC9513"/></li>
	</ul>		</ul>
	<t>When multiple instances of the OSPFv2/OSPFv3 Prefix Attribute Flags sub- TLVs are received within the same TLV, an implementation MUST use only the first occurrence of the sub-TLV and MUST ignore all subsequent instances of the sub-T LV. Errors SHOULD be logged subject to rate limiting.</t>		<t>When multiple instances of the OSPFv2/OSPFv3 Prefix Attribute Flags sub- TLVs are received within the same TLV, an implementation <bcp14>MUST</bcp14> use only the first occurrence of the sub-TLV and <bcp14>MUST</bcp14> ignore all sub sequent instances of the sub-TLV. Errors <bcp14>SHOULD</bcp14> be logged subject to rate limiting.</t>
	</section>		</section>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>Backward Compatibility</name>		<name>Backward Compatibility</name>
	<t>The Prefix Attribute Flags sub-TLV does not introduce any backward co mpatibility issues. An implementation that does not recognize the OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLV would ignore the sub-TLV as per normal TLV proces sing operations (refer Section 6.3 of <xref target="RFC3630"/> and Section 2.3.2 of <xref target="RFC8362"/>).</t>		<t>The OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLV does not introduce a ny backward compatibility issues. An implementation that does not recognize the OSPFv2/OSPFv3 Prefix Attribute Flags sub-TLV would ignore the sub-TLV as per nor mal TLV processing operations (refer to <xref target="RFC3630" sectionFormat="of " section="2.3.2"/> and <xref target="RFC8362" sectionFormat="of" section="6.3"/ >).</t>
	</section>		</section>
	<section anchor="Acknowledgements" numbered="true" toc="default">
	<name>Acknowledgements</name>
	<t>The authors thank Shraddha Hegde, Changwang Lin, Tom Petch and many oth
	ers for their suggestions and comments.</t>
	<t>The authors would like to thank Acee Lindem for aligning the terminolog
	y with existing OSPF documents and for editorial improvements.</t>
	</section>
	<!-- Possibly a 'Contributors' section ... -->
	<section anchor="IANA" numbered="true" toc="default">		<section anchor="IANA" numbered="true" toc="default">
	<name>IANA Considerations</name>		<name>IANA Considerations</name>
	<t>This document requests allocation for the following registries.</t>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>OSPFv2</name>		<name>OSPFv2</name>
	<section numbered="true" toc="default">		<!-- [rfced] We have included some specific questions about the IANA
	<name>OSPFv2 Prefix Attribute Flags Sub-TLV Registry</name>		text below. In addition to responding to those questions, please
	<t>This document requests IANA to make permanent the early allocation of the		review all of the IANA-related updates carefully and let us know
	following codepoint for the "OSPFv2 Prefix Attribute Flags" in the "OSPFv2 Exten		if any further updates are needed.
	ded Prefix TLV Sub-TLVs" registry to be made permanent:</t>
	<artwork align="center" name=" " type="" alt="">		a) We see the following note from IANA. Please confirm if the additional
	<![CDATA[		sentence has been added or if it still needs to be added.
	Value Description Reference
	11 OSPFv2 Prefix Attribute Flags RFC to be		NOTE: The authors plan to upload an -08 that will include
	]]></artwork>		an additional sentence in the IANA Considerations section.
	</section>
			b) Should the titles of the new registries created by this document
			be updated to use "Flags" rather than "Flag Field"? We ask because that
			seems to be the pattern with other registry titles within both of the
			registry groups (see links below).
			Also, the name of the field in Figure 1 of this document is "Prefix Attribute
			Flags". Should the titles of the registries be updated further to use
			"Prefix Attribute" rather than "Prefix Extended"? Or is this okay?
			If the titles are updated, we will ask IANA to update the registries
			accordingly.
			https://www.iana.org/assignments/ospfv2-parameters/
			https://www.iana.org/assignments/ospfv3-parameters/
			Current:
			OSPFv2 Prefix Extended Flag Field
			OSPFv3 Prefix Extended Flag Field
			Perhaps A:
			OSPFv2 Prefix Extended Flags
			OSPFv3 Prefix Extended Flags
			or
			Perhaps B:
			OSPFv2 Prefix Attribute Flags
			OSPFv3 Prefix Attribute Flags
			[RFC-EDITOR NOTE]: IANA Actions needed
			-->
			<section numbered="true" toc="default">
			<name>OSPFv2 Prefix Attribute Flags Sub-TLV</name>
			<t>IANA has allocated the following codepoint in the "OSPFv2 Extended Prefix
			TLV Sub-TLVs" registry:</t>
			<table>
			<thead>
			<tr><th>Value</th><th>Description</th><th>Reference</th></tr>
			</thead>
			<tbody>
			<tr><td>11</td><td>OSPFv2 Prefix Attribute Flags</td><td>RFC 9792</td></t
			r>
			</tbody>
			</table>
			</section>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>OSPFv2 Prefix Extended Flags Field Registry</name>		<name>OSPFv2 Prefix Attribute Flags Registry</name>
	<t>This document requests the creation of "OSPFv2 Prefix Extended Flag Fie		<t>IANA has created the "OSPFv2 Prefix Attribute Flags" registry within th
	ld" Registry under "Open Shortest Path First v2 (OSPFv2) Parameters" registry gr		e "Open Shortest Path First v2 (OSPFv2) Parameters" registry group. The registry
	oup. The registry defines the bits in the Prefix Attribute Flags field in the OS		defines the bits in the Prefix Attribute Flags field in the OSPFv2 Prefix Attri
	PFv2 Prefix Attribute Flags sub-TLV as specified in Section 2. The bits are to b		bute Flags sub-TLV as specified in <xref target="vlpafsf"/>. The bits are to be
	e allocated via IETF Review <xref target="RFC8126"/>. Each bit definition will i		allocated via IETF Review <xref target="RFC8126"/>. Each bit definition will inc
	nclude:</t>		lude:</t>
	<artwork align="center" name=" " type="" alt="">		<ul spacing="normal">
	<![CDATA[		<li>Bit number (counting from bit 0 as the most significant bit of the fi
	* Bit number (counting from bit 0 as the most significant		rst block)</li>
	bit of the first block)		<li>Description</li>
	* Description		<li>Reference</li>
	* Reference		</ul>
	]]></artwork>
	<t>No bits are currently defined. Bits 0-31 are to be initially marked as		<t>No bits are currently defined. Bits 0-31 are to be initially marked as
	"Unassigned". The flags defined in this document may use either a single bit or		"Unassigned". The flags defined in this document may use either a single bit or
	multiple bits to represent a state, as determined by the specific requirements		multiple bits to represent a state, as determined by the specific requirements
	of the document defining them. IANA is requested to add subsequent blocks of 32		of the document defining them. IANA will add subsequent blocks of 32 bits upon e
	bits upon exhaustion of the preceding 32-bit block.</t>		xhaustion of the preceding 32-bit block.</t>
	</section>		</section>
	</section>		</section>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>OSPFv3</name>		<name>OSPFv3</name>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>OSPFv3 Prefix Attribute Flags Sub-TLV Registry</name>		<name>OSPFv3 Prefix Attribute Flags Sub-TLV</name>
	<t>This document requests IANA to make permanent the early allocation of		<t>IANA has allocated the following codepoint in the "OSPFv3 Extended-LS
	the following codepoint for the "OSPFv3 Prefix Attribute Flags" in the "OSPFv3		A Sub-TLVs" registry:</t>
	Extended-LSA sub-TLVs" registry:</t>
	<artwork align="center" name=" " type="" alt="">		<table>
	<![CDATA[		<thead><tr><th>Value</th><th>Description</th><th>Reference</th></tr></t
	Value Description Reference		head>
	37 OSPFv3 Prefix Attribute Flags RFC to be		<tbody><tr><td>37</td><td>OSPFv3 Prefix Attribute Flags</td><td>RFC 979
	]]></artwork>		2</td></tr></tbody>
	</section>		</table>
			<t>The entry in the "L2BM" field is "X".</t>
			</section>
	<section numbered="true" toc="default">		<section numbered="true" toc="default">
	<name>OSPFv3 Prefix Extended Flags Field Registry</name>		<name>OSPFv3 Prefix Attribute Flags Registry</name>
	<t>This document requests the creation of "OSPFv3 Prefix Extended Flag Fie		<t>IANA has created the "OSPFv3 Prefix Attribute Flags" registry within th
	ld" registry under "Open Shortest Path First v3 (OSPFv3)" registry group. The re		e "Open Shortest Path First v3 (OSPFv3) Parameters" registry group. The registry
	gistry defines the bits in the Prefix Attribute Flags field in the OSPFv2 Prefix		defines the bits in the Prefix Attribute Flags field in the OSPFv2 Prefix Attri
	Attribute Flags sub-TLV as specified in Section 2. The bits are to be allocated		bute Flags sub-TLV as specified in <xref target="vlpafsf"/>. The bits are to be
	via IETF Review <xref target="RFC8126"/>. Each bit definition will include:</t>		allocated via IETF Review <xref target="RFC8126"/>. Each bit definition will inc
	<artwork align="center" name=" " type="" alt="">		lude:</t>
	<![CDATA[		<ul spacing="normal">
	* Bit number (counting from bit 0 as the most significant		<li>Bit number (counting from bit 0 as the most significant bit of the fi
	bit of the first block )		rst block)</li>
	* Description		<li>Description</li>
	* Reference		<li>Reference</li>
	]]></artwork>		</ul>
	<t>No bits are currently defined. Bits 0-31 are to be initially marked as		<t>No bits are currently defined. Bits 0-31 are to be initially marked as
	"Unassigned". The flags defined in this document may use either a single bit or		"Unassigned". The flags defined in this document may use either a single bit or
	multiple bits to represent a state, as determined by the specific requirements		multiple bits to represent a state, as determined by the specific requirements
	of the document defining them. IANA is requested to add subsequent blocks of 32		of the document defining them. IANA will add subsequent blocks of 32 bits upon e
	bits upon exhaustion of the preceding 32-bit block. </t>		xhaustion of the preceding 32-bit block. </t>
	</section>		</section>
	</section>		</section>
	</section>		</section>
	<section anchor="Security" numbered="true" toc="default">		<section anchor="Security" numbered="true" toc="default">
	<name>Security Considerations</name>		<name>Security Considerations</name>
	<t>Procedures and protocol extensions defined in this document do not affec t the OSPFv2 or OSPFv3 security models. See the "Security Considerations" Sectio n of <xref target="RFC7684" format="default"></xref> for a discussion of OSPFv2 TLV-encoding considerations, and the "Security Considerations" Section of <xref target="RFC8362" format="default"></xref> for a discussion of OSPFv3 security.</ t>		<t>Procedures and protocol extensions defined in this document do not affec t the OSPFv2 or OSPFv3 security models. See <xref target="RFC7684" sectionForma t="of" section="5"/> for a discussion of OSPFv2 TLV-encoding considerations and <xref target="RFC8362" sectionFormat="of" section="7"/> for a discussion of OSPF v3 security.</t>
	</section>		</section>
	</middle>		</middle>
	<!-- *****BACK MATTER ***** -->
	<back>		<back>
	<references>		<references>
	<name>References</name>		<name>References</name>
	<references>		<references>
	<name>Normative References</name>		<name>Normative References</name>
	&RFC2119;		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.211
	&RFC3630;		9.xml"/>
	&RFC5340;		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.363
	&RFC7684;		0.xml"/>
	&RFC8126;		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.534
	&RFC8174;		0.xml"/>
	&RFC8362;		<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.768
	&RFC9513;		4.xml"/>
			<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.812
			6.xml"/>
			<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.817
			4.xml"/>
			<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.836
			2.xml"/>
			<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.951
			3.xml"/>
	</references>		</references>
	<references>		<references>
	<name>Informative References</name>		<name>Informative References</name>
	<reference anchor="IANA-OSPFv2-EPF" target="https://www.iana.org/assign ments/ospfv2-parameters/ospfv2-parameters.xhtml#extended-prefix-tlv-flags">		<reference anchor="IANA-OSPFv2-EPF" target="https://www.iana.org/assign ments/ospfv2-parameters">
	<front>		<front>
	<title>OSPFv2 Extended Prefix TLV Flags</title>		<title>OSPFv2 Extended Prefix TLV Flags</title>
	<author>		<author>
	<organization></organization>		<organization>IANA</organization>
	</author>		</author>
	</front>		</front>
	</reference>		</reference>
	<reference anchor="IANA-OSPFv3-PO" target="https://www.iana.org/assignm
	ents/ospfv3-parameters/ospfv3-parameters.xhtml#ospfv3-parameters-4">		<reference anchor="IANA-OSPFv3-PO" target="https://www.iana.org/assignm
			ents/ospfv3-parameters">
	<front>		<front>
	<title>OSPFv3 Prefix Options (8 bits)</title>		<title>OSPFv3 Prefix Options (8 bits)</title>
	<author>		<author>
	<organization></organization>		<organization>IANA</organization>
	</author>		</author>
	</front>		</front>
	</reference>		</reference>
	</references>		</references>
	</references>		</references>
			<section anchor="Acknowledgements" numbered="false" toc="default">
			<name>Acknowledgements</name>
			<t>The authors would like to thank <contact fullname="Shraddha Hegde"/>, <
			contact fullname="Changwang Lin"/>, <contact fullname="Tom Petch"/>, and many ot
			hers for their suggestions and comments.</t>
			<t>The authors would also like to thank <contact fullname="Acee Lindem"/>
			for aligning the terminology with existing OSPF documents and for editorial impr
			ovements.</t>
			</section>
	</back>		</back>
	</rfc>		</rfc>
End of changes. 43 change blocks.
	264 lines changed or deleted		263 lines changed or added
This html diff was produced by rfcdiff 1.48.