Skip to content

Commit

Permalink
Carles's review
Browse files Browse the repository at this point in the history
  • Loading branch information
pthubert committed Aug 5, 2020
1 parent 13480d5 commit 9f5b90e
Show file tree
Hide file tree
Showing 2 changed files with 103 additions and 90 deletions.
134 changes: 67 additions & 67 deletions roll-turnon-rfc8138.txt
Expand Up @@ -5,12 +5,12 @@
ROLL P. Thubert, Ed.
Internet-Draft L. Zhao
Updates: 8138 (if approved) Cisco Systems
Intended status: Standards Track 21 July 2020
Expires: 22 January 2021
Intended status: Standards Track 5 August 2020
Expires: 6 February 2021


A RPL DODAG Configuration Option for the 6LoWPAN Routing Header
draft-ietf-roll-turnon-rfc8138-09
draft-ietf-roll-turnon-rfc8138-10

Abstract

Expand All @@ -34,7 +34,7 @@ Status of This Memo
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 22 January 2021.
This Internet-Draft will expire on 6 February 2021.

Copyright Notice

Expand All @@ -53,9 +53,9 @@ Copyright Notice



Thubert & Zhao Expires 22 January 2021 [Page 1]
Thubert & Zhao Expires 6 February 2021 [Page 1]

Internet-Draft Turn On 6LoRH July 2020
Internet-Draft Turn On 6LoRH August 2020


Table of Contents
Expand All @@ -73,8 +73,8 @@ Table of Contents
5.3. Rolling Back . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
9. Normative References . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
9. Normative References . . . . . . . . . . . . . . . . . . . . 8
10. Informative References . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9

Expand Down Expand Up @@ -109,31 +109,31 @@ Table of Contents



Thubert & Zhao Expires 22 January 2021 [Page 2]
Thubert & Zhao Expires 6 February 2021 [Page 2]

Internet-Draft Turn On 6LoRH July 2020
Internet-Draft Turn On 6LoRH August 2020


2. Terminology

2.1. References

The Terminology used in this document is consistent with and
The terminology used in this document is consistent with and
incorporates that described in "Terms Used in Routing for Low-Power
and Lossy Networks (LLNs)" [RFC7102]. Other terms in use in LLNs are
found in "Terminology for Constrained-Node Networks" [RFC7228].

"RPL", the "RPL Packet Information" (RPI), "RPL Instance" (indexed by
a RPLInstanceID) are defined in "RPL: IPv6 Routing Protocol for
Low-Power and Lossy Networks" [RFC6550]. The RPI is the abstract
information that RPL defines to be placed in data packets, e.g., as
the RPL Option [RFC6553] within the IPv6 Hop-By-Hop Header. By
extension the term "RPI" is often used to refer to the RPL Option
"RPL", the "RPL Packet Information" (RPI), and "RPL Instance"
(indexed by a RPLInstanceID) are defined in "RPL: IPv6 Routing
Protocol for Low-Power and Lossy Networks" [RFC6550]. The RPI is the
abstract information that RPL defines to be placed in data packets,
e.g., as the RPL Option [RFC6553] within the IPv6 Hop-By-Hop Header.
By extension the term "RPI" is often used to refer to the RPL Option
itself. The DODAG Information Solicitation (DIS), Destination
Advertisement Object (DAO) and DODAG Information Object (DIO)
messages are also specified in [RFC6550].

This document uses the terms RPL-Unaware Leaf (RUL) and RPL Aware
This document uses the terms RPL-Unaware Leaf (RUL) and RPL-Aware
Leaf (RAL) consistently with "Using RPI Option Type, Routing Header
for Source Routes and IPv6-in-IPv6 encapsulation in the RPL Data
Plane" [USEofRPLinfo]. The term RPL-Aware Node (RAN) refers to a
Expand Down Expand Up @@ -165,9 +165,9 @@ Internet-Draft Turn On 6LoRH July 2020



Thubert & Zhao Expires 22 January 2021 [Page 3]
Thubert & Zhao Expires 6 February 2021 [Page 3]

Internet-Draft Turn On 6LoRH July 2020
Internet-Draft Turn On 6LoRH August 2020


2.3. Requirements Language
Expand Down Expand Up @@ -214,24 +214,24 @@ Internet-Draft Turn On 6LoRH July 2020
is set, it is transparently flooded to all the nodes in the DODAG.

Section 6.3.1 of [RFC6550] defines a 3-bit Mode of Operation (MOP) in
the DIO Base Object. For MOP values 0 to 6, the use of compression
depends on the "T" flag as specified in this document. A MOP value
of 7 and above MUST use compression by default and ignore the setting
of the "T" flag.
the DIO Base Object. This specification applies to MOP values 0 to
6. For a MOP value of 7 (and above when extended), the compression
MUST be used by default regardless of the setting of the "T" flag.



Thubert & Zhao Expires 22 January 2021 [Page 4]

Thubert & Zhao Expires 6 February 2021 [Page 4]

Internet-Draft Turn On 6LoRH July 2020
Internet-Draft Turn On 6LoRH August 2020


4. Updating RFC 8138

