Zum Hauptinhalt springen

11. IANA Considerations

This section preserves the RFC text for RPL DAO Projection and root-initiated routing state, including P-DAO, P-DAO-ACK, P-DAO-REQ, PDR-ACK, VIO, SIO, RPI, SRH, Storing and Non-Storing P-Routes, Tracks, IANA registrations, and normative behavior.

Original RFC Text

11.  IANA Considerations

11.1. RPL DODAG Configuration Option Flag

IANA has assigned a flag in the "DODAG Configuration Option Flags for
MOP 0..6" registry [RFC9008] under the "Routing Protocol for Low
Power and Lossy Networks (RPL)" registry group [IANA-RPL] as follows:

+============+==============================+===========+
| Bit Number | Capability Description | Reference |
+============+==============================+===========+
| 0 | Projected Routes Support (D) | RFC 9914 |
+------------+------------------------------+-----------+

Table 21: New DODAG Configuration Option Flag

IANA has added this RFC as an additional reference for MOP 7 in the
"Mode of Operation" registry under the "Routing Protocol for Low
Power and Lossy Networks (RPL)" registry group [IANA-RPL].

11.2. Elective 6LoWPAN Routing Header Type

IANA has updated the "Elective 6LoWPAN Routing Header Type" registry
[RFC8138] under the "IPv6 Low Power Personal Area Network Parameters"
registry group [IANA-6LO] as follows:

+=======+=============+===========+
| Value | Description | Reference |
+=======+=============+===========+
| 8 | P-RPI-6LoRH | RFC 9914 |
+-------+-------------+-----------+

Table 22: New Elective 6LoWPAN
Routing Header Type

11.3. Critical 6LoWPAN Routing Header Type

IANA has updated the "Critical 6LoWPAN Routing Header Type" registry
[RFC8138] under the "IPv6 Low Power Personal Area Network Parameters"
registry group [IANA-6LO] as follows:

+=======+=============+===========+
| Value | Description | Reference |
+=======+=============+===========+
| 8 | P-RPI-6LoRH | RFC 9914 |
+-------+-------------+-----------+

Table 23: New Critical 6LoWPAN
Routing Header Type

11.4. Registry for RPL Option Flags

IANA has created the "RPL Option Flags" registry, for the 8-bit RPL
Option flags field as detailed in Figure 11, under the "Routing
Protocol for Low Power and Lossy Networks (RPL)" registry group
[IANA-RPL]. The bits are indexed from 0 (leftmost) to 7. Each bit
is tracked with the following qualities:

* Bit number (counting from bit 0 as the most significant bit)

* Indication when set

* Reference

The registration procedure is Standards Action [RFC8126]. The
initial allocation is as indicated in Table 24:

+============+======================+===========+
| Bit Number | Indication When Set | Reference |
+============+======================+===========+
| 0 | Down (O) | [RFC6553] |
+------------+----------------------+-----------+
| 1 | Rank-Error (R) | [RFC6553] |
+------------+----------------------+-----------+
| 2 | Forwarding-Error (F) | [RFC6553] |
+------------+----------------------+-----------+
| 3 | Projected-Route (P) | RFC 9914 |
+------------+----------------------+-----------+
| 4..255 | Unassigned | |
+------------+----------------------+-----------+

Table 24: Initial P-DAO-REQ Flags

11.5. RPL Control Codes

IANA has updated the "RPL Control Codes" registry under the "Routing
Protocol for Low Power and Lossy Networks (RPL)" registry group
[IANA-RPL] as indicated in Table 25:

+======+================================================+===========+
| Code | Description | Reference |
+======+================================================+===========+
| 0x09 | Projected DAO Request (P-DAO-REQ) | RFC 9914 |
+------+------------------------------------------------+-----------+
| 0x0A | Projected DAO Request | RFC 9914 |
| | Acknowledgment (PDR-ACK) | |
+------+------------------------------------------------+-----------+

Table 25: New RPL Control Codes

11.6. RPL Control Message Options

IANA has updated the "RPL Control Message Options" registry under the
"Routing Protocol for Low Power and Lossy Networks (RPL)" registry
group [IANA-RPL] as indicated in Table 26:

