A RPL DODAG Configuration Option for the 6LoWPAN Routing Header
draft-ietf-roll-turnon-rfc8138-15

Document Type Active Internet-Draft (roll WG)
Last updated 2020-09-18
Replaces draft-thubert-roll-turnon-rfc8138
Stream IETF
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Mar 2020 - Initial submission t... )
Document shepherd Ines Robles
Shepherd write-up Show (last changed 2020-04-17)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has 2 DISCUSSes. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Alvaro Retana
Send notices to Ines Robles <mariainesrobles@googlemail.com>, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
ROLL                                                     P. Thubert, Ed.
Internet-Draft                                                   L. Zhao
Updates: 6550, 8138 (if approved)                          Cisco Systems
Intended status: Standards Track                       18 September 2020
Expires: 22 March 2021

    A RPL DODAG Configuration Option for the 6LoWPAN Routing Header
                   draft-ietf-roll-turnon-rfc8138-15

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

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 22 March 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
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Thubert & Zhao            Expires 22 March 2021                 [Page 1]
Internet-Draft                Turn On 6LoRH               September 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  References  . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Updating RFC 8138 . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Transition Scenarios  . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Coexistence . . . . . . . . . . . . . . . . . . . . . . .   6
     5.2.  Inconsistent State While Migrating  . . . . . . . . . . .   6
     5.3.  Rolling Back  . . . . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   10. Informative References  . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The design of Low Power and Lossy Networks (LLNs) is generally
   focused on saving energy, which is the most constrained resource of
   all.  The routing optimizations in the "Routing Protocol for Low
   Power and Lossy Networks" [RFC6550] (RPL) such as routing along a
   Destination-Oriented Directed Acyclic Graph (DODAG) to a Root Node
   and the associated routing header compression and forwarding
   technique specified in [RFC8138] derive from that primary concern.

   Enabling [RFC8138] on a running network requires a Flag Day where the
   network is upgraded and rebooted.  Otherwise, if acting as a Leaf, a
   node that does not support the compression would fail to communicate;
   if acting as a router it would drop the compressed packets and black-
   hole a portion of the network.  This specification enables a hot
   upgrade where a live network is migrated.  During the migration, the
   compression remains inactive, until all nodes are upgraded.

   This document complements [RFC8138] and signals whether it should be
   used within a RPL DODAG with a new flag in the RPL DODAG
   Configuration Option.  The setting of this new flag is controlled by
   the Root and propagates as is in the whole network as part of the
   normal RPL signaling.

   The flag is cleared to maintain the compression inactive during the
   migration phase.  When the migration is complete (e.g., as known by
   network management and/or inventory), the flag is set and the
Show full document text