Dear ROLL WG,

We're DELIGHTED to let you know that after 4 years of really hard work, the Working Group has completed the standardization of RPL, a new routing protocol designed for large-scale IPv6 constrained and harsh environments, and especially for the Internet Of Things. RPL is made of several components (RFC6550) with 4 companions RFC listed below.
RPL is the result of the hard work on the whole ROLL WG!

Even more importantly, not only other standards and alliances who adopted RPL as their routing protocol of choice (Zigbee/IP, Wave2M, …), but we are ware of more than 15 independent implementations, and we start to see actual deployments in the field. As far as we know, there is already a 3,000 and 4,000 node networks deployed with a single DAG and first results look excellent. We're hoping to see IETF I-D describing these deployments. Feel free to share on the ROLL mailing list.

The main body of work is now done, although we will undoubtedly find limitations and issues in the field, and we will go through standard process to continue improving the protocol (summarily to any other protocols) and adding extensions, in addition to the other WG items of course – This is undoubtedly a key milestone.

Set of RPL Standards:

RFC 6550: RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
RFC 6551: Routing Metrics Used for Path Calculation in Low-Power and Lossy Networks
RFC 6552: Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL)
RFC 6553: The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane Datagrams
RFC 6554: An IPv6 Routing Header for Source Routes with       the Routing Protocol for Low-Power and Lossy Networks (RPL).
 
JP, David, Adrian and Michael.
 


Begin forwarded message:

> From: rfc-editor@rfc-editor.org
> Subject: RFC 6550 on RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
> Date: March 26, 2012 1:37:19 PM GMT+02:00
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: roll@ietf.org, rfc-editor@rfc-editor.org
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 6550
> 
>        Title:      RPL: IPv6 Routing Protocol for 
>                    Low-Power and Lossy Networks 
>        Author:     T. Winter, Ed.,
>                    P. Thubert, Ed.,
>                    A. Brandt, J. Hui,
>                    R. Kelsey, P. Levis,
>                    K. Pister, R. Struik,
>                    JP. Vasseur, R. Alexander
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       March 2012
>        Mailbox:    wintert@acm.org, 
>                    pthubert@cisco.com, 
>                    abr@sdesigns.dk,  jhui@archrock.com, 
>                    kelsey@ember.com,  pal@cs.stanford.edu, 
>                    kpister@dustnetworks.com,  rstruik.ext@gmail.com, 
>                    jpv@cisco.com,  roger.alexander@cooperindustries.com
>        Pages:      157
>        Characters: 360651
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-ietf-roll-rpl-19.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc6550.txt
> 
> Low-Power and Lossy Networks (LLNs) are a class of network in which
> both the routers and their interconnect are constrained.  LLN routers
> typically operate with constraints on processing power, memory, and
> energy (battery power).  Their interconnects are characterized by
> high loss rates, low data rates, and instability.  LLNs are comprised
> of anything from a few dozen to thousands of routers.  Supported
> traffic flows include point-to-point (between devices inside the
> LLN), point-to-multipoint (from a central control point to a subset
> of devices inside the LLN), and multipoint-to-point (from devices
> inside the LLN towards a central control point).  This document
> specifies the IPv6 Routing Protocol for Low-Power and Lossy Networks
> (RPL), which provides a mechanism whereby multipoint-to-point traffic
> from devices inside the LLN towards a central control point as well
> as point-to-multipoint traffic from the central control point to the
> devices inside the LLN are supported.  Support for point-to-point
> traffic is also available.  [STANDARDS-TRACK]
> 
> This document is a product of the Routing Over Low power and Lossy networks Working Group of the IETF.
> 
> This is now a Proposed Standard Protocol.
> 
> STANDARDS TRACK: This document specifies an Internet standards track
> protocol for the Internet community,and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Internet
> Official Protocol Standards (STD 1) for the standardization state and
> status of this protocol.  Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
>