--- 1/draft-ietf-roll-routing-dispatch-03.txt 2016-10-26 09:15:55.737986247 -0700 +++ 2/draft-ietf-roll-routing-dispatch-04.txt 2016-10-26 09:15:55.809988012 -0700 @@ -1,23 +1,23 @@ roll P. Thubert, Ed. Internet-Draft Cisco Intended status: Standards Track C. Bormann -Expires: April 28, 2017 Uni Bremen TZI +Expires: April 29, 2017 Uni Bremen TZI L. Toutain IMT-TELECOM Bretagne R. Cragie ARM - October 25, 2016 + October 26, 2016 6LoWPAN Routing Header - draft-ietf-roll-routing-dispatch-03 + draft-ietf-roll-routing-dispatch-04 Abstract This specification introduces a new 6LoWPAN dispatch type for use in 6LoWPAN Route-Over topologies, that initially covers the needs of RPL (RFC6550) data packets compression. Using this dispatch type, this specification defines a method to compress RPL Option (RFC6553) information and Routing Header type 3 (RFC6554), an efficient IP-in- IP technique and is extensible for more applications. @@ -29,21 +29,21 @@ 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 April 28, 2017. + This Internet-Draft will expire on April 29, 2017. 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 @@ -194,30 +194,30 @@ Additionally, in the case of the Non-Storing Mode of Operation (MOP), RPL requires a Source Routing Header (SRH) in all packets that are routed down a RPL graph. for that purpose, the "IPv6 Routing Header for Source Routes with RPL" [RFC6554] specification defines the type 3 Routing Header for IPv6 (RH3). ------+--------- ^ | Internet | | | Native IPv6 +-----+ | - | | Border Router (RPL Root) ^ | ^ + | | Border Router (RPL Root) + | + | | | | | - +-----+ | | | IPv6 in - | | | | IPv6 - o o o o | | | plus - o o o o o o o o o | | | RPL SRH - o o o o o o o o o o | | | + +-----+ | | | tunneled + | | | | using + o o o o | | | IPv6-in- + o o o o o o o o o | | | IPv6 and + o o o o o o o o o o | | | RPL SRH o o o o o o o o o | | | - o o o o o o o o v v v - o o o o + o o o o o o o o | | | + o o o o + v + LLN Figure 2: IP-in-IP Encapsulation within the LLN. With Non-Storing RPL, even if the source is a node in the same LLN, the packet must first reach up the graph to the root so that the root can insert the SRH to go down the graph. In any fashion, whether the packet was originated in a node in the LLN or outside the LLN, and regardless of whether the packet stays within the LLN or not, as long as the source of the packet is not the root itself, the source- @@ -1312,22 +1312,22 @@ of IEEE 802.15.4", draft-ietf-6tisch-architecture-10 (work in progress), June 2016. [I-D.ietf-roll-useofrplinfo] Robles, I., Richardson, M., and P. Thubert, "When to use RFC 6553, 6554 and IPv6-in-IPv6", draft-ietf-roll- useofrplinfo-09 (work in progress), October 2016. [I-D.thubert-6lo-forwarding-fragments] Thubert, P. and J. Hui, "LLN Fragment Forwarding and - Recovery", draft-thubert-6lo-forwarding-fragments-02 (work - in progress), November 2014. + Recovery", draft-thubert-6lo-forwarding-fragments-03 (work + in progress), October 2016. [RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C. Bormann, "Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC 6775, DOI 10.17487/RFC6775, November 2012, . [RFC7102] Vasseur, JP., "Terms Used in Routing for Low-Power and Lossy Networks", RFC 7102, DOI 10.17487/RFC7102, January 2014, .