Root initiated routing state in RPL
draft-ietf-roll-dao-projection-15

Document Type Active Internet-Draft (roll WG)
Authors Pascal Thubert  , Rahul Jadhav  , Matthew Gillmore 
Last updated 2020-11-27
Replaces draft-thubert-roll-dao-projection
Stream IETF
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document (wg milestone: Jul 2020 - Initial submission o... )
Revised I-D Needed - Issue raised by WGLC
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ROLL                                                     P. Thubert, Ed.
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                             R.A. Jadhav
Expires: 31 May 2021                                         Huawei Tech
                                                             M. Gillmore
                                                                   Itron
                                                        27 November 2020

                  Root initiated routing state in RPL
                   draft-ietf-roll-dao-projection-15

Abstract

   This document extends RFC 6550 and RFC 6553 to enable a RPL Root to
   install and maintain Projected Routes within its DODAG, along a
   selected set of nodes that may or may not include self, for a chosen
   duration.  This potentially enables routes that are more optimized or
   resilient than those obtained with the classical distributed
   operation of RPL, either in terms of the size of a Routing Header or
   in terms of path length, which impacts both the latency and the
   packet delivery ratio.

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 31 May 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.

Thubert, et al.            Expires 31 May 2021                  [Page 1]
Internet-Draft               DAO Projection                November 2020

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   5
     2.2.  Glossary  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Other Terms . . . . . . . . . . . . . . . . . . . . . . .   6
     2.4.  References  . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Extending RFC 6550  . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Projected DAO . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Sibling Information Option  . . . . . . . . . . . . . . .   8
     3.3.  P-DAO Request . . . . . . . . . . . . . . . . . . . . . .   8
     3.4.  Extending the RPI . . . . . . . . . . . . . . . . . . . .   8
   4.  Extending RFC 6553  . . . . . . . . . . . . . . . . . . . . .   8
   5.  Extending RFC 8138  . . . . . . . . . . . . . . . . . . . . .   9
   6.  New RPL Control Messages and Options  . . . . . . . . . . . .  10
     6.1.  New P-DAO Request Control Message . . . . . . . . . . . .  10
     6.2.  New PDR-ACK Control Message . . . . . . . . . . . . . . .  11
     6.3.  Via Information Options . . . . . . . . . . . . . . . . .  12
     6.4.  Sibling Information Option  . . . . . . . . . . . . . . .  15
   7.  Projected DAO . . . . . . . . . . . . . . . . . . . . . . . .  16
     7.1.  Requesting a Track  . . . . . . . . . . . . . . . . . . .  18
     7.2.  Identifying a Track . . . . . . . . . . . . . . . . . . .  18
     7.3.  Installing a Track  . . . . . . . . . . . . . . . . . . .  19
     7.4.  Forwarding Along a Track  . . . . . . . . . . . . . . . .  20
     7.5.  Non-Storing Mode Projected Route  . . . . . . . . . . . .  21
     7.6.  Storing Mode Projected Route  . . . . . . . . . . . . . .  23
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  25
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  25
     9.1.  New Elective 6LoWPAN Routing Header Type  . . . . . . . .  25
     9.2.  New Critical 6LoWPAN Routing Header Type  . . . . . . . .  25
     9.3.  New Subregistry For The RPL Option Flags  . . . . . . . .  26
     9.4.  New RPL Control Codes . . . . . . . . . . . . . . . . . .  26
     9.5.  New RPL Control Message Options . . . . . . . . . . . . .  27
Show full document text