--- 1/draft-ietf-roll-turnon-rfc8138-16.txt 2020-09-30 10:14:48.116943096 -0700 +++ 2/draft-ietf-roll-turnon-rfc8138-17.txt 2020-09-30 10:14:48.140943701 -0700 @@ -1,19 +1,19 @@ ROLL P. Thubert, Ed. Internet-Draft L. Zhao Updates: 8138 (if approved) Cisco Systems -Intended status: Standards Track 24 September 2020 -Expires: 28 March 2021 +Intended status: Standards Track 30 September 2020 +Expires: 3 April 2021 A RPL DODAG Configuration Option for the 6LoWPAN Routing Header - draft-ietf-roll-turnon-rfc8138-16 + draft-ietf-roll-turnon-rfc8138-17 Abstract This document updates RFC 8138 by defining a bit in the RPL DODAG Configuration Option to indicate whether compression is used within the RPL Instance, and specify the behavior of RFC 8138-capable nodes when the bit is set and unset. Status of This Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 28 March 2021. + This Internet-Draft will expire on 3 April 2021. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights @@ -159,36 +159,36 @@ information affecting the construction and maintenance of the DODAG, as well as operational parameters for RPL on the DODAG, through the DODAG. As shown in Figure 1, the Option was originally designed with 4 bit positions reserved for future use as Flags. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = 0x04 |Opt Length = 14| | |T| |A| ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + + <- Flags -> Figure 1: DODAG Configuration Option (Partial View) This specification defines a new flag "Enable RFC8138 Compression" (T). The "T" flag is set to turn-on the use of [RFC8138] within the DODAG. The "T" flag is encoded in position 2 of the reserved Flags in the DODAG Configuration Option (counting from bit 0 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]. 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 2 is considered - unallocated and [RFC8138] MUST be used on Links where 6LoWPAN Header - Compression [RFC6282] applies and MUST NOT be used otherwise. + zero (0) to six (6) only. For a MOP value of 7, [RFC8138] MUST be + used on Links where 6LoWPAN Header Compression [RFC6282] applies and + MUST NOT be used otherwise. The RPL DODAG Configuration Option is typically placed in a DODAG Information Object (DIO) message. The DIO message propagates down the DODAG to form and then maintain its structure. The DODAG Configuration Option is copied unmodified from parents to children. [RFC6550] states that "Nodes other than the DODAG Root MUST NOT modify this information when propagating the DODAG Configuration option". Therefore, a legacy parent propagates the "T" flag as set by the Root, and when the "T" flag is set, it is transparently flooded to all the nodes in the DODAG. @@ -285,23 +285,24 @@ flag unset before allowing nodes that do not support the compression in the network. To that effect, whether the compression is active in a node SHOULD be exposed the node's management interface. Nodes that do not support [RFC8138] SHOULD NOT be deployed in a network where the compression is turned on. If that is done, the node can only operate as a RUL. 6. IANA Considerations - IANA is requested to assign a new option flag from the Registry for - the "DODAG Configuration Option Flags" that was created for [RFC6550] - as follows: + This specification updates the Registry that was created for + [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 | +---------------+---------------------------------+-----------+ | 2 (suggested) | Turn on RFC8138 Compression (T) | THIS RFC | +---------------+---------------------------------+-----------+ Table 1: New DODAG Configuration Option Flag 7. Security Considerations