draft-ietf-roll-useofrplinfo-22.txt   draft-ietf-roll-useofrplinfo-23.txt 
ROLL Working Group M. Robles ROLL Working Group M. Robles
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 6553, 6550, 8138 (if approved) M. Richardson Updates: 6553, 6550, 8138 (if approved) M. Richardson
Intended status: Standards Track SSW Intended status: Standards Track SSW
Expires: September 2, 2018 P. Thubert Expires: November 2, 2018 P. Thubert
Cisco Cisco
March 1, 2018 May 1, 2018
When to use RFC 6553, 6554 and IPv6-in-IPv6 When to use RFC 6553, 6554 and IPv6-in-IPv6
draft-ietf-roll-useofrplinfo-22 draft-ietf-roll-useofrplinfo-23
Abstract Abstract
This document looks at different data flows through LLN (Low-Power This document looks at different data flows through LLN (Low-Power
and Lossy Networks) where RPL (IPv6 Routing Protocol for Low-Power and Lossy Networks) where RPL (IPv6 Routing Protocol for Low-Power
and Lossy Networks) is used to establish routing. The document and Lossy Networks) is used to establish routing. The document
enumerates the cases where RFC 6553, RFC 6554 and IPv6-in-IPv6 enumerates the cases where RFC 6553, RFC 6554 and IPv6-in-IPv6
encapsulation is required. This analysis provides the basis on which encapsulation is required. This analysis provides the basis on which
to design efficient compression of these headers. This document to design efficient compression of these headers. This document
updates RFC 6553 adding a change to the RPL Option Type. updates RFC 6553 adding a change to the RPL Option Type.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 2, 2018. This Internet-Draft will expire on November 2, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 50 skipping to change at page 2, line 50
6.3. Storing Mode: Interaction between Leaf and Leaf . . . . . 21 6.3. Storing Mode: Interaction between Leaf and Leaf . . . . . 21
6.3.1. SM: Example of Flow from RPL-aware-leaf to RPL-aware- 6.3.1. SM: Example of Flow from RPL-aware-leaf to RPL-aware-
leaf . . . . . . . . . . . . . . . . . . . . . . . . 21 leaf . . . . . . . . . . . . . . . . . . . . . . . . 21
6.3.2. SM: Example of Flow from RPL-aware-leaf to non-RPL- 6.3.2. SM: Example of Flow from RPL-aware-leaf to non-RPL-
aware-leaf . . . . . . . . . . . . . . . . . . . . . 22 aware-leaf . . . . . . . . . . . . . . . . . . . . . 22
6.3.3. SM: Example of Flow from not-RPL-aware-leaf to RPL- 6.3.3. SM: Example of Flow from not-RPL-aware-leaf to RPL-
aware-leaf . . . . . . . . . . . . . . . . . . . . . 23 aware-leaf . . . . . . . . . . . . . . . . . . . . . 23
6.3.4. SM: Example of Flow from not-RPL-aware-leaf to not- 6.3.4. SM: Example of Flow from not-RPL-aware-leaf to not-
RPL-aware-leaf . . . . . . . . . . . . . . . . . . . 24 RPL-aware-leaf . . . . . . . . . . . . . . . . . . . 24
7. Non Storing mode . . . . . . . . . . . . . . . . . . . . . . 25 7. Non Storing mode . . . . . . . . . . . . . . . . . . . . . . 25
7.1. Non-Storing Mode: Interaction between Leaf and Root . . . 26 7.1. Non-Storing Mode: Interaction between Leaf and Root . . . 27
7.1.1. Non-SM: Example of Flow from RPL-aware-leaf to root . 27 7.1.1. Non-SM: Example of Flow from RPL-aware-leaf to root . 27
7.1.2. Non-SM: Example of Flow from root to RPL-aware-leaf . 27 7.1.2. Non-SM: Example of Flow from root to RPL-aware-leaf . 27
7.1.3. Non-SM: Example of Flow from root to not-RPL-aware- 7.1.3. Non-SM: Example of Flow from root to not-RPL-aware-
leaf . . . . . . . . . . . . . . . . . . . . . . . . 28 leaf . . . . . . . . . . . . . . . . . . . . . . . . 28
7.1.4. Non-SM: Example of Flow from not-RPL-aware-leaf to 7.1.4. Non-SM: Example of Flow from not-RPL-aware-leaf to
root . . . . . . . . . . . . . . . . . . . . . . . . 29 root . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2. Non-Storing Mode: Interaction between Leaf and Internet . 30 7.2. Non-Storing Mode: Interaction between Leaf and Internet . 30
7.2.1. Non-SM: Example of Flow from RPL-aware-leaf to 7.2.1. Non-SM: Example of Flow from RPL-aware-leaf to
Internet . . . . . . . . . . . . . . . . . . . . . . 30 Internet . . . . . . . . . . . . . . . . . . . . . . 30
7.2.2. Non-SM: Example of Flow from Internet to RPL-aware- 7.2.2. Non-SM: Example of Flow from Internet to RPL-aware-
skipping to change at page 20, line 44 skipping to change at page 20, line 44
Internet --> root (6LBR) --> 6LR_i --> not-RPL-aware-leaf (IPv6) Internet --> root (6LBR) --> 6LR_i --> not-RPL-aware-leaf (IPv6)
For example, a communication flow could be: Internet --> Node A For example, a communication flow could be: Internet --> Node A
root(6LBR) --> Node B --> Node E --> Node G root(6LBR) --> Node B --> Node E --> Node G
The 6LBR will have to add an RPI header within an IP-in-IP header. The 6LBR will have to add an RPI header within an IP-in-IP header.
The IP-in-IP is addressed to the not-RPL-aware-leaf, leaving the RPI The IP-in-IP is addressed to the not-RPL-aware-leaf, leaving the RPI
inside. inside.
Note that there is a requirement that the final node be able to Note that there is a requirement that the final node be able to
remove one or more IPIP headers which are all addressed to it. remove one or more IP-in-IP headers which are all addressed to it,
(EDNOTE: this should go into [I-D.ietf-6man-rfc6434-bis]) mentioned in [I-D.thubert-roll-unaware-leaves] :
"RPL data packets are often encapsulated using IP in IP. The 6LN
MUST be able to decapsulate a packet when it is the destination of
the outer header and process correctly the inner header."
The 6LBR MAY set the flow label on the inner IP-in-IP header to zero The 6LBR MAY set the flow label on the inner IP-in-IP header to zero
in order to aid in compression. in order to aid in compression.
+-----------+----------+---------------+---------------+------------+ +-----------+----------+---------------+---------------+------------+
| Header | Internet | 6LBR | 6LR_i | IPv6 | | Header | Internet | 6LBR | 6LR_i | IPv6 |
+-----------+----------+---------------+---------------+------------+ +-----------+----------+---------------+---------------+------------+
| Inserted | -- | IP-in-IP(RPI) | -- | -- | | Inserted | -- | IP-in-IP(RPI) | -- | -- |
| headers | | | | | | headers | | | | |
| Removed | -- | -- | -- | -- | | Removed | -- | -- | -- | -- |
| headers | | | | | | headers | | | | |
skipping to change at page 23, line 21 skipping to change at page 23, line 23
6LN. 6LN.
This situation is identical to the previous situation Section 6.3.1 This situation is identical to the previous situation Section 6.3.1
+-----------+------+--------+---------------+--------+--------------+ +-----------+------+--------+---------------+--------+--------------+
| Header | 6LN | 6LR_ia | 6LR_x(common | 6LR_id | IPv6 | | Header | 6LN | 6LR_ia | 6LR_x(common | 6LR_id | IPv6 |
| | src | | parent) | | | | | src | | parent) | | |
+-----------+------+--------+---------------+--------+--------------+ +-----------+------+--------+---------------+--------+--------------+
| Inserted | RPI | -- | -- | -- | -- | | Inserted | RPI | -- | -- | -- | -- |
| headers | | | | | | | headers | | | | | |
| Removed | -- | -- | -- | -- | RPI | | Removed | -- | -- | -- | -- | -- |
| headers | | | | | | | headers | | | | | |
| Re-added | -- | -- | -- | -- | -- | | Re-added | -- | -- | -- | -- | -- |
| headers | | | | | | | headers | | | | | |
| Modified | -- | RPI | RPI | RPI | -- | | Modified | -- | RPI | RPI | RPI | -- |
| headers | | | | | | | headers | | | | | |
| Untouched | -- | -- | -- | -- | RPI(Ignored) | | Untouched | -- | -- | -- | -- | RPI(Ignored) |
| headers | | | | | | | headers | | | | | |
+-----------+------+--------+---------------+--------+--------------+ +-----------+------+--------+---------------+--------+--------------+
Storing: Summary of the use of headers for RPL-aware-leaf to non-RPL- Storing: Summary of the use of headers for RPL-aware-leaf to non-RPL-
skipping to change at page 45, line 7 skipping to change at page 45, line 7
>145k hacked cameras", September 2016, >145k hacked cameras", September 2016,
<http://arstechnica.com/security/2016/09/botnet-of-145k- <http://arstechnica.com/security/2016/09/botnet-of-145k-
cameras-reportedly-deliver-internets-biggest-ddos-ever/>. cameras-reportedly-deliver-internets-biggest-ddos-ever/>.
[I-D.ietf-6lo-backbone-router] [I-D.ietf-6lo-backbone-router]
Thubert, P., "IPv6 Backbone Router", draft-ietf-6lo- Thubert, P., "IPv6 Backbone Router", draft-ietf-6lo-
backbone-router-06 (work in progress), February 2018. backbone-router-06 (work in progress), February 2018.
[I-D.ietf-6man-rfc6434-bis] [I-D.ietf-6man-rfc6434-bis]
Chown, T., Loughney, J., and T. Winters, "IPv6 Node Chown, T., Loughney, J., and T. Winters, "IPv6 Node
Requirements", draft-ietf-6man-rfc6434-bis-05 (work in Requirements", draft-ietf-6man-rfc6434-bis-08 (work in
progress), February 2018. progress), March 2018.
[I-D.ietf-6tisch-dtsecurity-secure-join] [I-D.ietf-6tisch-dtsecurity-secure-join]
Richardson, M., "6tisch Secure Join protocol", draft-ietf- Richardson, M., "6tisch Secure Join protocol", draft-ietf-
6tisch-dtsecurity-secure-join-01 (work in progress), 6tisch-dtsecurity-secure-join-01 (work in progress),
February 2017. February 2017.
[I-D.ietf-anima-autonomic-control-plane] [I-D.ietf-anima-autonomic-control-plane]
Eckert, T., Behringer, M., and S. Bjarnason, "An Autonomic Eckert, T., Behringer, M., and S. Bjarnason, "An Autonomic
Control Plane (ACP)", draft-ietf-anima-autonomic-control- Control Plane (ACP)", draft-ietf-anima-autonomic-control-
plane-13 (work in progress), December 2017. plane-13 (work in progress), December 2017.
[I-D.ietf-anima-bootstrapping-keyinfra] [I-D.ietf-anima-bootstrapping-keyinfra]
Pritikin, M., Richardson, M., Behringer, M., Bjarnason, Pritikin, M., Richardson, M., Behringer, M., Bjarnason,
S., and K. Watsen, "Bootstrapping Remote Secure Key S., and K. Watsen, "Bootstrapping Remote Secure Key
Infrastructures (BRSKI)", draft-ietf-anima-bootstrapping- Infrastructures (BRSKI)", draft-ietf-anima-bootstrapping-
keyinfra-11 (work in progress), February 2018. keyinfra-15 (work in progress), April 2018.
[I-D.thubert-roll-unaware-leaves]
Thubert, P., "Routing for RPL Leaves", draft-thubert-roll-
unaware-leaves-04 (work in progress), March 2018.
[RFC4192] Baker, F., Lear, E., and R. Droms, "Procedures for [RFC4192] Baker, F., Lear, E., and R. Droms, "Procedures for
Renumbering an IPv6 Network without a Flag Day", RFC 4192, Renumbering an IPv6 Network without a Flag Day", RFC 4192,
DOI 10.17487/RFC4192, September 2005, DOI 10.17487/RFC4192, September 2005,
<https://www.rfc-editor.org/info/rfc4192>. <https://www.rfc-editor.org/info/rfc4192>.
[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Control Message Protocol (ICMPv6) for the Internet Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification", STD 89, Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006, RFC 4443, DOI 10.17487/RFC4443, March 2006,
 End of changes. 10 change blocks. 
11 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/