Multicast Forwarding Using Trickle
draft-ietf-roll-trickle-mcast-01

The information below is for an old version of the document
Document Type Active Internet-Draft (roll WG)
Last updated 2012-08-16 (latest revision 2012-07-13)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd Vasseur Jp
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ROLL                                                              J. Hui
Internet-Draft                                                     Cisco
Intended status: Standards Track                               R. Kelsey
Expires: January 14, 2013                                   Silicon Labs
                                                           July 13, 2012

                   Multicast Forwarding Using Trickle
                    draft-ietf-roll-trickle-mcast-01

Abstract

   Low power and Lossy Networks (LLNs) are typically composed of
   resource constrained nodes communicating over links that have dynamic
   characteristics.  Memory constraints coupled with temporal variations
   in link connectivity makes the use of topology maintenance to support
   IPv6 multicast challenging.  This document describes the use of
   Trickle to efficiently forward multicast messages without the need
   for topology maintenance.

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 14, 2013.

Copyright Notice

   Copyright (c) 2012 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

Hui & Kelsey            Expires January 14, 2013                [Page 1]
Internet-Draft        Trickle Multicast Forwarding             July 2012

   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
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Trickle Multicast Parameters . . . . . . . . . . . . . . . . .  7
   5.  Message Formats  . . . . . . . . . . . . . . . . . . . . . . .  9
     5.1.  Trickle Multicast Option . . . . . . . . . . . . . . . . .  9
     5.2.  Trickle ICMPv6 Message . . . . . . . . . . . . . . . . . . 10
       5.2.1.  Sequence List  . . . . . . . . . . . . . . . . . . . . 11
   6.  Trickle Multicast Forwarder Behavior . . . . . . . . . . . . . 12
     6.1.  Managing Sliding Windows . . . . . . . . . . . . . . . . . 12
     6.2.  Trickle Timers . . . . . . . . . . . . . . . . . . . . . . 12
     6.3.  Trickle Multicast Option Processing  . . . . . . . . . . . 13
     6.4.  Trickle ICMP Processing  . . . . . . . . . . . . . . . . . 13
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 18
     10.2. Informative References . . . . . . . . . . . . . . . . . . 18
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

Hui & Kelsey            Expires January 14, 2013                [Page 2]
Internet-Draft        Trickle Multicast Forwarding             July 2012

1.  Introduction

   The resource constraints of Low power and Lossy Networks (LLNs) may
   preclude the use of existing IPv6 multicast forwarding mechanisms.
   Such networks are typically constrained in resources (limited channel
   capacity, processing power, energy capacity, memory).  In particular
   memory constraints may limit nodes to maintaining state for only a
   small subset of neighbors.  Limited channel and energy capacity
   require protocols to remain efficient and robust even in dense
   topologies.

   Traditional IP multicast forwarding typically relies on topology
   maintenance mechanisms to efficiently forward multicast messages to
   the intended destinations.  In some cases, topology maintenance
   involves maintaining multicast trees to reach all subscribers of a
Show full document text