rfc9927v1.txt   rfc9927.txt 
skipping to change at line 51 skipping to change at line 51
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License. in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction 1. Introduction
2. Terminology 2. Terminology
2.1. Requirements Language 2.1. Requirements Language
2.2. Terminology 2.2. Related Documents
2.3. Acronyms 2.3. Acronyms
3. Updating RFC 8928 3. Updating RFC 8928
4. Security Considerations 4. Security Considerations
5. Operational Considerations 5. Operational Considerations
6. IANA Considerations 6. IANA Considerations
6.1. Bit Position of the C-flag 6.1. Bit Position of the C-flag
7. References 7. References
7.1. Normative References 7.1. Normative References
7.2. Informative References 7.2. Informative References
Authors' Addresses Authors' Addresses
skipping to change at line 88 skipping to change at line 88
2. Terminology 2. Terminology
2.1. Requirements Language 2.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 "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2.2. Terminology 2.2. Related Documents
This document uses terms and concepts that are discussed in IPv6 This document uses terms and concepts that are discussed in IPv6
Neighbor Discovery (ND) [RFC4861], [RFC4862], as well as 6LoWPAN-ND Neighbor Discovery (ND) [RFC4861], [RFC4862], as well as 6LoWPAN-ND
[RFC6775], [RFC8505], [RFC8928], [RFC8929], [RFC9685], and [RFC9926]. [RFC6775], [RFC8505], [RFC8928], [RFC8929], [RFC9685], and [RFC9926].
2.3. Acronyms 2.3. Acronyms
This document uses the following abbreviations: This document uses the following abbreviations:
*6LN:* 6LoWPAN Node 6LN: 6LoWPAN Node
*EARO:* Extended Address Registration Option EARO: Extended Address Registration Option
*ND:* Neighbor Discovery ND: Neighbor Discovery
*RATInd:* Registered Address Type Indicator RATInd: Registered Address Type Indicator
*ROVR:* Registration Ownership Verifier ROVR: Registration Ownership Verifier
3. Updating RFC 8928 3. Updating RFC 8928
[RFC8928] incorrectly refers to the Extended Address Registration [RFC8928] incorrectly refers to the Extended Address Registration
Option (EARO) as the Enhanced Address Registration Option. This Option (EARO) as the Enhanced Address Registration Option. This
specification corrects this terminology throughout the document. specification corrects this terminology throughout the document.
In [RFC8928], the C-flag is specified in the EARO flags field at bit In [RFC8928], the C-flag is specified in the EARO flags field at bit
position 3 (as depicted in Figure 1 of [RFC8928]); however, [RFC8928] position 3 (as depicted in Figure 1 of [RFC8928]); however, [RFC8928]
fails to register its position with IANA. Later, [RFC9685] defined fails to register its position with IANA. Later, [RFC9685] defined
skipping to change at line 165 skipping to change at line 165
... Registration Ownership Verifier (ROVR) ... ... Registration Ownership Verifier (ROVR) ...
| (64, 128, 192, or 256 bits) | | (64, 128, 192, or 256 bits) |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Extended Address Registration Option (EARO) Format for Figure 2: Extended Address Registration Option (EARO) Format for
Use in NA Messages Use in NA Messages
Option fields of interest for this specification: Option fields of interest for this specification:
*Type:* 33 Type: 33
*Length:* Defined in [RFC8505] Length: Defined in [RFC8505]
*F:* Defined in [RFC9926] F: Defined in [RFC9926]
*Prefix Length* Defined in [RFC9926] Prefix Length Defined in [RFC9926]
*Status:* 6-bit unsigned integer. This field is used in NA(EARO) Status: 6-bit unsigned integer. This field is used in NA(EARO)
response messages only to indicate the status of a registration. response messages only to indicate the status of a registration.
This field is defined in [RFC8505] and resized by [RFC9010]. The This field is defined in [RFC8505] and resized by [RFC9010]. The
values for the Status field are available in [IANA.ICMP.ARO.STAT]. values for the Status field are available in [IANA.ICMP.ARO.STAT].
This field MUST be set to 0 in NS(EARO) messages unless the This field MUST be set to 0 in NS(EARO) messages unless the
registration is for a prefix, in which case the F-flag is set and registration is for a prefix, in which case the F-flag is set and
the prefix length is provided. the prefix length is provided.
*Opaque:* Defined in [RFC8505] Opaque: Defined in [RFC8505]
*r (reserved):* 1-bit reserved field in NS(EARO) and NA(EARO) as r (reserved): 1-bit reserved field in NS(EARO) and NA(EARO) as
depicted in Figure 1 and Figure 2. 2-bit reserved field (most depicted in Figure 1 and Figure 2. 2-bit reserved field (most
significant bits of Status filed) in NA(EARO) as depicted in significant bits of Status filed) in NA(EARO) as depicted in
Figure 2. All reserved field MUST be set to zero by the sender Figure 2. All reserved field MUST be set to zero by the sender
and MUST be ignored by the receiver. and MUST be ignored by the receiver.
*C:* 1-bit flag, moved from its position in Figure 1 of [RFC8928]. C: 1-bit flag, moved from its position in Figure 1 of [RFC8928]. It
It is set to indicate that the ROVR field contains a Crypto-ID and is set to indicate that the ROVR field contains a Crypto-ID and
that the 6LN MAY be challenged for ownership. that the 6LN MAY be challenged for ownership.
*P:* 2-bit field for Registered Address Type Indicator (RATInd). P: 2-bit field for Registered Address Type Indicator (RATInd).
Indicates whether the registered address is unicast, multicast, Indicates whether the registered address is unicast, multicast,
anycast, or derived from the registered unicast prefix. Used to anycast, or derived from the registered unicast prefix. Used to
transport the RATInd in different protocols. The values for the transport the RATInd in different protocols. The values for the
RATInd field are available in [IANA.ICMP.ARO.P-FIELD]. RATInd field are available in [IANA.ICMP.ARO.P-FIELD].
*I:* Defined in [RFC8505] I: Defined in [RFC8505]
*R:* Defined in [RFC8505] R: Defined in [RFC8505]
*T:* Defined in [RFC8505] T: Defined in [RFC8505]
*TID (Transaction ID):* Defined in [RFC8505] TID (Transaction ID): Defined in [RFC8505]
*Registration Lifetime:* Defined in [RFC8505] Registration Lifetime: Defined in [RFC8505]
*Registration Ownership Verifier (ROVR):* Defined in [RFC8505]. Registration Ownership Verifier (ROVR): Defined in [RFC8505].
Variable-length field used to verify who "owns" a registered IPv6 Variable-length field used to verify who "owns" a registered IPv6
address. When the C-flag is set, this field contains a Crypto-ID address. When the C-flag is set, this field contains a Crypto-ID
[RFC8928]. [RFC8928].
4. Security Considerations 4. Security Considerations
This specification does not introduce any new security considerations This specification does not introduce any new security considerations
beyond those already discussed in [RFC8928] and [RFC8505]. beyond those already discussed in [RFC8928] and [RFC8505].
5. Operational Considerations 5. Operational Considerations
 End of changes. 22 change blocks. 
23 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.48.