Skip to main content

Status update for WG

ROLL focuses on IPv6 routing for Low Power and Lossy Networks (LLN). It maintains and improves the protocols already developed, including RPL and MPL.

In draft-ietf-roll-rpl-observations, we describe RPL protocol design issues, their consequences and some implementation choices, with the goal of producing new documents that solve those issues.

One such limitation is the exhaustion of the Mode of Operation field (MOP) of RPL. draft-ietf-roll-mopex-cap aims at extending the MOP field and adding the notion of Capabilities to RPL networks.

Another improvement being worked on is an efficient route invalidation messaging scheme for RPL. draft-ietf-roll-efficient-npdao, currently in IESG processing, describes such ​a proposal.

Additionally, we are working on a proposal allowing a RPL Root to install and maintain Projected routes within the RPL Domain (see draft-ietf-roll-dao-projection), and a proposal to extend secure network enrollment (BRSKI) to RPL networks (see draft-ietf-roll-enrollment-priority).

Another area of improvement is the routing for RPL-unaware nodes through a RPL domain. Proposals can be found in draft-ietf-roll-unaware-leaves.

The WG is also putting the last touch on draft-ietf-roll-nsa-extension, that describes a new routing objective function for RPL, based on a metric that represents the node’s remaining traffic capacity.

New work includes a proposal for reliably eliding RPL control information and querying that information, (see draft-thubert-roll-eliding-dio-information) and a proposal to signal that RFC8138 compression is turned on (see draft-thubert-roll-turnon-rfc8138).

Finally, also in IESG processing, draft-ietf-roll-useofrplinfo describes use cases for RPL data plane features, notably the need for IP-in-IP incapsulation, in the various Modes Of Operation and for the various traffics that are carried across a RPL domain.

[Last Updated: Nov 08, 2019.]