draft-ietf-roll-useofrplinfo-39.txt   draft-ietf-roll-useofrplinfo-40.txt 
ROLL Working Group M. Robles ROLL Working Group M. Robles
Internet-Draft UTN-FRM/Aalto Internet-Draft UTN-FRM/Aalto
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: December 10, 2020 P. Thubert Expires: December 27, 2020 P. Thubert
Cisco Cisco
June 8, 2020 June 25, 2020
Using RPI Option Type, Routing Header for Source Routes and IPv6-in-IPv6 Using RPI Option Type, Routing Header for Source Routes and IPv6-in-IPv6
encapsulation in the RPL Data Plane encapsulation in the RPL Data Plane
draft-ietf-roll-useofrplinfo-39 draft-ietf-roll-useofrplinfo-40
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 RFC6553 (RPI Option Type), RFC6554 enumerates the cases where RFC6553 (RPI Option Type), RFC6554
(Routing Header for Source Routes) and IPv6-in-IPv6 encapsulation is (Routing Header for Source Routes) and IPv6-in-IPv6 encapsulation is
required in data plane. This analysis provides the basis on which to required in data plane. This analysis provides the basis on which to
design efficient compression of these headers. This document updates design efficient compression of these headers. This document updates
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 December 10, 2020. This Internet-Draft will expire on December 27, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 14, line 22 skipping to change at page 14, line 22
letters above the nodes are there so that they may be referenced in letters above the nodes are there so that they may be referenced in
subsequent sections. In the figure, 6LR represents a full router subsequent sections. In the figure, 6LR represents a full router
node. The 6LN is a RPL aware router, or host (as a leaf). node. The 6LN is a RPL aware router, or host (as a leaf).
Additionally, for simplification purposes, it is supposed that the Additionally, for simplification purposes, it is supposed that the
6LBR has direct access to Internet and is the root of the DODAG, thus 6LBR has direct access to Internet and is the root of the DODAG, thus
the 6BBR is not present in the figure. the 6BBR is not present in the figure.
The 6LN leaves (RAL) marked as (F, H and I) are RPL nodes with no The 6LN leaves (RAL) marked as (F, H and I) are RPL nodes with no
children hosts. children hosts.
The leaves marked as RUL (G and J) are devices which do not speak RPL The leaves marked as RUL (G and J) are devices that do not speak RPL
at all (not-RPL-aware), but uses Router-Advertisements, 6LowPAN DAR/ at all (not-RPL-aware), but use Router-Advertisements, 6LowPAN DAR/
DAC and 6LoWPAN ND only to participate in the network [RFC8505]. In DAC and 6LoWPAN ND only to participate in the network [RFC8505]. In
the document these leaves (G and J) are also referred to as a RUL. the document these leaves (G and J) are also referred to as a RUL.
The 6LBR ("A") in the figure is the root of the Global DODAG. The 6LBR ("A") in the figure is the root of the Global DODAG.
+------------+ +------------+
| INTERNET ----------+ | INTERNET ----------+
| | | | | |
+------------+ | +------------+ |
| |
skipping to change at page 24, line 41 skipping to change at page 24, line 41
RUL (IPv6 src node) --> 6LR_1 --> 6LR_i --> root (6LBR) RUL (IPv6 src node) --> 6LR_1 --> 6LR_i --> root (6LBR)
For example, a communication flow could be: Node G (RUL) --> Node E For example, a communication flow could be: Node G (RUL) --> Node E
(6LR_1)--> Node B (6LR_i)--> Node A root(6LBR) (6LR_1)--> Node B (6LR_i)--> Node A root(6LBR)
6LR_i represents the intermediate routers from the source (RUL) to 6LR_i represents the intermediate routers from the source (RUL) to
the destination (6LBR), 1 <= i <= n, where n is the total number of the destination (6LBR), 1 <= i <= n, where n is the total number of
routers (6LR) that the packet goes through from the RUL to the 6LBR. routers (6LR) that the packet goes through from the RUL to the 6LBR.
When the packet arrives from the RUL (Node G) to 6LR_1 (Node E), the When the packet arrives from the RUL (Node G) to 6LR_1 (Node E), the
6LR_1 will insert encapsulate the packet in an IPv6-in-IPv6 header 6LR_1 will encapsulate the packet in an IPv6-in-IPv6 header with an
and prepend an RPI. The IPv6-in-IPv6 header is addressed to the root RPI. The IPv6-in-IPv6 header is addressed to the root (Node A). The
(Node A). The root removes the header and processes the packet. root removes the header and processes the packet.
The Figure 12 shows the table that summarizes what headers are needed The Figure 12 shows the table that summarizes what headers are needed
for this use case where the IPv6-in-IPv6 header is addressed to the for this use case where the IPv6-in-IPv6 header is addressed to the
root (Node A). root (Node A).
+-----------+------+--------------+----------------+-----------------+ +-----------+------+--------------+----------------+-----------------+
| Header | RUL | 6LR_1 | 6LR_i | 6LBR dst | | Header | RUL | 6LR_1 | 6LR_i | 6LBR dst |
| | src | | | | | | src | | | |
| | node | | | | | | node | | | |
+-----------+------+--------------+----------------+-----------------+ +-----------+------+--------------+----------------+-----------------+
skipping to change at page 32, line 24 skipping to change at page 32, line 24
6LR_id (Node E) represents the intermediate routers from the Root 6LR_id (Node E) represents the intermediate routers from the Root
(Node B) to destination RUL (Node G). In this case, 1 <= id <= m, (Node B) to destination RUL (Node G). In this case, 1 <= id <= m,
where m is the total number of routers (6LR) that the packet goes where m is the total number of routers (6LR) that the packet goes
through from the Root down to the destination RUL. through from the Root down to the destination RUL.
In this case, the packet from the RAL goes to 6LBR because the route In this case, the packet from the RAL goes to 6LBR because the route
to the RUL is not injected into the RPL-SM. Thus, the RAL inserts an to the RUL is not injected into the RPL-SM. Thus, the RAL inserts an
RPI (RPI1) addressed to the root(6LBR). The root does not removes RPI (RPI1) addressed to the root(6LBR). The root does not removes
the RPI1 (the root cannot remove an RPI if there is no the RPI1 (the root cannot remove an RPI if there is no
encapsulation). The root inserts an RPI2 encapsulated to the 6LR encapsulation). The root inserts an IPv6-IPv6 encapsulation with an
parent of the RUL, which removes the RPI2 before pasing the packet to RPI2 and sends it to the 6LR parent of the RUL, which removes the
the RUL. encapsulation and RPI2 before passing the packet to the RUL.
The Figure 19 summarizes what headers are needed for this use case. The Figure 19 summarizes what headers are needed for this use case.
+----------+-------+-------+---------+---------+---------+---------+ +----------+-------+-------+---------+---------+---------+---------+
| Header | RAL |6LR_ia | 6LBR | 6LR_id | 6LR_m | RUL | | Header | RAL |6LR_ia | 6LBR | 6LR_id | 6LR_m | RUL |
| | src | | | | | dst | | | src | | | | | dst |
| | node | | | | | node | | | node | | | | | node |
+----------+-------+-------+---------+---------+---------+---------+ +----------+-------+-------+---------+---------+---------+---------+
| Added | | | IP6-IP6 | -- | -- | -- | | Added | | | IP6-IP6 | -- | -- | -- |
| headers | RPI1 | -- | (RPI2) | | | | | headers | RPI1 | -- | (RPI2) | | | |
skipping to change at page 61, line 18 skipping to change at page 61, line 18
in progress), March 2020. in progress), March 2020.
[I-D.ietf-6tisch-dtsecurity-zerotouch-join] [I-D.ietf-6tisch-dtsecurity-zerotouch-join]
Richardson, M., "6tisch Zero-Touch Secure Join protocol", Richardson, M., "6tisch Zero-Touch Secure Join protocol",
draft-ietf-6tisch-dtsecurity-zerotouch-join-04 (work in draft-ietf-6tisch-dtsecurity-zerotouch-join-04 (work in
progress), July 2019. progress), July 2019.
[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-24 (work in progress), March 2020. plane-25 (work in progress), June 2020.
[I-D.ietf-anima-bootstrapping-keyinfra] [I-D.ietf-anima-bootstrapping-keyinfra]
Pritikin, M., Richardson, M., Eckert, T., Behringer, M., Pritikin, M., Richardson, M., Eckert, T., Behringer, M.,
and K. Watsen, "Bootstrapping Remote Secure Key and K. Watsen, "Bootstrapping Remote Secure Key
Infrastructures (BRSKI)", draft-ietf-anima-bootstrapping- Infrastructures (BRSKI)", draft-ietf-anima-bootstrapping-
keyinfra-41 (work in progress), April 2020. keyinfra-41 (work in progress), April 2020.
[I-D.ietf-intarea-tunnels] [I-D.ietf-intarea-tunnels]
Touch, J. and M. Townsley, "IP Tunnels in the Internet Touch, J. and M. Townsley, "IP Tunnels in the Internet
Architecture", draft-ietf-intarea-tunnels-10 (work in Architecture", draft-ietf-intarea-tunnels-10 (work in
progress), September 2019. progress), September 2019.
[I-D.ietf-roll-unaware-leaves] [I-D.ietf-roll-unaware-leaves]
Thubert, P. and M. Richardson, "Routing for RPL Leaves", Thubert, P. and M. Richardson, "Routing for RPL Leaves",
draft-ietf-roll-unaware-leaves-15 (work in progress), draft-ietf-roll-unaware-leaves-18 (work in progress), June
April 2020. 2020.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <https://www.rfc-editor.org/info/rfc2460>. December 1998, <https://www.rfc-editor.org/info/rfc2460>.
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in
IPv6 Specification", RFC 2473, DOI 10.17487/RFC2473, IPv6 Specification", RFC 2473, DOI 10.17487/RFC2473,
December 1998, <https://www.rfc-editor.org/info/rfc2473>. December 1998, <https://www.rfc-editor.org/info/rfc2473>.
[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
 End of changes. 9 change blocks. 
15 lines changed or deleted 15 lines changed or added

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