RPL-BIER
draft-thubert-roll-bier-00

Document Type Active Internet-Draft (individual)
Last updated 2017-07-27
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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                                                     Cisco
Updates: 6282,6550,6775 (if approved)                      July 27, 2017
Intended status: Standards Track
Expires: January 28, 2018

                                RPL-BIER
                       draft-thubert-roll-bier-00

Abstract

   This specification extends RPL to provide unicast and multicast
   routing based on bitStrings such as used in Bit Index Explicit
   Replication and its source-routed Traffic Engineering variant, which
   correspond to RPL storing and non-storing modes respectively.

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 January 28, 2018.

Copyright Notice

   Copyright (c) 2017 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                 Expires January 28, 2018                [Page 1]
Internet-Draft                  RPL-BIER                       July 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Extensions to RFC 6550  . . . . . . . . . . . . . . . . . . .   5
     4.1.  RPL-BIER MOPs . . . . . . . . . . . . . . . . . . . . . .   6
       4.1.1.  RPL-BIER non-storing mode . . . . . . . . . . . . . .   6
       4.1.2.  RPL-BIER storing mode . . . . . . . . . . . . . . . .   6
     4.2.  BitString Information . . . . . . . . . . . . . . . . . .   7
   5.  Updating the 6LoWPAN Framework  . . . . . . . . . . . . . . .   8
     5.1.  Extensions to  RFC 6775 . . . . . . . . . . . . . . . . .   8
     5.2.  Extensions to RFC 6282  . . . . . . . . . . . . . . . . .   9
     5.3.  New Neighbor Discovery Options and Messages . . . . . . .   9
       5.3.1.  6LoWPAN ND Bit Position Option  . . . . . . . . . . .   9
       5.3.2.  Address Mapping Message . . . . . . . . . . . . . . .  10
   6.  BitString formats . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Bit-by-bit BitStrings . . . . . . . . . . . . . . . . . .  11
       6.1.1.  Allocating a Bit Position in a Bit-by-bit BitString .  12
       6.1.2.  Aggregation of Bit-by-bit BitStrings  . . . . . . . .  13
       6.1.3.  Forwarding Based on Bit-by-bit BitStrings . . . . . .  13
       6.1.4.  Reliable Multicast based on Bit-by-bit BitStrings . .  14
     6.2.  Bloom Filters . . . . . . . . . . . . . . . . . . . . . .  14
       6.2.1.  Computing and Saving Bloom Filters  . . . . . . . . .  15
       6.2.2.  Forwarding based on Bloom Filters . . . . . . . . . .  15
       6.2.3.  Hash Functions Distribution . . . . . . . . . . . . .  15
   7.  Implementation Status . . . . . . . . . . . . . . . . . . . .  15
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  16
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  18

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.  Other design constraints, such as a limited memory capacity,
   duty cycling of the LLN devices and low-power lossy transmissions,
Show full document text