+=======+==============================================+===========+
| Value | Meaning | Reference |
+=======+==============================================+===========+
| 0x0F | Stateful Storing Mode VIO (SM-VIO) | RFC 9914 |
+-------+----------------------------------------------+-----------+
| 0x10 | Source-Routed Non-Storing Mode VIO (NSM-VIO) | RFC 9914 |
+-------+----------------------------------------------+-----------+
| 0x11 | Sibling Information Option (SIO) | RFC 9914 |
+-------+----------------------------------------------+-----------+

Table 26: RPL Control Message Options

11.7. Registry for Projected DAO Request Flags

IANA has created the "Projected DAO Request (P-DAO-REQ) Flags"
registry under the "Routing Protocol for Low Power and Lossy Networks
(RPL)" registry group [IANA-RPL]. The bits are indexed from 0
(leftmost) to 7. Each bit is tracked with the following qualities:

* Bit number (counting from bit 0 as the most significant bit)

* Capability description

* Reference

The registration procedure is Standards Action [RFC8126]. The
initial allocation is as indicated in Table 27:

+============+========================================+===========+
| Bit Number | Capability Description | Reference |
+============+========================================+===========+
| 0 | PDR-ACK requested (K) | RFC 9914 |
+------------+----------------------------------------+-----------+
| 1 | Requested path should be redundant (R) | RFC 9914 |
+------------+----------------------------------------+-----------+
| 2..255 | Unassigned | |
+------------+----------------------------------------+-----------+

Table 27: Initial P-DAO-REQ Flags

11.8. Registry for Projected DAO Request Acknowledgment (PDR-ACK) Flags

IANA has created the "Projected DAO Request Acknowledgment (PDR-ACK)
Flags" registry under the "Routing Protocol for Low Power and Lossy
Networks (RPL)" registry group [IANA-RPL]. The bits are indexed from
0 (leftmost) to 7. Each bit is tracked with the following qualities:

* Bit number (counting from bit 0 as the most significant bit)

* Capability description

* Reference

The registration procedure is Standards Action [RFC8126]. At the
time of publication of this document, no bit has been assigned in
this registry.

11.9. Registry for PDR-ACK Acceptance Status Values

IANA has created the "PDR-ACK Acceptance Status Values" registry
under the "Routing Protocol for Low Power and Lossy Networks (RPL)"
registry group [IANA-RPL]. Each value is tracked with the following
qualities:

* Value

* Meaning

* Reference

The possible values are expressed as a 6-bit unsigned integer
(0..63). The registration procedure is Standards Action [RFC8126].
The initial allocation is as indicated in Table 28:

+=======+========================+===========+
| Value | Meaning | Reference |
+=======+========================+===========+
| 0 | Unqualified Acceptance | RFC 9914 |
+-------+------------------------+-----------+
| 1..63 | Unassigned | |
+-------+------------------------+-----------+

Table 28: Acceptance Values of the PDR-ACK
Status

11.10. Registry for PDR-ACK Rejection Status Values

IANA has created the "PDR-ACK Rejection Status Values" registry under
the "Routing Protocol for Low Power and Lossy Networks (RPL)"
registry group [IANA-RPL]. Each value is tracked with the following
qualities:

* Value

* Meaning

* Reference

The possible values are expressed as a 6-bit unsigned integer
(0..63). The registration procedure is Standards Action [RFC8126].
The initial allocation is as indicated in Table 29:

+=======+=======================+===========+
| Value | Meaning | Reference |
+=======+=======================+===========+
| 0 | Unqualified Rejection | RFC 9914 |
+-------+-----------------------+-----------+
| 1 | Transient Failure | RFC 9914 |
+-------+-----------------------+-----------+
| 2..63 | Unassigned | |
+-------+-----------------------+-----------+

Table 29: PDR-ACK Rejection Status Values

11.11. Registry for Via Information Options Flags

IANA has created the "Via Information Options (VIO) Flags" registry
under the "Routing Protocol for Low Power and Lossy Networks (RPL)"
registry group [IANA-RPL]. The bits are indexed from 0 (leftmost) to
7. Each bit is tracked with the following qualities:

