draft-ietf-roll-unaware-leaves-19.txt   draft-ietf-roll-unaware-leaves-20.txt 
ROLL P. Thubert, Ed. ROLL P. Thubert, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: 6550, 8505 (if approved) M. Richardson Updates: 6550, 8505 (if approved) M. Richardson
Intended status: Standards Track Sandelman Intended status: Standards Track Sandelman
Expires: 22 March 2021 18 September 2020 Expires: 28 March 2021 24 September 2020
Routing for RPL Leaves Routing for RPL Leaves
draft-ietf-roll-unaware-leaves-19 draft-ietf-roll-unaware-leaves-20
Abstract Abstract
This specification extends RFC6550 and RFC8505 to provide routing This specification extends RFC6550 and RFC8505 to provide routing
services to Hosts called RPL Unaware Leaves that implement 6LoWPAN ND services to Hosts called RPL Unaware Leaves that implement 6LoWPAN ND
but do not participate in RPL. This specification also enables the but do not participate in RPL. This specification also enables the
RPL Root to proxy the 6LoWPAN keep-alive flows in its DODAG. RPL Root to proxy the 6LoWPAN keep-alive flows in its DODAG.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 22 March 2021. This Internet-Draft will expire on 28 March 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 14, line 36 skipping to change at page 14, line 36
The "P" flag is set to indicate support for this specification at the The "P" flag is set to indicate support for this specification at the
Root within the DODAG. The "P" flag is encoded in position 1 of the Root within the DODAG. The "P" flag is encoded in position 1 of the
reserved Flags in the DODAG Configuration Option (counting from bit 0 reserved Flags in the DODAG Configuration Option (counting from bit 0
as the most significant bit) and set to 0 in legacy implementations as the most significant bit) and set to 0 in legacy implementations
as specified respectively in Sections 20.14 and 6.7.6 of [RFC6550]. as specified respectively in Sections 20.14 and 6.7.6 of [RFC6550].
The "P" flag is set to indicate that the Root performs the proxy The "P" flag is set to indicate that the Root performs the proxy
operation, which implies that it supports the Updated RPL Target operation, which implies that it supports the Updated RPL Target
Option (see Section 6.1). Option (see Section 6.1).
Section 4.3 of [USEofRPLinfo] updates [RFC6550] to indicate that the
definition of the Flags applies to Mode of Operation (MOP) values
zero (0) to six (6) only, leaving the flags reserved for MOP value
seven (7). For a MOP value of 7, the bit in position 1 is considered
unallocated and the Root is expected to perform the proxy operation
by default.
The RPL DODAG Configuration Option is typically placed in a DODAG The RPL DODAG Configuration Option is typically placed in a DODAG
Information Object (DIO) message. The DIO message propagates down Information Object (DIO) message. The DIO message propagates down
the DODAG to form and then maintain its structure. The DODAG the DODAG to form and then maintain its structure. The DODAG
Configuration Option is copied unmodified from parents to children. Configuration Option is copied unmodified from parents to children.
Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP) in
the DIO Base Object. This specification applies to MOP values 0 to
6. For a MOP value of 7, the bit in position 1 is considered
unallocated and [RFC8138] MUST be used by default.
[RFC6550] states that "Nodes other than the DODAG Root MUST NOT [RFC6550] states that "Nodes other than the DODAG Root MUST NOT
modify this information when propagating the DODAG Configuration modify this information when propagating the DODAG Configuration
option". Therefore, a legacy parent propagates the "P" flag as set option". Therefore, a legacy parent propagates the "T" flag as set
by the Root whether it supports this specification or not. So when by the Root, and when the "T" flag is set, it is transparently
the "P" flag is set, it is transparently flooded to all the nodes in flooded to all the nodes in the DODAG.
the DODAG.
6.3. Updated RPL Status 6.3. Updated RPL Status
The RPL Status is defined in section 6.5.1 of [RFC6550] for use in The RPL Status is defined in section 6.5.1 of [RFC6550] for use in
the DAO-ACK message and values are assigned as follows: the DAO-ACK message and values are assigned as follows:
+---------+--------------------------------+ +---------+--------------------------------+
| Range | Meaning | | Range | Meaning |
+---------+--------------------------------+ +---------+--------------------------------+
| 0 | Success/Unqualified acceptance | | 0 | Success/Unqualified acceptance |
skipping to change at page 26, line 40 skipping to change at page 26, line 40
whereby it is possible to validate the origin of an address that is whereby it is possible to validate the origin of an address that is
injected in a DAO. This specification makes a first step in that injected in a DAO. This specification makes a first step in that
direction by allowing the Root to challenge the RUL via the 6LR that direction by allowing the Root to challenge the RUL via the 6LR that
serves it. serves it.
12. IANA Considerations 12. IANA Considerations
12.1. Fixing the Address Registration Option Flags 12.1. Fixing the Address Registration Option Flags
Section 9.1 of [RFC8505] creates a Registry for the 8-bit Address Section 9.1 of [RFC8505] creates a Registry for the 8-bit Address
Registration Option Flags field. Registration Option Flags field. IANA is requested to rename the
first column of the table from "ARO Status" to "Bit number".
IANA is requested to rename the first column of the table from "ARO
Status" to "Bit number".
12.2. Resizing the ARO Status values 12.2. Resizing the ARO Status values
Section 12 of [RFC6775] creates the Address Registration Option Section 12 of [RFC6775] creates the Address Registration Option
Status Values Registry with a range 0-255. Status Values Registry with a range 0-255.
This specification reduces that range to 0-63. This specification reduces that range to 0-63.
IANA is requested to reduce the upper bound of the unassigned values IANA is requested to reduce the upper bound of the unassigned values
in the Address Registration Option Status Values Registry from -255 in the Address Registration Option Status Values Registry from -255
to -63. to -63.
12.3. New DODAG Configuration Option Flag 12.3. New DODAG Configuration Option Flag
This specification updates the Registry for the "DODAG Configuration This specification updates the Registry that was created for
Option Flags" that was created for [RFC6550] as follows: [RFC6550] as the registry for "DODAG Configuration Option Flags" and
updated as the registry for "DODAG Configuration Option Flags for MOP
0..6" by [USEofRPLinfo], by allocating one new Flag as follows:
+------------+----------------------------+-----------+ +------------+----------------------------+-----------+
| Bit Number | Capability Description | Reference | | Bit Number | Capability Description | Reference |
+------------+----------------------------+-----------+ +------------+----------------------------+-----------+
| 1 | Root Proxies EDAR/EDAC (P) | THIS RFC | | 1 | Root Proxies EDAR/EDAC (P) | THIS RFC |
+------------+----------------------------+-----------+ +------------+----------------------------+-----------+
Table 2: New DODAG Configuration Option Flag Table 2: New DODAG Configuration Option Flag
12.4. New RPL Target Option Flag 12.4. New RPL Target Option Flag
 End of changes. 8 change blocks. 
19 lines changed or deleted 19 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/