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

Document Type Active Internet-Draft (roll WG)
Last updated 2020-04-17
Replaces draft-thubert-roll-turnon-rfc8138
Stream IETF
Intended RFC status Proposed Standard
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
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 Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Ines Robles <mariainesrobles@googlemail.com>
ROLL                                                     P. Thubert, Ed.
Internet-Draft                                                   L. Zhao
Updates: 6550, 8138 (if approved)                          Cisco Systems
Intended status: Standards Track                           17 April 2020
Expires: 19 October 2020

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

Abstract

   This document updates RFC 8138 and RFC 6550 by defining a bit in the
   RPL configuration option to indicate whether RFC 8138 compression is
   used within the RPL Instance, and specify the behavior of RFC
   8138-capable nodes when the bit is set and reset.

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 19 October 2020.

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 19 October 2020                [Page 1]
Internet-Draft                Turn On 6LoRH                   April 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  References  . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  BCP 14  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Updating RFC 8138 . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Transition Scenarios  . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Inconsistent State While Migrating  . . . . . . . . . . .   6
     5.2.  Single RPL Instance Scenario  . . . . . . . . . . . . . .   6
     5.3.  Double RPL Instances Scenario . . . . . . . . . . . . . .   7
     5.4.  Rolling Back  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   10. Informative References  . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The transition of a RPL [RFC6550] network to activate the compression
   defined in [RFC8138] can only be done when all routers in the network
   support it.  Otherwise, a non-capable node acting as a router would
   drop the compressed packets and black-hole its subDAG.  In a mixed
   case with both RFC8138-capable and non-capable nodes, the compression
   may be turned on only if all the non-capable nodes act as Hosts and
   their RPL parents handle the compression/decompression for them.

   This document complements [RFC8138] and dedicates a flag in the RPL
   configuration option to indicate whether [RFC8138] compression should
   be used within the RPL Instance.  The setting of this new flag is
   controlled by the Root and propagates as is in the whole network.
   When the bit is not set, source nodes that support [RFC8138] should
   refrain from using the compression unless the information is
   superseded by configuration.

   With RPL, a leaf is an IPv6 Host, which implies that leaves do not
   forward packets.  This specification provides scenarios that force a
   non-capable RPL-Aware Node (RAN) to become a leaf.  The parent router
   must know, e.g., by configuration, or leveraging "RPL Capabilities"
   [CAPABILITIES], when a leaf does not support the compression defined
   in [RFC8138].  This is implicitly the case for a RPL-Unaware Leaf
Show full document text