Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Multicast Protocol for Low-Power and Lossy Networks (MPL) (RFC7731)

IP.com Disclosure Number: IPCOM000245238D
Original Publication Date: 2016-Feb-01
Included in the Prior Art Database: 2016-Feb-19
Document File: 58 page(s) / 63K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Hui: AUTHOR [+2]

Abstract

Low-Power and Lossy Networks (LLNs) typically operate with strict resource constraints in communication, computation, memory, and energy. Such resource constraints may preclude the use of existing IPv6 multicast routing and forwarding mechanisms. Traditional IP multicast delivery typically relies on topology maintenance mechanisms to discover and maintain routes to all subscribers of a multicast group (e.g., [RFC3973] [RFC4601]). However, maintaining such topologies in LLNs is costly and may not be feasible given the available resources.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Internet Engineering Task Force (IETF)                            J. Hui Request for Comments: 7731                                     Nest Labs Category: Standards Track                                      R. Kelsey ISSN: 2070-1721                                             Silicon Labs                                                            February 2016

        Multicast Protocol for Low-Power and Lossy Networks (MPL)

Abstract

   This document specifies the Multicast Protocol for Low-Power and    Lossy Networks (MPL), which provides IPv6 multicast forwarding in    constrained networks.  MPL avoids the need to construct or maintain    any multicast forwarding topology, disseminating messages to all MPL    Forwarders in an MPL Domain.

   MPL has two modes of operation.  One mode uses the Trickle algorithm    to manage control-plane and data-plane message transmissions and is    applicable for deployments with few multicast sources.  The other    mode uses classic flooding.  By providing both modes and    parameterization of the Trickle algorithm, an MPL implementation can    be used in a variety of multicast deployments and can trade between    dissemination latency and transmission efficiency.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7731.

Hui & Kelsey                 Standards Track                    [Page 1]
 RFC 7731                           MPL                     February 2016

 Copyright Notice

   Copyright (c) 2016 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    descr...