A node SHOULD source packets in the compressed form using [RFC8138]
if and only if the "T" flag is set. This behaviour can be overridden
by e.g., configuration or network management. Overriding may be
needed e.g., to cope with a legacy implementations of the Root that
needed e.g., to cope with a legacy implementation of the Root that
supports [RFC8138] but not this specification and cannot set the "T"
flag.

Expand All @@ -243,18 +243,19 @@ Internet-Draft Turn On 6LoRH July 2020
packet as is.

An external target [USEofRPLinfo] is not expected to support
[RFC8138]. In most cases, packets from/to an external target are
tunneled back and forth between the RPL border router and the Root
regardless of the MOP used in the RPL DODAG. The inner packet is
typically not compressed with [RFC8138] so the 6LR just needs to
decapsulate the (compressed) outer header and forward the
(uncompressed) inner packet towards the external target.
[RFC8138]. In most cases, packets from and to an external target are
tunneled back and forth between the border router (referred to as
6LR) that serves the external target and the Root, regardless of the
MOP used in the RPL DODAG. The inner packet is typically not
compressed with [RFC8138], so for outgoing packets, the border router
just needs to decapsulate the (compressed) outer header and forward
the (uncompressed) inner packet towards the external target.

A router MUST uncompress a packet that is to be forwarded to an
external target. Otherwise, the router MUST forward the packet in
the form that the source used, either compressed or uncompressed.

A RUL [UNAWARE-LEAVES] is both a leaf and an external target . A RUL
A RUL [UNAWARE-LEAVES] is both a leaf and an external target. A RUL
does not participate in RPL and depends on the parent router to
obtain connectivity. In the case of a RUL, forwarding towards an
external target actually means delivering the packet.
Expand All @@ -263,8 +264,9 @@ Internet-Draft Turn On 6LoRH July 2020

A node that supports [RFC8138] but not this specification can only be
used in an homogeneous network. Enabling the [RFC8138] compression
requires a "flag day"; all nodes must be upgraded, and then the
network can be rebooted with the [RFC8138] compression turned on.
without a turn-on signaling requires a "flag day"; all nodes must be
upgraded, and then the network can be rebooted with the [RFC8138]
compression turned on.

The intent for this specification is to perform a migration once and
for all without the need for a flag day. In particular it is not the
Expand All @@ -275,11 +277,9 @@ Internet-Draft Turn On 6LoRH July 2020





Thubert & Zhao Expires 22 January 2021 [Page 5]
Thubert & Zhao Expires 6 February 2021 [Page 5]

Internet-Draft Turn On 6LoRH July 2020
Internet-Draft Turn On 6LoRH August 2020


5.1. Coexistence
Expand Down Expand Up @@ -333,9 +333,9 @@ Internet-Draft Turn On 6LoRH July 2020



Thubert & Zhao Expires 22 January 2021 [Page 6]
Thubert & Zhao Expires 6 February 2021 [Page 6]

Internet-Draft Turn On 6LoRH July 2020
Internet-Draft Turn On 6LoRH August 2020


6. IANA Considerations
Expand Down Expand Up @@ -377,6 +377,23 @@ Internet-Draft Turn On 6LoRH July 2020
network, at an additional cost of bandwidth for packets in the
uncompressed form.

An attacker in the middle of the network may reset the "T" flag to
cause extra energy spending in its subDAG. Conversely it may set the
"T" flag, so that nodes located downstream would compress when that
it is not desired, potentially resulting in the loss of packets. In
a tree structure, the attacker would be in position to drop the
packets from and to the attacked nodes. So the attacks above would
be more complex and more visible than simply dropping selected
packets. The downstream node may have other parents and see both
settings, which could raise attention.



Thubert & Zhao Expires 6 February 2021 [Page 7]

Internet-Draft Turn On 6LoRH August 2020


8. Acknowledgments

The authors wish to thank Alvaro Retana, Dominique Barthel and Rahul
Expand All @@ -387,13 +404,6 @@ Internet-Draft Turn On 6LoRH July 2020

9. Normative References



Thubert & Zhao Expires 22 January 2021 [Page 7]

Internet-Draft Turn On 6LoRH July 2020


[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
Expand Down Expand Up @@ -433,23 +443,19 @@ Internet-Draft Turn On 6LoRH July 2020

10. Informative References



Thubert & Zhao Expires 6 February 2021 [Page 8]

Internet-Draft Turn On 6LoRH August 2020


[RFC6553] Hui, J. and JP. Vasseur, "The Routing Protocol for Low-
Power and Lossy Networks (RPL) Option for Carrying RPL
Information in Data-Plane Datagrams", RFC 6553,
DOI 10.17487/RFC6553, March 2012,
<https://www.rfc-editor.org/info/rfc6553>.







Thubert & Zhao Expires 22 January 2021 [Page 8]

Internet-Draft Turn On 6LoRH July 2020


[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for
Constrained-Node Networks", RFC 7228,
DOI 10.17487/RFC7228, May 2014,
Expand Down Expand Up @@ -495,10 +501,4 @@ Authors' Addresses









Thubert & Zhao Expires 22 January 2021 [Page 9]
Thubert & Zhao Expires 6 February 2021 [Page 9]

0 comments on commit 9f5b90e

Please sign in to comment.