Constrained-Cast: Source-Routed Multicast for RPL
draft-ietf-roll-ccast-01

Document Type Active Internet-Draft (roll WG)
Last updated 2017-10-30
Replaces draft-bergmann-bier-ccast
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Roll Working Group                                           O. Bergmann
Internet-Draft                                                C. Bormann
Intended status: Standards Track                               S. Gerdes
Expires: May 3, 2018                             Universitaet Bremen TZI
                                                                 H. Chen
                                                     Huawei Technologies
                                                        October 30, 2017

           Constrained-Cast: Source-Routed Multicast for RPL
                        draft-ietf-roll-ccast-01

Abstract

   This specification defines a protocol for forwarding multicast
   traffic in a constrained node network employing the RPL routing
   protocol in non-storing mode.

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 May 3, 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

Bergmann, et al.           Expires May 3, 2018                  [Page 1]
Internet-Draft              Constrained-Cast                October 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  The BIER Approach . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The Constrained-Cast Approach . . . . . . . . . . . . . . . .   3
   4.  False Positives . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Protocol  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Multicast Listener Advertisement Object (MLAO)  . . . . .   4
     5.2.  Routing Header  . . . . . . . . . . . . . . . . . . . . .   5
   6.  Implementation  . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Benefits  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  ICMPv6 Parameter Registration . . . . . . . . . . . . . .   8
     9.2.  Critical 6LowPAN Routing Header Type Registration . . . .   8
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   8
     11.2.  Informative References . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   As defined in [RFC6550], RPL Multicast assumes that the RPL network
   operates in Storing Mode.  Multicast DAOs are used to indicate
   subscription to multicast address to a parent; these DAOs percolate
   up and create bread-crumbs.  This specification, although part of RFC
   6550, appears to be incomplete and untested.  More importantly,
   Storing Mode is not in use in constrained node networks outside
   research operating environments.

   The present specification addresses multicast forwarding for RPL
   networks in the much more common Non-Storing Mode.  Non-Storing is
   based on the root node adding source-routing information to downward
   packets.  Evidently, to make this work, RPL multicast needs to
   source-route multicast packets.  A source route here is a list of
   identifiers to instruct forwarders to relay the respective IP
   datagram.

   As every forwarder in an IP-based constrained node network has at
   least one network interface, it is straight-forward to use the
   address of an outgoing interface as identifiers in this source-route.
Show full document text