Root initiated routing state in RPL
draft-thubert-roll-dao-projection-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-19
Replaced by draft-ietf-roll-dao-projection
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ROLL                                                     P. Thubert, Ed.
Internet-Draft                                              J. Pylakutty
Intended status: Standards Track                                   Cisco
Expires: April 21, 2016                                 October 19, 2015

                  Root initiated routing state in RPL
                  draft-thubert-roll-dao-projection-01

Abstract

   This document proposes a root-initiated protocol extension to RPL
   that enables to install a limited amount of downward routes in non-
   storing mode.  This enables loose source routing down the DODAG.

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 http://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 April 21, 2016.

Copyright Notice

   Copyright (c) 2015 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
   (http://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 & Pylakutty      Expires April 21, 2016                 [Page 1]
Internet-Draft     Root initiated routing state in RPL      October 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  New RPL Control Message Options . . . . . . . . . . . . . . .   3
     3.1.  Via Information . . . . . . . . . . . . . . . . . . . . .   4
   4.  Loose Source Routing in Non-storing Mode  . . . . . . . . . .   5
   5.  Centralized Computation of Optimized Peer-to-Peer Routes  . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The Routing Protocol for Low Power and Lossy Networks [RFC6550]
   (LLN)(RPL) specification defines a generic Distance Vector protocol
   that is designed for very low energy consumption and adapted to a
   variety of LLNs.  RPL forms Destination Oriented Directed Acyclic
   Graphs (DODAGs) which root often acts as the Border Router to connect
   the RPL domain to the Internet.  The root is responsible to select
   the RPL Instance that is used to forward a packet coming from the
   Internet into the RPL domain and set the related RPL information in
   the packets.

   The non-storing mode of operation (MOP) is largely utilized because
   networks can get very large and the amount of memory in nodes close
   to the root may become prohibitive in storing mode.

   But as a network gets deep, the size of the source routing header
   that the root must add to all the downward packets may also become an
   issue as well.  In some cases, RPL network form long lines and a
   limited number of well-targeted routes would enable a loose source
   routing operation and save packet size, energy, and eventually
   fragmentation which is highly detrimental to the LLN operation.
   Because the capability to store state in every node is limited, the
   decision of which route is installed where can only be optimized with
   a global knowledge of the system.

   RPL storing mode is optimized or Point-to-Multipoint (P2MP), root to
   leaves and Multipoint-to-Point (MP2P) leaves to root operations.
   Peer to Peer (P2P) routes in a RPL network will generally suffer from
   some stretch since routing between 2 peers always happens via a
   common parent.

Thubert & Pylakutty      Expires April 21, 2016                 [Page 2]
Internet-Draft     Root initiated routing state in RPL      October 2015
Show full document text