Re: [6lo] I-D Action: draft-ietf-6lo-rfc6775-update-07.txt

Rahul <rahul.ietf@gmail.com> Sat, 29 July 2017 07:35 UTC

Return-Path: <rahul.ietf@gmail.com>
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 0F862132256; Sat, 29 Jul 2017 00:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Ylw4sHIRkGUX; Sat, 29 Jul 2017 00:35:51 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 A88DA132250; Sat, 29 Jul 2017 00:35:50 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id v205so89893104itf.1; Sat, 29 Jul 2017 00:35:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=W6yvgRm9BlaJAgFlGCR8lR71JoG4qbkgswMYbUz6VLc=; b=atjzaS9rwWxtZmJS554yswx6pDxdn4ksT518w4tu+akQqBM2CEtuuLNaXjaf0yK2no yPndHuFKh6SZTixlSS3031m55Th6DjVSyan8LPl8rBS3xvuz4ooiQVBL5DEM2M0FK8E/ rCKVQyWdYFInpfcZcs/c/ZdqWsad003R9cgdx4UQxlU5qAhtgNryO4ejz2O9N/1LM9fb lpD6GWtU99UkStgOsmCmsg867OvFyZpwK68hFeLgvVGGRVlnZvt0QAXCV38X0zdZSICL llld4aomB1GkPuYvDAWkx45rWK2rEsnMRHVsaOm4Y3npCVRjidmnL2zDCBsW9BdFaYhn Y2kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=W6yvgRm9BlaJAgFlGCR8lR71JoG4qbkgswMYbUz6VLc=; b=PADgumDYKxnSy8dvnDlS08XXCZFfL3LAPCmd82oeCDs7oBDiB49e9ZQn+EKOMIwKet WcPf69b8fAWPGd80VRKuRVvUc7NPOoMbjWhNi1/nua8aAhcF6bK3+cgWBrCRhncMAKpJ ZnKDtuWnhZTqqB6yYzsb86+Hj2RJOi+YJX6esqOmbc7WUE++O3ViZ8l337AXQoB6u2l3 Cd82C0W8MdAo1ANmOJZEuchDK7uBzMlWchNl2P4crO8PDcglJyA/ddtKH33fo41ceilJ VksnIyDumK9Ql1A11VV1MGfSGmJR0iwKGqpGHhZLEZu548ZlfkE2Qbdh5zmw40c/U7bR 4CbA==
X-Gm-Message-State: AIVw111gxl+FhVw5h+/rYR/P1n/iL2viw4UvvS27ymTVTZLBrjQEvuM6 jeKu8GqY9ZU0yg==
X-Received: by 10.36.178.16 with SMTP id u16mr11763209ite.160.1501313749943; Sat, 29 Jul 2017 00:35:49 -0700 (PDT)
Received: from ubuntu-1604-lts.c.rjtmp-165304.internal (53.84.197.104.bc.googleusercontent.com. [104.197.84.53]) by smtp.gmail.com with ESMTPSA id l62sm3009609ita.8.2017.07.29.00.35.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jul 2017 00:35:49 -0700 (PDT)
From: Rahul <rahul.ietf@gmail.com>
X-Google-Original-From: Rahul <nyrahul@ubuntu-1604-lts.c.rjtmp-165304.internal>
Date: Sat, 29 Jul 2017 07:35:39 +0000
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
cc: "6lo-chairs@ietf.org" <6lo-chairs@ietf.org>, "6lo@ietf.org" <6lo@ietf.org>
In-Reply-To: <9874400d7c874bdf84ada5c665d4b0e6@XCH-RCD-001.cisco.com>
Message-ID: <alpine.DEB.2.20.1707290656450.4945@ubuntu-1604-lts.c.rjtmp-165304.internal>
References: <150126752527.25319.17166946473513771104@ietfa.amsl.com> <9874400d7c874bdf84ada5c665d4b0e6@XCH-RCD-001.cisco.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/MKSc-Zn7YX0a7Y5zjgX_9J4NN5Y>
Subject: Re: [6lo] I-D Action: draft-ietf-6lo-rfc6775-update-07.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
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, 29 Jul 2017 07:35:53 -0000

Thanks Pascal for the revised text.

Have some more points...

The revised text suggests to use EARO in the DAR/DAC messages (section 
6.1 in 6775-update-07) to include TID so as to indicate freshness.

Current RFC6775 does not use ARO option in DAR/DAC message (section 
4.1), but it copies most (but not all) of its fields including 
registration lifetime, EUI-64 in the Duplicate Address Messages.
Quoting RFC6775, "The information contained in the ARO is also included in 
the multihop DAR and DAC messages used between 6LRs and 6LBRs, but the 
option itself is not used in those messages."

Two points:
a. This update suggests including EARO in DAR/DAC message which is in 
contradiction to the text suggested in section4.1-RFC6775. Per me, I don't 
see a problem with this inclusion, but just want to highlight this fact 
and wondering if a text update could be added.
b. Secondly, with this inclusion, the reg lifetime and EUI-64 is redundant 
in the DAR/DAC (since EARO option and base DAR/DAC have the same fields). 
This is 12bytes redundancy! Essentially what we want is TID to be 
included in DAR/DAC messages but using EARO in DAR/DAC might not be the 
best way to do it.

Regards,
Rahul

On Fri, 28 Jul 2017, Pascal Thubert (pthubert) wrote:

> Dear chairs and all:
>
> This revision addresses Sedat and Rahul's WGLC comments, and integrates the computation of the TID as discussed at the WG meeting.
>
> To my best knowledge, the document is ready for the next steps.
>
> Take care,
>
> Pascal
>
> -----Original Message-----
> From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: vendredi 28 juillet 2017 20:45
> To: i-d-announce@ietf.org
> Cc: 6lo@ietf.org
> Subject: [6lo] I-D Action: draft-ietf-6lo-rfc6775-update-07.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 over Networks of Resource-constrained Nodes WG of the IETF.
>
>        Title           : An Update to 6LoWPAN ND
>        Authors         : Pascal Thubert
>                          Erik Nordmark
>                          Samita Chakrabarti
> 	Filename        : draft-ietf-6lo-rfc6775-update-07.txt
> 	Pages           : 31
> 	Date            : 2017-07-28
>
> Abstract:
>   This specification updates RFC 6775 - 6LoWPAN Neighbor Discovery, to
>   clarify the role of the protocol as a registration technique,
>   simplify the registration operation in 6LoWPAN routers, as well as to
>   provide enhancements to the registration capabilities and mobility
>   detection for different network topologies including the backbone
>   routers performing proxy Neighbor Discovery in a low power network.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6lo-rfc6775-update/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-6lo-rfc6775-update-07
> https://datatracker.ietf.org/doc/html/draft-ietf-6lo-rfc6775-update-07
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6lo-rfc6775-update-07
>
>
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>