* Bit number (counting from bit 0 as the most significant bit)

* Capability description

* Reference

The registration procedure is Standards Action [RFC8126]. At the
time of publication of this document, no bit has been assigned in
this registry (see more in Section 5.3).

11.12. Registry for Sibling Information Option Flags

IANA has created the "Sibling Information Option (SIO) Flags"
registry under the "Routing Protocol for Low Power and Lossy Networks
(RPL)" registry group [IANA-RPL]. The bits are indexed from 0
(leftmost) to 4. Each bit is tracked with the following qualities:

* Bit number (counting from bit 0 as the most significant bit)

* Capability description

* Reference

The registration procedure is Standards Action [RFC8126]. The
initial allocation is as indicated in Table 30 (see more in
Figure 17):

+============+=========================================+===========+
| Bit Number | Capability Description | Reference |
+============+=========================================+===========+
| 0 | 'S' flag: Sibling in same DODAG as self | RFC 9914 |
+------------+-----------------------------------------+-----------+
| 1 | 'B' flag: Connectivity to the sibling | RFC 9914 |
| | is roughly symmetrical | |
+------------+-----------------------------------------+-----------+
| 2..4 | Unassigned | |
+------------+-----------------------------------------+-----------+

Table 30: Initial SIO Flags

11.13. Destination Advertisement Object Flag

IANA has updated the "Destination Advertisement Object (DAO) Flags"
registry, created in Section 20.11 of [RPL], under the "Routing
Protocol for Low Power and Lossy Networks (RPL)" registry group
[IANA-RPL] as indicated in Table 31 (see more in Section 4.1.1):

+============+========================+===========+
| Bit Number | Capability Description | Reference |
+============+========================+===========+
| 2 | Projected DAO (P) | RFC 9914 |
+------------+------------------------+-----------+

Table 31: New Destination Advertisement Object
(DAO) Flag

11.14. Destination Advertisement Object Acknowledgment Flag

IANA has updated the "Destination Advertisement Object (DAO)
Acknowledgment Flags" registry, created in Section 20.12 of [RPL],
under the "Routing Protocol for Low Power and Lossy Networks (RPL)"
registry group [IANA-RPL] as indicated in Table 32 (see more in
Section 4.1.2):

+============+==================================+===========+
| Bit Number | Capability Description | Reference |
+============+==================================+===========+
| 1 | Projected DAO Acknowledgment (P) | RFC 9914 |
+------------+----------------------------------+-----------+

Table 32: New Destination Advertisement Object
Acknowledgment Flag

11.15. ICMPv6 Error Code

In some cases, RPL will return an ICMPv6 error message when a message
cannot be forwarded along a P-Route.

Per this specification, IANA has updated the "Type 1 - Destination
Unreachable" registry, in the "ICMPv6 'Code' Fields" registry, under
the "Internet Control Message Protocol version 6 (ICMPv6) Parameters"
registry group [IANA-ICMP] as indicated in Table 33.

+======+==================+===========+
| Code | Name | Reference |
+======+==================+===========+
| 9 | Error in P-Route | RFC 9914 |
+------+------------------+-----------+

Table 33: New ICMPv6 Error Code

11.16. RPL Rejection Status Values

IANA has updated the "RPL Rejection Status" registry under the
"Routing Protocol for Low Power and Lossy Networks (RPL)" registry
group [IANA-RPL] as indicated in Table 34:

+=======+=========================+===========+
| Value | Meaning | Reference |
+=======+=========================+===========+
| 2 | Out of Resources | RFC 9914 |
+-------+-------------------------+-----------+
| 3 | Error in VIO | RFC 9914 |
+-------+-------------------------+-----------+
| 4 | Predecessor Unreachable | RFC 9914 |
+-------+-------------------------+-----------+
| 5 | Unreachable Target | RFC 9914 |
+-------+-------------------------+-----------+
| 6..63 | Unassigned | |
+-------+-------------------------+-----------+

Table 34: RPL Rejection Status Values