rfc9927.original.xml   rfc9927.xml 
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!--DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"-->
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc authorship="yes"?>
<?rfc tocappendix="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902
"
tocInclude="true" indexInclude="true" obsoletes="" consensus="true"
submissionType="IETF" xml:lang="en" version="3" updates="8928" docName="draft-i
etf-6lo-updating-rfc-8928-05" >
<front> <!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<title abbrev="RFC 8928-Fix">Fixing the C-Flag in Extended Address Registrati <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" ipr="trust200902"
on Option (EARO)</title> tocInclude="true" indexInclude="true" obsoletes="" consensus="true" submissionT
<!-- <title abbrev="EARO Flags Field Fix">Fixing the Extended Address Reg ype="IETF" xml:lang="en" version="3" updates="8928" docName="draft-ietf-6lo-upda
istration Option (EARO) Flags Field</title> --> ting-rfc-8928-05" number="9927" symRefs="true" sortRefs="true">
<front>
<title abbrev="RFC 8928-Fix">Fixing the C-Flag in the Extended Address Regist
ration Option (EARO)</title>
<seriesInfo name="RFC" value="9927"/>
<author initials='P' surname='Thubert' fullname='Pascal Thubert' > <author initials='P' surname='Thubert' fullname='Pascal Thubert' >
<!-- <organization abbrev='Cisco Systems'>Cisco Systems, Inc</organization > -->
<address> <address>
<postal> <postal>
<city>Roquefort-les-Pins</city> <city>Roquefort-les-Pins</city>
<code>06330</code> <code>06330</code>
<country>France</country> <country>France</country>
</postal> </postal>
<email>pascal.thubert@gmail.com</email> <email>pascal.thubert@gmail.com</email>
</address> </address>
</author> </author>
skipping to change at line 49 skipping to change at line 38
<address> <address>
<postal> <postal>
<street>Via Edoardo Orabona 4</street> <street>Via Edoardo Orabona 4</street>
<city>Bari</city> <city>Bari</city>
<code>70126</code> <code>70126</code>
<country>Italy</country> <country>Italy</country>
</postal> </postal>
<email>adnan.rashid@poliba.it</email> <email>adnan.rashid@poliba.it</email>
</address> </address>
</author> </author>
<date year="2026" month="January"/>
<area>Internet</area> <area>INT</area>
<workgroup>6lo</workgroup> <workgroup>6lo</workgroup>
<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on https://www.rfc-editor.org/search. -->
<keyword>example</keyword>
<!-- [rfced] Some author comments are present in the XML. Please confirm
that no updates related to these comments are outstanding. Note that
the comments will be deleted prior to publication.
-->
<abstract> <abstract>
<!-- <t>This document updates RFC 8928 by changing the position for the C-fla g in the Extended Address Registration Option (EARO) and registering it with IAN A. <!-- <t>This document updates RFC 8928 by changing the position for the C-fla g in the Extended Address Registration Option (EARO) and registering it with IAN A.
It also requests IANA to add a 2-bit integer for the I-Field in the "Addre ss Registration Option Flags" registry under ICMPv6 Parameters, as defined in RF C 8505. --> It also requests IANA to add a 2-bit integer for the I-Field in the "Addre ss Registration Option Flags" registry under ICMPv6 Parameters, as defined in RF C 8505. -->
<t> <t>This document updates "Address-Protected Neighbor Discovery for
This document updates “Address-Protected Neighbor Discovery for Low-Power Low-Power and Lossy Networks" (RFC 8928) by changing the position of the
and Lossy Networks” (RFC 8928) by changing the position of the C-flag in the Ext C-flag in the Extended Address Registration Option (EARO) and registering
ended Address Registration Option (EARO) and it with IANA.</t>
registering it with IANA. <!-- The document also registers the I-Field, initially defined in "Registrat
<!-- The document also registers the I-Field, initially defined in “Registrat ion Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN)
ion Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery" (RFC 8505),
Neighbor Discovery” (RFC 8505), in the "Address Registration Option Flags" registry under the "ICMPv6 Paramet
in the "Address Registration Option Flags" registry under the “ICMPv6 Paramet ers" registry group. -->
ers” registry group. -->
</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<!-- **************************************************************** -->
<!-- **************************************************************** -->
<!-- **************************************************************** -->
<!-- **************************************************************** -->
<section anchor="introduction"> <name>Introduction</name> <section anchor="introduction"> <name>Introduction</name>
<t>The <xref target="RFC8928"> Address-Protected Neighbor Discovery <t>The <xref target="RFC8928"> Address-Protected Neighbor Discovery
for Low-Power and Lossy Networks (AP-ND)</xref> defined the C-flag in EARO. I t is used to indicate that the Registration Ownership Verifier (ROVR) field cont ains for Low-Power and Lossy Networks (AP-ND)</xref> defined the C-flag in EARO. I t is used to indicate that the Registration Ownership Verifier (ROVR) field cont ains
a Crypto-ID and that the 6LoWPAN Node (6LN) may be challenged for ownership o a Crypto-ID and that the 6LoWPAN Node (6LN) may be challenged for ownership o
f the registered address. Initially <xref target="RFC8928"/> defined the C-flag f the registered address. Initially, <xref target="RFC8928"/> defined the C-flag
in the EARO in bit position 3; later <xref target="RFC9685"/> defined the P-Fiel in the EARO in bit position 3; later, <xref target="RFC9685"/> defined the P-Fi
d in bits 2 and 3 of the eld in bits 2 and 3 of the
EARO flags field with proper IANA registration, causing an overlap with Figu EARO flags field with proper IANA registration, causing an overlap with Figu
re 1 of <xref target="RFC8928"/> which depicts the location of the C-flag.</t> re 1 of <xref target="RFC8928"/>, which depicts the location of the C-flag.</t>
<t>This specification updates <xref target="RFC8928"/> by repositioning the C -flag as bit 1 of the EARO flags field, thereby preventing conflicts.</t> <t>This specification updates <xref target="RFC8928"/> by repositioning the C -flag as bit 1 of the EARO flags field, thereby preventing conflicts.</t>
</section> <!-- end section = "Introduction" --> </section>
<section> <name>Terminology</name> <section> <name>Terminology</name>
<section anchor="bcp"><name>Requirements Language</name> <section anchor="bcp"><name>Requirements Language</name>
<t> <t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and ",
"OPTIONAL" in this document are to be interpreted as described in BCP 14 "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
<xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
they appear in all capitals, as shown here. "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be
</t> 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 anchor="lo"><name>References</name> <section anchor="lo"><name>Terminology</name>
<t> <t>
This document uses terms and concepts that are discussed in IPv6-Neighbor Discovery (ND) This document uses terms and concepts that are discussed in IPv6 Neighbor Discovery (ND)
<xref target="RFC4861"/>, <xref target="RFC4862"/>, as well as 6LoWPAN-ND <xref target="RFC4861"/>, <xref target="RFC4862"/>, as well as 6LoWPAN-ND
<xref target="RFC6775"/>, <xref target="RFC8505"/>, <xref target="RFC6775"/>, <xref target="RFC8505"/>,
<xref target="RFC8928"/>, <xref target="RFC8929"/>, <xref target="RFC8928"/>, <xref target="RFC8929"/>,
<xref target="RFC9685"/>, and <xref target="I-D.ietf-6lo-prefix-registration" />. <xref target="RFC9685"/>, and <xref target="RFC9926"/>.
</t> </t>
</section> </section>
<section anchor='acronyms' > <name>Acronyms</name> <section anchor='acronyms' > <name>Acronyms</name>
<t>This document uses the following abbreviations:</t> <t>This document uses the following abbreviations:</t>
<dl spacing='compact'> <dl spacing='normal' newline="false">
<dt><strong>6LN:</strong></dt><dd>6LoWPAN Node</dd> <dt><strong>6LN:</strong></dt><dd>6LoWPAN Node</dd>
<!-- <dt><strong>AP-ND:</strong></dt><dd>Address-Protected Neighbor Discov ery</dd> --> <!-- <dt><strong>AP-ND:</strong></dt><dd>Address-Protected Neighbor Discov ery</dd> -->
<!-- <dt><strong>ARO:</strong></dt><dd>Address Registration Option</dd> -- > <!-- <dt><strong>ARO:</strong></dt><dd>Address Registration Option</dd> -- >
<!-- <dt><strong>DAD:</strong></dt><dd>Duplicate Address Detection</dd> -- > <!-- <dt><strong>DAD:</strong></dt><dd>Duplicate Address Detection</dd> -- >
<dt><strong>EARO:</strong></dt><dd>Extended Address Registration Option</d d> <dt><strong>EARO:</strong></dt><dd>Extended Address Registration Option</d d>
<!-- <dt><strong>LLN:</strong></dt><dd>Low-Power and Lossy Network</dd> -- > <!-- <dt><strong>LLN:</strong></dt><dd>Low-Power and Lossy Network</dd> -- >
<!-- <dt><strong>6LoWPAN:</strong></dt><dd>IPv6 over Low-power Wireless P ersonal Area Networks</dd> --> <!-- <dt><strong>6LoWPAN:</strong></dt><dd>IPv6 over Low-power Wireless P ersonal Area Networks</dd> -->
<!-- <dt><strong>LoWPAN:</strong></dt><dd>Low-Rate Wireless Personal Area Network</dd> --> <!-- <dt><strong>LoWPAN:</strong></dt><dd>Low-Rate Wireless Personal Area Network</dd> -->
<!-- <dt><strong>LR-WPAN:</strong></dt><dd>Low-Rate Wireless Personal Area Network (IEEE Std. 802.15.4) <xref target="IEEE802154"/></dd> --> <!-- <dt><strong>LR-WPAN:</strong></dt><dd>Low-Rate Wireless Personal Area Network (IEEE Std. 802.15.4) <xref target="IEEE802154"/></dd> -->
<dt><strong>ND:</strong></dt><dd>Neighbor Discovery</dd> <dt><strong>ND:</strong></dt><dd>Neighbor Discovery</dd>
skipping to change at line 147 skipping to change at line 140
In <xref target="RFC8928"/>, the C-flag is specified in the EARO flags field a t bit position 3 (as depicted in Figure 1 of <xref target="RFC8928"/>); In <xref target="RFC8928"/>, the C-flag is specified in the EARO flags field a t bit position 3 (as depicted in Figure 1 of <xref target="RFC8928"/>);
however, <xref target="RFC8928"/> fails to register its position with IANA. La ter, <xref target="RFC9685"/> defined the P-Field however, <xref target="RFC8928"/> fails to register its position with IANA. La ter, <xref target="RFC9685"/> defined the P-Field
in bits 2 and 3 of the EARO flags field and obtained proper IANA registration, but this introduced an overlap with the in bits 2 and 3 of the EARO flags field and obtained proper IANA registration, but this introduced an overlap with the
representation in <xref target="RFC8928"/>. To resolve the conflict, this spec ification updates <xref target="RFC8928"/> by repositioning representation in <xref target="RFC8928"/>. To resolve the conflict, this spec ification updates <xref target="RFC8928"/> by repositioning
the C-flag to bit 1 of the EARO flags field, ensuring there are no overlapping definitions. the C-flag to bit 1 of the EARO flags field, ensuring there are no overlapping definitions.
</t> </t>
<t> <t>
<xref target="EARO"/> replaces Figure 1 in <xref target="RFC8928"/> in the cas e of an EARO used in an NS message. <xref target="EARO"/> replaces Figure 1 in <xref target="RFC8928"/> in the cas e of an EARO used in an NS message.
</t> </t>
<figure anchor="EARO"> <figure anchor="EARO">
<name>Extended Address Registration Option (EARO) Format for use in NS message <name>Extended Address Registration Option (EARO) Format for Use in NS Message
s</name> s</name>
<artwork align="center"> <artwork align="center"><![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 |F|Prefix Length| Opaque | | Type | Length |F|Prefix Length| Opaque |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|r|C| P | I |R|T| TID | Registration Lifetime | |r|C| P | I |R|T| TID | Registration Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
... Registration Ownership Verifier (ROVR) ... ... Registration Ownership Verifier (ROVR) ...
| (64, 128, 192, or 256 bits) | | (64, 128, 192, or 256 bits) |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</artwork> </figure>
</figure><!-- end figure "EARO Option Format" --> <!-- [rfced] Regarding usage of <strong> elements in this document.
please review the occurrences and let us know if any updates needed
for consistency.
In the HTML and PDF outputs, <strong> yields bold.
In the text output, <strong> yields an asterisk before and after.
We suggest removing usage in this document because the asterisks
seem to clutter the text output in Sections 2.3 and 3.
-->
<t> <t>
-&gt;
<xref target="EARO2"/> replaces Figure 1 in <xref target="RFC8928"/> in the case of an EARO used in an NA message. The difference between the two formats is in the usage of bits 16 to 23. <xref target="EARO2"/> replaces Figure 1 in <xref target="RFC8928"/> in the case of an EARO used in an NA message. The difference between the two formats is in the usage of bits 16 to 23.
</t> </t>
<figure anchor="EARO2"> <figure anchor="EARO2">
<name>Extended Address Registration Option (EARO) Format for use in NA message <name>Extended Address Registration Option (EARO) Format for Use in NA Message
s</name> s</name>
<artwork align="center"> <artwork align="center"><![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 | r | Status | Opaque | | Type | Length | r | Status | Opaque |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|r|C| P | I |R|T| TID | Registration Lifetime | |r|C| P | I |R|T| TID | Registration Lifetime |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
... Registration Ownership Verifier (ROVR) ... ... Registration Ownership Verifier (ROVR) ...
| (64, 128, 192, or 256 bits) | | (64, 128, 192, or 256 bits) |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
</artwork> </figure>
</figure><!-- end figure "EARO Option Format" -->
<t>Option fields of interest for this specification:</t> <t>Option fields of interest for this specification:</t>
<dl> <dl spacing="normal" newline="false">
<dt><strong>Type:</strong></dt> <dt><strong>Type:</strong></dt>
<dd>33</dd> <dd>33</dd>
<dt><strong>Length:</strong></dt> <dt><strong>Length:</strong></dt>
<dd>Defined in <xref target="RFC8505"/>.</dd> <dd>Defined in <xref target="RFC8505"/></dd>
<dt><strong>F:</strong></dt> <dt><strong>F:</strong></dt>
<dd>Defined in <xref target= "I-D.ietf-6lo-prefix-registration"/></dd> <dd>Defined in <xref target= "RFC9926"/></dd>
<!-- <dd> 1-bit flag; set to 1 to indicate that the sender expects other <!-- <dd> 1-bit flag; set to 1 to indicate that the sender expects other
routers to forward packets to self when the packets are sourced routers to forward packets to self when the packets are sourced
within the registered prefix. For use in NS messages only <xref target= "I -D.ietf-6lo-prefix-registration"/>.</dd> --> within the registered prefix. For use in NS messages only <xref target= "I -D.ietf-6lo-prefix-registration"/>.</dd> -->
<dt><strong>Prefix Length</strong></dt> <dt><strong>Prefix Length</strong></dt>
<dd>Defined in <xref target= "I-D.ietf-6lo-prefix-registration"/></dd> <dd>Defined in <xref target= "RFC9926"/></dd>
<!-- <dd> 7-bit integer. This field contains a prefix length <!-- <dd> 7-bit integer. This field contains a prefix length
expressed in bits if the P-Field is set to 3 and the EARO is expressed in bits if the P-Field is set to 3 and the EARO is
placed in an NS message. In that case, the value MUST be at least placed in an NS message. In that case, the value <bcp14>MUST</bcp14> be at least
16 and at most 120. The field contains a Status if the 16 and at most 120. The field contains a Status if the
EARO is placed in an NA message regardless of the setting of the P-flag. EARO is placed in an NA message regardless of the setting of the P-flag.
In all other cases, it is reserved, so it MUST be set to 0 In all other cases, it is reserved, so it <bcp14>MUST</bcp14> be set to 0
by the sender and ignored by the receiver. For use in NS messages only <xr ef target= "I-D.ietf-6lo-prefix-registration"/>.</dd> --> by the sender and ignored by the receiver. For use in NS messages only <xr ef target= "I-D.ietf-6lo-prefix-registration"/>.</dd> -->
<dt><strong>Status:</strong></dt> <dd> 6-bit unsigned integer. <dt><strong>Status:</strong></dt> <dd> 6-bit unsigned integer.
This field is used in NA(EARO) response messages only to indicate the stat us of a registration. This field is used in NA(EARO) response messages only to indicate the stat us of a registration.
This field is defined in <xref target="RFC8505"/> and resized by <xref tar get="RFC9010"/>. This field is defined in <xref target="RFC8505"/> and resized by <xref tar get="RFC9010"/>.
The values for the Status field are available in <xref target="IANA.ICMP.A RO.STAT"/>. The values for the Status field are available in <xref target="IANA.ICMP.A RO.STAT"/>.
This field MUST be set to 0 in NS(EARO) messages unless the registration i s for a prefix, This field <bcp14>MUST</bcp14> be set to 0 in NS(EARO) messages unless the registration is for a prefix,
in which case the F-flag is set and the prefix length is provided. in which case the F-flag is set and the prefix length is provided.
</dd> </dd>
<dt><strong>Opaque:</strong></dt> <dt><strong>Opaque:</strong></dt>
<dd>Defined in <xref target="RFC8505"/></dd> <dd>Defined in <xref target="RFC8505"/></dd>
<!-- <dd> 8-bit field opaque to ND. It MUST be set to 0 when not used. Define d in <xref target="RFC8505"/>.</dd> --> <!-- <dd> 8-bit field opaque to ND. It <bcp14>MUST</bcp14> be set to 0 when n ot used. Defined in <xref target="RFC8505"/>.</dd> -->
<dt><strong>r (reserved):</strong></dt> <dt><strong>r (reserved):</strong></dt>
<dd>1-bit reserved field in NS(EARO) and NA(EARO) as depicted in <xref target ="EARO"/> and <xref target="EARO2"/>. <dd>1-bit reserved field in NS(EARO) and NA(EARO) as depicted in <xref target ="EARO"/> and <xref target="EARO2"/>.
2-bit reserved field (most significant bits of Status filed) in NA(EARO) as depicted in <xref target="EARO2"/>. 2-bit reserved field (most significant bits of Status filed) in NA(EARO) as depicted in <xref target="EARO2"/>.
All reserved field MUST be set to zero by the sender and MUST be ignored by the receiver.</dd> All reserved field <bcp14>MUST</bcp14> be set to zero by the sender and < bcp14>MUST</bcp14> be ignored by the receiver.</dd>
<dt><strong>C:</strong></dt> <dt><strong>C:</strong></dt>
<dd>1-bit flag, moved from its position in Figure 1 of <xref target="RFC8928"/ >. It is set to indicate that the ROVR field contains a Crypto-ID and that the 6 LN MAY be challenged for ownership.</dd> <dd>1-bit flag, moved from its position in Figure 1 of <xref target="RFC8928"/ >. It is set to indicate that the ROVR field contains a Crypto-ID and that the 6 LN <bcp14>MAY</bcp14> be challenged for ownership.</dd>
<dt><strong>P:</strong></dt> <dt><strong>P:</strong></dt>
<dd>2-bit field for Registered Address Type Indicator (RATInd). Indicates whet her the registered address is unicast, multicast, or anycast, or derived from th e registered unicast prefix. <dd>2-bit field for Registered Address Type Indicator (RATInd). Indicates whet her the registered address is unicast, multicast, anycast, or derived from the r egistered unicast prefix.
Used to transport the RATInd in different protocols. The values for the RATIn d field are available in <xref target="IANA.ICMP.ARO.P-FIELD"/>.</dd> Used to transport the RATInd in different protocols. The values for the RATIn d field are available in <xref target="IANA.ICMP.ARO.P-FIELD"/>.</dd>
<dt><strong>I:</strong></dt> <dt><strong>I:</strong></dt>
<dd>Defined in <xref target="RFC8505"/></dd> <dd>Defined in <xref target="RFC8505"/></dd>
<!-- <dd>2-bit integer field that helps to decide how to use the 8-bit Opaque field. <!-- <dd>2-bit integer field that helps to decide how to use the 8-bit Opaque field.
When 0, it means the Opaque field has info about the default routing path. When 0, it means the Opaque field has info about the default routing path.
Other values are reserved. Defined in <xref target="RFC8505"/>.</dd> --> Other values are reserved. Defined in <xref target="RFC8505"/>.</dd> -->
<dt><strong>R:</strong></dt> <dt><strong>R:</strong></dt>
<dd>Defined in <xref target="RFC8505"/></dd> <dd>Defined in <xref target="RFC8505"/></dd>
skipping to change at line 255 skipping to change at line 256
<!-- <dd>1-bit flag. Set if the next octet is used as a TID. Defined in <xref target="RFC8505"/>.</dd> --> <!-- <dd>1-bit flag. Set if the next octet is used as a TID. Defined in <xref target="RFC8505"/>.</dd> -->
<dt><strong>TID (Transaction ID):</strong></dt> <dt><strong>TID (Transaction ID):</strong></dt>
<dd>Defined in <xref target="RFC8505"/></dd> <dd>Defined in <xref target="RFC8505"/></dd>
<!-- <dd>8-bit unsigned integer that tracks transactions for registrations. <!-- <dd>8-bit unsigned integer that tracks transactions for registrations.
It is incremented with each new transaction and ignored unless the T-flag is set. Defined in <xref target="RFC8505"/>.</dd> --> It is incremented with each new transaction and ignored unless the T-flag is set. Defined in <xref target="RFC8505"/>.</dd> -->
<dt><strong>Registration Lifetime:</strong></dt> <dt><strong>Registration Lifetime:</strong></dt>
<dd>Defined in <xref target="RFC8505"/></dd> <dd>Defined in <xref target="RFC8505"/></dd>
<!-- <dd>16-bit integer representing the lifetime in minutes of the Registere d Address. <!-- <dd>16-bit integer representing the lifetime in minutes of the Registere d Address.
Zero indicates the registration has ended, and the associated state MUST b e removed. Defined in <xref target="RFC8505"/>.</dd> --> Zero indicates the registration has ended, and the associated state <bcp14 >MUST</bcp14> be removed. Defined in <xref target="RFC8505"/>.</dd> -->
<dt><strong>Registration Ownership Verifier (ROVR):</strong></dt> <dt><strong>Registration Ownership Verifier (ROVR):</strong></dt>
<dd>Defined in <xref target="RFC8505"/>. Variable length field, used to verify who "owns" a registered IPv6 address. <dd>Defined in <xref target="RFC8505"/>. Variable-length field used to verify who "owns" a registered IPv6 address.
When the C-flag is set, this field contains a Crypto-ID <xref target="RFC8928 "/>.</dd> When the C-flag is set, this field contains a Crypto-ID <xref target="RFC8928 "/>.</dd>
</dl> </dl>
</section> <!-- end section "Updating RFC 8928" --> </section>
<section><name>Security Considerations</name> <section><name>Security Considerations</name>
<t>This specification does not introduce any new security considerations beyo nd those already discussed in <xref target="RFC8928"/> and <xref target="RFC8505 "/>.</t> <t>This specification does not introduce any new security considerations beyo nd those already discussed in <xref target="RFC8928"/> and <xref target="RFC8505 "/>.</t>
</section> <!-- end section "Security Considerations" --> </section>
<section><name>Operational Considerations</name> <section><name>Operational Considerations</name>
<t> <t>
The updates introduced in this document are not backward compatible. However, gi ven that there are no known implementations or deployments of <xref target="RFC8 928"/>, The updates introduced in this document are not backward compatible. However, gi ven that there are no known implementations or deployments of <xref target="RFC8 928"/>,
this document do not require any transition plan. this document does not require any transition plan.
</t> </t>
</section> </section>
<section ><name>IANA Considerations</name> <section ><name>IANA Considerations</name>
<!-- <t> IANA is requested to update the "Address Registration Option Flags" <x ref target="IANA.ICMP.ARO.FLG"/> registry under the heading "Internet Control Me ssage Protocol version 6 (ICMPv6) Parameters".</t> --> <!-- <t> IANA is requested to update the "Address Registration Option Flags" <x ref target="IANA.ICMP.ARO.FLG"/> registry under the heading "Internet Control Me ssage Protocol version 6 (ICMPv6) Parameters".</t> -->
<section><name>Bit Position of the C-flag</name> <section><name>Bit Position of the C-flag</name>
<t> <t>
<!-- This specification updates the location of the C-flag introduced in <xre f target= <!-- This specification updates the location of the C-flag introduced in <xre f target=
"RFC8928"/> to position it as bit 1 in the EARO flags field. --> "RFC8928"/> to position it as bit 1 in the EARO flags field. -->
IANA is requested to reference this RFC in addition to <xref target="RFC8928" IANA has updated the "Address Registration Option Flags" <xref target="IANA.I
/> when CMP.ARO.FLG"/> registry
updating the "Address Registration Option Flags" <xref target="IANA.ICMP.ARO. in the "Internet Control Message Protocol version 6 (ICMPv6) Parameters" regi
FLG"/> registry stry group as specified
under the heading "Internet Control Message Protocol version 6 (ICMPv6) Param in <xref target="AROflags"/> so this document is referenced in addition to <x
eters" as specified ref target="RFC8928"/> for bit number 1:
in <xref target="AROflags"/>:
</t> </t>
<table anchor="AROflags" ><name>Bit Position of the C-flag</name> <table anchor="AROflags" ><name>Bit Position of the C-flag</name>
<thead> <thead>
<tr><td>EARO flag</td><td>Description</td><td>Reference</td></tr> <tr><th>Bit Number</th><th>Description</th><th>Reference</th></tr>
</thead><tbody> </thead><tbody>
<tr><td>1 (suggested)</td><td> C-Flag </td><td>RFC XXXX and <xref target=" RFC8928"/></td></tr> <tr><td>1</td><td> C-Flag </td><td>RFC 9927 and <xref target="RFC8928"/></ td></tr>
</tbody> </tbody>
</table> <!-- end table "New ARO flag1" +--> </table>
</section> <!-- end section "Bit Position of the C-flag" --> </section>
<!-- <!--
<section><name>Adding the I-Field</name> <section><name>Adding the I-Field</name>
<t> <t>
IANA is requested to add 2-bit integer for the I-Field in the "Address Registrat ion Option Flags" IANA is requested to add 2-bit integer for the I-Field in the "Address Registrat ion Option Flags"
<xref target="IANA.ICMP.ARO.FLG"/> registry under the heading "Internet Control Message Protocol version 6 <xref target="IANA.ICMP.ARO.FLG"/> registry under the heading "Internet Control Message Protocol version 6
(ICMPv6) Parameters" as specified in <xref target="RFC8505"/>. (ICMPv6) Parameters" as specified in <xref target="RFC8505"/>.
</t> </t>
<table anchor="AROflags2" ><name>I-Field in ARO flags field</name> <table anchor="AROflags2" ><name>I-Field in ARO flags field</name>
skipping to change at line 321 skipping to change at line 321
<tr><td>Bit Number</td><td>Description</td><td>Reference</td></tr> <tr><td>Bit Number</td><td>Description</td><td>Reference</td></tr>
</thead><tbody> </thead><tbody>
<tr><td>4-5</td><td> I-Field </td><td><xref target="RFC8505"/> </td></tr> <tr><td>4-5</td><td> I-Field </td><td><xref target="RFC8505"/> </td></tr>
</tbody> </tbody>
</table> </table>
<t>The values taken by the I-Field are defined in <xref target="IANA.ICMP.ARO.F LG"/>.</t> <t>The values taken by the I-Field are defined in <xref target="IANA.ICMP.ARO.F LG"/>.</t>
</section> --> </section> -->
</section> <!-- end section "IANA Considerations" --> </section>
<!--
<section title="Acknowledgments">
<t>
Many thanks to Dave Thaler and Dan Romascanu for their early INT-DIR review.
</t>
</section> title="Acknowledgments" -->
</middle> </middle>
<back> <back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<references title="Normative References"> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4861.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4862.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6775.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8505.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8928.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9010.xml"
/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9685.xml"
/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere <!-- draft-ietf-6lo-prefix-registration-16 is companion doc RFC 9926
nce.RFC.2119.xml"/> -->
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.
RFC.4861.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.4862.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.6775.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.8174.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere
nce.RFC.8505.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.
RFC.8928.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference
.RFC.9010.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference
.RFC.9685.xml"/>
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/referenc <reference anchor="RFC9926" target="https://www.rfc-editor.org/info/rfc9926">
e.I-D.ietf-6lo-prefix-registration.xml"/> <front>
<title>IPv6 Neighbor Discovery Prefix Registration</title>
<author initials="P." surname="Thubert" fullname="Pascal Thubert" role="edit
or">
</author>
<date month="January" year="2026"/>
</front>
<seriesInfo name="RFC" value="9926"/>
<seriesInfo name="DOI" value="10.17487/RFC9926"/>
</reference>
<reference anchor="IANA.ICMP.ARO.FLG"> <reference anchor="IANA.ICMP.ARO.FLG" target="https://www.iana.org/assignments/i
<front> cmpv6-parameters">
<title>IANA Registry for the Address Registration Option <front>
Flags</title> <title>Address Registration Option Flags</title>
<author> <author>
<organization> <organization>
IANA IANA
</organization> </organization>
</author> </author>
<date year=""></date> </front>
</front> </reference>
<seriesInfo name="IANA," value="https://www.iana.org/assignments/
icmpv6-parameters/icmpv6-parameters.xhtml#icmpv6-adress-registration-option-flag
s"></seriesInfo>
</reference>
<reference anchor="IANA.ICMP.ARO.STAT"> <reference anchor="IANA.ICMP.ARO.STAT" target="https://www.iana.org/assignments/
<front> icmpv6-parameters">
<title>IANA Registry for the Address Registration Option <front>
Status Value</title> <title>Address Registration Option Status Values</title>
<author> <author>
<organization> <organization>
IANA IANA
</organization> </organization>
</author> </author>
<date year=""></date> </front>
</front> </reference>
<seriesInfo name="IANA," value=
"https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parame
ters.xhtml#address-registration"></seriesInfo>
</reference>
<reference anchor="IANA.ICMP.ARO.P-FIELD"> <!-- [rfced] FYI, regarding [IANA.ICMP.ARO.P-FIELD],
<front> we updated the reference's title to "P-Field Values" to match
<title>IANA Registry for the Address Registration Option what seems to have been intended. Please let us know if this
Status Value</title> is not accurate.
<author>
<organization> Original:
IANA [IANA.ICMP.ARO.P-FIELD]
</organization> IANA, "IANA Registry for the Address Registration Option
</author> Status Value", IANA, https://www.iana.org/assignments/
<date year=""></date> icmpv6-parameters/icmpv6-parameters.xhtml#p-field-values.
</front>
<seriesInfo name="IANA," value= Current:
"https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parame [IANA.ICMP.ARO.P-FIELD]
ters.xhtml#p-field-values"></seriesInfo> IANA, "P-Field Values",
</reference> <https://www.iana.org/assignments/icmpv6-parameters>.
-->
<reference anchor="IANA.ICMP.ARO.P-FIELD" target="https://www.iana.org/assignmen
ts/icmpv6-parameters">
<front>
<title>P-Field Values</title>
<author>
<organization>
IANA
</organization>
</author>
</front>
</reference>
</references> </references>
<references title="Informative References"> <references>
<name>Informative References</name>
<!-- <reference anchor="IEEE802154"> <!-- <reference anchor="IEEE802154">
<front> <front>
<title>IEEE Std 802.15.4, Part. 15.4: Wireless Medium Access <title>IEEE Std 802.15.4, Part. 15.4: Wireless Medium Access
Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate Control (MAC) and Physical Layer (PHY) Specifications for Low-Rate
Wireless Personal Area Networks Wireless Personal Area Networks
</title> </title>
<author> <author>
<organization>IEEE standard for Information Technology</organizat ion> <organization>IEEE standard for Information Technology</organizat ion>
</author> </author>
<date/> <date/>
</front> </front>
</reference> --> </reference> -->
<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refere nce.RFC.8929.xml"/> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.89 29.xml"/>
<!-- <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer ence.I-D.ietf-6lo-prefix-registration-10.xml"/> --> <!-- <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer ence.I-D.ietf-6lo-prefix-registration-10.xml"/> -->
<!-- <xi:include href='https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/refere nce.I-D.ietf-6man-ipv6-over-wireless.xml'/> --> <!-- <xi:include href='https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/refere nce.I-D.ietf-6man-ipv6-over-wireless.xml'/> -->
</references> </references>
</references>
<!--
<section numbered="false"><name>Acknowledgments</name>
<t>
Many thanks to Dave Thaler and Dan Romascanu for their early INT-DIR review.
</t>
-->
<!-- [rfced] Please review the "Inclusive Language" portion of the online
Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language>
and let us know if any changes are needed. Updates of this nature typically
result in more precise language, which is helpful for readers.
Note that our script did not flag any words in particular, but this should
still be reviewed as a best practice.
-->
</back> </back>
</rfc> </rfc>
 End of changes. 55 change blocks. 
181 lines changed or deleted 211 lines changed or added

This html diff was produced by rfcdiff 1.48.