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

The information below is for an old version of the document
Document Type Active Internet-Draft (roll WG)
Authors Pascal Thubert  , Rahul Jadhav  , Matthew Gillmore 
Last updated 2020-09-29 (latest revision 2020-09-21)
Replaces draft-thubert-roll-dao-projection
Stream IETF
Intended RFC status (None)
Formats 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
Updates: 6550 (if approved)                                  R.A. Jadhav
Intended status: Standards Track                             Huawei Tech
Expires: 2 April 2021                                        M. Gillmore
                                                                   Itron
                                                       29 September 2020

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

Abstract

   This document updates RFC 6550 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 source-route 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 2 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.

Thubert, et al.           Expires 2 April 2021                  [Page 1]
Internet-Draft               DAO Projection               September 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 . . . . . . . . . . . . . . . . . . . . . . .   5
     2.4.  References  . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Updating RFC 6550 . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Identifying a Track . . . . . . . . . . . . . . . . . . . . .   8
   5.  New RPL Control Messages and Options  . . . . . . . . . . . .   9
     5.1.  New P-DAO Request Control Message . . . . . . . . . . . .   9
     5.2.  New PDR-ACK Control Message . . . . . . . . . . . . . . .  10
     5.3.  Route Projection Options  . . . . . . . . . . . . . . . .  12
     5.4.  Sibling Information Option  . . . . . . . . . . . . . . .  14
   6.  Projected DAO . . . . . . . . . . . . . . . . . . . . . . . .  16
     6.1.  Requesting a Track  . . . . . . . . . . . . . . . . . . .  17
     6.2.  Routing over a Track  . . . . . . . . . . . . . . . . . .  18
     6.3.  Non-Storing Mode Projected Route  . . . . . . . . . . . .  18
     6.4.  Storing Mode Projected Route  . . . . . . . . . . . . . .  20
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  22
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  22
     8.1.  New RPL Control Codes . . . . . . . . . . . . . . . . . .  22
     8.2.  New RPL Control Message Options . . . . . . . . . . . . .  22
     8.3.  SubRegistry for the Projected DAO Request Flags . . . . .  23
     8.4.  SubRegistry for the PDR-ACK Flags . . . . . . . . . . . .  23
     8.5.  Subregistry for the PDR-ACK Acceptance Status Values  . .  24
     8.6.  Subregistry for the PDR-ACK Rejection Status Values . . .  24
     8.7.  SubRegistry for the Route Projection Options Flags  . . .  24
     8.8.  SubRegistry for the Sibling Information Option Flags  . .  25
     8.9.  Error in Projected Route ICMPv6 Code  . . . . . . . . . .  25
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  25
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  26
   11. Informative References  . . . . . . . . . . . . . . . . . . .  26
Show full document text