Re: [6tisch] [Roll] Fwd: New Version Notification for draft-thubert-roll-unaware-leaves-02.txt

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 21 February 2018 22:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A466912AAB6; Wed, 21 Feb 2018 14:55:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYWzjnRZyMlX; Wed, 21 Feb 2018 14:55:56 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 176B812422F; Wed, 21 Feb 2018 14:55:56 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8A3E420091; Wed, 21 Feb 2018 18:03:18 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1A9A780B14; Wed, 21 Feb 2018 17:55:55 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
cc: "6tisch@ietf.org" <6tisch@ietf.org>
In-Reply-To: <0507EB1B-3B42-4108-A511-EEE413CF0FE4@cisco.com>
References: <151920480372.9603.17635052466831884104.idtracker@ietfa.amsl.com> <0507EB1B-3B42-4108-A511-EEE413CF0FE4@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Wed, 21 Feb 2018 17:55:55 -0500
Message-ID: <10405.1519253755@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/K9DNuDAUQwweXcb3s3abTDtVizU>
Subject: Re: [6tisch] [Roll] Fwd: New Version Notification for draft-thubert-roll-unaware-leaves-02.txt
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 22:55:58 -0000

Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
    > This is a short draft, but the work is much needed to complete the RPL
    > story on non-RPL-aware leaves. The draft conforms to the long-standing
    > expectations from the 6TiSCH architecture.

1) can you add a reference for "Routing Stretch"?
2) Alternatively, the 6LN may rely on its 6LR to perform routing and
   forwarding on its behalf.  In the context of RPL, such a 6LN is

   -> if you want to give an example of such a node, I think that the window
      smash sensor (alarm system), or the kinetically powered light switch,
      are two good examples.
   {I wish I had links to real products that actually ran RPL.}

section 3:
s/      Upon the renewal of a registration, this specification changes the
        behavior or the 6LR.
 /      Upon the renewal of a 6lowPAN ND registration, this specification changes the
        behavior of the 6LR. /

The rest of that paragraph is ver hard to parse.

section 4:
should:
   This document specifies a new flag in the EARO option, the 'R' flag,
   used by the registering node to indicate that the 6LN that performs
   the registration is a router and that it handles its reachability.

say:
   This document specifies a new flag in the EARO option, the 'R' flag,
   used by a 6LN, when registering, to indicate that this 6LN
   is a router and that it will handles its own reachability.

   (...By sending a DAO)

The rest of the document has some difficult sentences too.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-