Low power and Lossy Networks (LLNs ) are made up of many embedded devices with limited power, memory, and processing resources. They are interconnected by a variety of links, such as IEEE 802.15.4, Bluetooth, Low Power WiFi, wired or other low power PLC (Powerline Communication) links. LLNs are transitioning to an end-to-end IP-based solution to avoid the problem of non-interoperable networks interconnected by protocol translation gateways and proxies. RFC7102 discusses ROLL specific aspects of LLNs, and RFC7228 provides additional terminology for constrained devices. RFC 5548, 5673, 5826, and 5876 describe the requirements for LLNs from several application perspectives. The Working Group has focused on routing solutions for the areas: connected home, building, and urban sensor networks. It has developed a Framework that takes into consideration various aspects including high reliability in the presence of time varying loss characteristics and connectivity while permitting low-power operation with very modest memory and CPU pressure in networks potentially comprising a very large number (several thousands) of nodes. The Working Group continues to focus on routing issues for LLN and to maintain, improve and streamline the protocols already developed, including RPL and MPL. The focus is on IPv6 work only. The Working Group will pay particular attention to routing security and manageability (e.g., self routing configuration) issues. It will also need to consider the transport characteristic the routing protocol messages will experience. ROLL will coordinate closely with the working groups in other areas that focus on constrained networks and/or constrained nodes, such as 6lo (Int), lwig (Int) and CoRE (App). Other working groups such as PIM (rtg), BIER (rtg) and MANET (rtg) will be consulted as needed. The Working group will align with the 6man (Int) WG when needed. Work Items are: - Guidance in using RFC6553, RFC6554, and IPv6-in-IPv6 encapsulation. - Additional protocol elements to reduce packet size and the amount of required routing states - Automatic selection of MPL forwarders to reduce message replication. - Data models for RPL and MPL management. - Multicast enhancements algorithms. Milestones Date Milestone September 2018 Recharter WG or close July 2018 Initial submission of a solution for draft-jadhav-roll-no-path-dao-ps to IESG November 2017 Initial submission of draft-satish-roll-aodv-rpl to IESG November 2017 Initial submission of draft-gundogan-roll-dis-modifications to IESG July 2017 Initial submission of draft-bergmann-bier-ccast to IESG July 2017 Initial submission of draft-vanderstok-roll-mpl-forw-select to IESG March 2017 Initial submission of draft-vanderstok-roll-mpl-yang to IESG March 2017 Initial submission of draft-thubert-roll-dao-projection to IESG November 2016 Initial Submission of the draft about when to use RFC6553, RFC6554, and IPv6-in-IPv6 encapsulation Draft-ietf-roll-useofrplinfo to the IESG.