[Roll] Iotdir last call review of draft-ietf-roll-turnon-rfc8138-09

Carles Gomez via Datatracker <noreply@ietf.org> Wed, 05 August 2020 07:26 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: roll@ietf.org
Delivered-To: roll@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D93A3A0F13; Wed, 5 Aug 2020 00:26:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Carles Gomez via Datatracker <noreply@ietf.org>
To: iot-directorate@ietf.org
Cc: last-call@ietf.org, draft-ietf-roll-turnon-rfc8138.all@ietf.org, roll@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.12.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159661239313.30550.10499047705190236121@ietfa.amsl.com>
Reply-To: Carles Gomez <carlesgo@entel.upc.edu>
Date: Wed, 05 Aug 2020 00:26:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/mk-aK5T8KwOxHjvam24QLzuOttw>
Subject: [Roll] Iotdir last call review of draft-ietf-roll-turnon-rfc8138-09
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2020 07:26:33 -0000

Reviewer: Carles Gomez
Review result: Ready with Nits

The document is generally clear and well written. No issue was found from a
"6lo" perspective.

Some nits/questions/comments follow:

- Section 2.1, 1st paragraph:  s/The Terminology/The terminology

- Section 2.1, 2nd paragraph, first line: s/"RPL Instance”/and “RPL Instance”

- Section 2.1, 3rd paragraph: s/RPL Aware Leaf/RPL-Aware Leaf

- Section 2.2: note that the use of hyphens in the expanded forms of RAL and
RUL are different from those in draft-ietf-roll-useofrplinfo. (I think the
correct form is the one in the turnon-rfc8138 document, but I guess this will
be confirmed at subsequent stages…)

- Section 3: “A MOP value of 7 and above”. If the MOP is a 3-bit field, the
highest MOP value is 7 (assuming that the lowest value is 0). Why state here
"and above"? Are there plans to extend the MOP field size?

- Section 3, after “A MOP value of 7 and above”. s/MUST use
compression/indicates that compression MUST be used

- Section 4, 1st paragraph: “if and only if the "T" flag is set.” Should we
perhaps append “or if the MOP value is 7.”  ?

- Section 4, 1st paragraph: s/implementations/implementation

- Section 4, 3rd paragraph: What is the "RPL border router"? I couldn't find a
definition in the Terminology section or in other documents...  May the "RPL
border router" and the Root run in the same physical device? May the "RPL
border router" and the Root run in different physical devices?

- Section 4, 3rd paragraph: the last sentence is written only from the “from”
perspective, whereas the previous one is keeps the double "from/to" perspective.

- Section 4, last paragraph, 1st sentence. Please remove the blank space at the
end of the sentence.

- Section 5, 1st paragraph, 2nd sentence. Perhaps prepend the following:
“Without this specification, ”

- Section 7, last sentence. Might this still be exploited as an attack (e.g. to
battery-operated devices) based on depleting energy at a faster rate? If
appropriate, please briefly discuss whether this might be significant or not.