Re: [Roll] FW: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 16 May 2014 01:39 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4A61A06D9; Thu, 15 May 2014 18:39:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 GCx1eV8PkJ_x; Thu, 15 May 2014 18:39:49 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C90951A06A8; Thu, 15 May 2014 18:39:49 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id uo5so1865877pbc.28 for <multiple recipients>; Thu, 15 May 2014 18:39:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ratcyS0Gr8lCsirt7RRbacoxcNWhEoBNgKwUSSgxELs=; b=PDq9zLMafZw8MyJDbaIS1t5wWHKugnlMVxzXath9rznBeVl5sS6OfVtRlK4TdevUUk 94089euREXbS3Jq9t+UCnjwso12c+Bmadmf/IdmWbnIRGeRXIWsG4rEuyZt0DFwCNEyg y/spnOQZst8WqZsUEIBT+GFr1AdM53yGkUtjD7uV70VgzkZGWdS1vu1utZXu4VF6A7NA PWZ/4fxVPo/PogF503B/GT+2Uyz+vVZ4ynzeGVzPD9uVD6+CsIE6LTMsDbeeNjfLsNpW XaNohyCTduj1W4C1sGD7VCKAI+y6MCYvmMqnV0qES12jjZJl4o6R2mWEVuSp0Yc+eaxH 3/Xw==
X-Received: by 10.66.151.144 with SMTP id uq16mr17057793pab.68.1400204382677; Thu, 15 May 2014 18:39:42 -0700 (PDT)
Received: from [192.168.178.20] (101.200.69.111.dynamic.snap.net.nz. [111.69.200.101]) by mx.google.com with ESMTPSA id iv2sm11433813pbc.19.2014.05.15.18.39.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 May 2014 18:39:41 -0700 (PDT)
Message-ID: <53756C64.6090900@gmail.com>
Date: Fri, 16 May 2014 13:39:48 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
References: <20140513091837.28963.29591.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD842658563@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD842658563@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/nPUCv5ky38AgIg8EeLdypdDkptg
Cc: roll <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>, Pat Kinney <pat.kinney@KINNEYCONSULTINGLLC.COM>
Subject: Re: [Roll] FW: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
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: <http://www.ietf.org/mail-archive/web/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: Fri, 16 May 2014 01:39:52 -0000

On 13/05/2014 21:26, Pascal Thubert (pthubert) wrote:
> Dear all:
> 
> This new version addresses Brian's concerns, in particular the language that relates this proposal with the Flow Label Specification (RFC 6437).
> It is made clearer that this is a deviation such as already tolerated for security reasons, and that the compelling reason is energy saving.
> The proposal only impacts the use of the flow label inside the LLN and does not result in a deterioration of the application of RFC 6437 inside the Internet. 
> The proposal is supported by individuals participating to LLN related groups at the IETF (cc'ed) and external SDOs (ISA100).

I'm happy with the new Applicability section. However, there is an editing
problem with the first sentence of its final paragraph (some words need to
be deleted, I suspect).

> The question is now whether we should complete the work at 6MAN or move back to ROLL.
> 
> What do you think?

IMHO, since this does not formally update a 6man document, I don't think
it's required to be processed by 6man - but a special WGLC in 6man would be
reasonable in any case, to avoid unexpected issues at IETF Last Call.
However, that's only one person's opinion.

Since 6man is not meeting in Toronto, please let us know if the draft
will be discussed elsewhere.

    Brian

> 
> Pascal
> 
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: mardi 13 mai 2014 11:19
> To: Pascal Thubert (pthubert); Pascal Thubert (pthubert)
> Subject: New Version Notification for draft-thubert-6man-flow-label-for-rpl-02.txt
> 
> 
> A new version of I-D, draft-thubert-6man-flow-label-for-rpl-02.txt
> has been successfully submitted by Pascal Thubert and posted to the IETF repository.
> 
> Name:		draft-thubert-6man-flow-label-for-rpl
> Revision:	02
> Title:		The IPv6 Flow Label within a RPL domain
> Document date:	2014-05-13
> Group:		Individual Submission
> Pages:		11
> URL:            http://www.ietf.org/internet-drafts/draft-thubert-6man-flow-label-for-rpl-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-thubert-6man-flow-label-for-rpl/
> Htmlized:       http://tools.ietf.org/html/draft-thubert-6man-flow-label-for-rpl-02
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-thubert-6man-flow-label-for-rpl-02
> 
> Abstract:
>    This document present how the Flow Label can be used inside a RPL
>    domain as a replacement to the RPL option and provides rules for the
>    root to set and reset the Flow Label when forwarding between the
>    inside of RPL domain and the larger Internet, in both direction.
>    This new operation saves 44 bits in each frame, and an eventual IP-
>    in-IP encapsulation within the RPL domain that is required for all
>    packets that reach outside of the RPL domain.
> 
>                                                                                   
> 
> 
> 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.
> 
> The IETF Secretariat
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>