Re: [Roll] WGLC for draft-thubert-6man-flow-label-for-rpl-03

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 05 August 2014 08:11 UTC

Return-Path: <pthubert@cisco.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 B88891B292D; Tue, 5 Aug 2014 01:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 x63rRy_OJ2NG; Tue, 5 Aug 2014 01:11:32 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 133E21B292C; Tue, 5 Aug 2014 01:11:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2141; q=dns/txt; s=iport; t=1407226293; x=1408435893; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=GLhN0aA6RY2A+DdFY9yxHXOiL44gy6konrHxwjuhaSg=; b=EygSvjm/f5tPINH9WztVp5NR1Gmo2KC6JFIlRtUSgAT2usQI7fUkb/dz WJOzGUkv9ngm6YxARBuSwgyJVWlsRb+9XQPP+vVRI5emRaH6lXG3BXjVo sxxEOSGoH18dErKRuLvL5/FlnJa0y0me77vXcItdQjdip56axtPZo+O+4 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AksFAICQ4FOtJA2D/2dsb2JhbABbDoJ/gSkE0zABgRUWd4QDAQEBBHkMBAIBCA4DBAEBAQodByERFAkIAQEEAQ0FCIgmAxG8OQ2GYxeNH4FWCR0xBwaDKYEcAQSKVY8tkD6GKIMLQmyBBUE
X-IronPort-AV: E=Sophos;i="5.01,804,1400025600"; d="scan'208";a="345162482"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP; 05 Aug 2014 08:11:32 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s758BVx3005452 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Aug 2014 08:11:31 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.37]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Tue, 5 Aug 2014 03:11:31 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Philip Levis <pal@cs.stanford.edu>, Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [Roll] WGLC for draft-thubert-6man-flow-label-for-rpl-03
Thread-Index: Ac+wDejPSf6MzwEzQpSdG5woHqaOoAAAz3YlABynPRA=
Date: Tue, 05 Aug 2014 08:11:30 +0000
Deferred-Delivery: Tue, 5 Aug 2014 08:11:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842D1A9FA@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD842D189A1@xmb-rcd-x01.cisco.com> <406B5D64-4F0E-4E71-BC60-A113FB367652@gmail.com> <46112F69-05F0-4E50-A808-287B06AE8E5F@cs.stanford.edu>
In-Reply-To: <46112F69-05F0-4E50-A808-287B06AE8E5F@cs.stanford.edu>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.75.33]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/l-XPu3-dVkfi7yTqckZetL8pdlg
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Routing Over Low power and Lossy networks <roll@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Roll] WGLC for draft-thubert-6man-flow-label-for-rpl-03
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: Tue, 05 Aug 2014 08:11:40 -0000

I think I see what you are saying, Phil.

I can split 1.3 to isolate the deviations to 6437.

I also need to move the following text from section 3 in that new section 

  This may seem contradictory with the IPv6
   Flow Label Specification [RFC6437] which stipulates that once it is
   set, the Flow Label is left unchanged; but the RFC also indicates a
   violation to the rule can be accepted for compelling reasons, and
   that security is a case justifying such a violation.  This
   specification suggests that energy-saving is another compelling
   reason for a violation to the aforementioned rule.

Proposed update for that text:

   This specification updates the IPv6
   Flow Label Specification [RFC6437], which stipulates that once it is
   set, the Flow Label is left unchanged. [RFC6437] also indicates that 
   a violation to the rule can be accepted for compelling reasons, 
   but limit those compelling reasons to security related issues.  This
   specification indicates that energy-saving is another compelling
   reason that justifies a violation to the aforementioned rule.

What do you think?

Cheers,

Pascal


> -----Original Message-----
> From: Philip Levis [mailto:pal@cs.stanford.edu]
> Sent: lundi 4 août 2014 20:23
> To: Ralph Droms
> Cc: Pascal Thubert (pthubert); Michael Richardson; Routing Over Low power
> and Lossy networks; ipv6@ietf.org
> Subject: Re: [Roll] WGLC for draft-thubert-6man-flow-label-for-rpl-03
> 
> 
> On Aug 4, 2014, at 11:10 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> 
> >
> > On Aug 4, 2014, at 2:01 PM 8/4/14, Pascal Thubert (pthubert)
> <pthubert@cisco.com> wrote:
> >
> >> The change is now done, Ralph.
> >>
> >> The only difference between draft-thubert-6man-flow-label-for-rpl-03 and
> draft-thubert-6man-flow-label-for-rpl-04 is
> >>
> >> Updates: 6437 (if approved)
> >
> > I suggest adding a section to your doc that explains exactly what is being
> updated in RFC 6437.
> >
> > - Ralph
> 
> 
> I agree. I think some of the text in 1.3 can be re-used for this purpose.
> 
> Phil