Re: [6lo] review of 6lo-blemesh

"Carles Gomez Montenegro" <carlesgo@entel.upc.edu> Sat, 28 September 2019 17:04 UTC

Return-Path: <carlesgo@entel.upc.edu>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F5912007A for <6lo@ietfa.amsl.com>; Sat, 28 Sep 2019 10:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 iStJF4etZSd4 for <6lo@ietfa.amsl.com>; Sat, 28 Sep 2019 10:04:05 -0700 (PDT)
Received: from dash.upc.es (dash.upc.es [147.83.2.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0EC8120047 for <6lo@ietf.org>; Sat, 28 Sep 2019 10:04:04 -0700 (PDT)
Received: from entelserver.upc.edu (entelserver.upc.es [147.83.39.4]) by dash.upc.es (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id x8SH3usC038827; Sat, 28 Sep 2019 19:03:56 +0200
Received: from webmail.entel.upc.edu (webmail.entel.upc.edu [147.83.39.6]) by entelserver.upc.edu (Postfix) with ESMTP id 10B451D53C1; Sat, 28 Sep 2019 19:03:55 +0200 (CEST)
Received: from 81.39.61.19 by webmail.entel.upc.edu with HTTP; Sat, 28 Sep 2019 19:03:55 +0200
Message-ID: <1e105105832b45342a54be08c3c9df90.squirrel@webmail.entel.upc.edu>
In-Reply-To: <CAO0Djp2Of3ERSvZoHvPosDvp1D6jGhKa4UU64uaQ5AX0a12dpA@mail.gmail.com>
References: <CAO0Djp2Of3ERSvZoHvPosDvp1D6jGhKa4UU64uaQ5AX0a12dpA@mail.gmail.com>
Date: Sat, 28 Sep 2019 19:03:55 +0200
From: "Carles Gomez Montenegro" <carlesgo@entel.upc.edu>
To: "Rahul Jadhav" <rahul.ietf@gmail.com>
Cc: "lo" <6lo@ietf.org>
User-Agent: SquirrelMail/1.4.21-1.fc14
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: clamav-milter 0.100.3 at dash
X-Virus-Status: Clean
X-Greylist: ACL matched, not delayed by milter-greylist-4.3.9 (dash.upc.es [147.83.2.50]); Sat, 28 Sep 2019 19:03:56 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/ig7y8jrXHEEPS0_O2C9qToT-hOw>
Subject: Re: [6lo] review of 6lo-blemesh
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Sep 2019 17:04:08 -0000

Dear Rahul,

First of all, apologies for the late response.

Thank you very much for your review.

We have just submitted -06, which is intended to address your comments:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-blemesh-06

Should you have any further concerns, please do not hesitate to let us know.

Cheers,

Carles (as a WG participant)


> Dear authors,
>
> Following are some review comments based on the latest updates to the
> document:
> 1. In the last revision, the draft mandated the use of NS(EARO) in
> place NS(ARO). This change is not consistently applied in the
> document. E.g., in section 3.3.3, the draft continues to use NS(ARO).
> 2. Section 3.3.3 also mandates the use of the 6CO option. 6CO option
> may not be necessary in case a single prefix is used in the network.
> The CID defaults to zero which results in the use of default prefix.
> 3. Section 3.3.3 the following statement is not clear, "In particular,
> the latter comprise link-local interactions, non-link- local packet
> transmissions originated and performed by a 6LN, and non-link-local
> packets transmitted (but not necessarily originated) by the neighbor
> of a 6LN to that 6LN."
> 4. I think the draft will benefit from a call flow diagram depicting
> the node joining procedure.
>    6LN ----(RS)-------> 6LR
>    6LN <---(RA-PIO)---- 6LR
>    6LN ----(NS-EARO)--> 6LR
>    [Multihop DAD procedure]
>    6LN <---(NA)--------  6LR
>    6LN can now start acting as 6LR and advertise its own RA
>    6LN ----(RA)--
>
> Regards,
> Rahul
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>