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

Philip Levis <pal@cs.stanford.edu> Wed, 06 August 2014 04:57 UTC

Return-Path: <pal@cs.stanford.edu>
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 CFA3E1B280C; Tue, 5 Aug 2014 21:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.201
X-Spam-Level:
X-Spam-Status: No, score=-6.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 qRdRm7y9aNfl; Tue, 5 Aug 2014 21:57:38 -0700 (PDT)
Received: from smtp1.cs.Stanford.EDU (smtp1.cs.Stanford.EDU [171.64.64.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CF681B280E; Tue, 5 Aug 2014 21:57:35 -0700 (PDT)
Received: from [76.14.66.110] (port=57734 helo=[192.168.0.103]) by smtp1.cs.Stanford.EDU with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from <pal@cs.stanford.edu>) id 1XEtI3-0005Zz-MS; Tue, 05 Aug 2014 21:57:34 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Philip Levis <pal@cs.stanford.edu>
In-Reply-To: <1E250FB9-1BBD-4074-9296-C269D6C409D7@ece.iisc.ernet.in>
Date: Tue, 5 Aug 2014 21:57:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADC094E3-9D88-4CE6-BC96-901DD29B8A0D@cs.stanford.edu>
References: <E045AECD98228444A58C61C200AE1BD842D189A1@xmb-rcd-x01.cisco.com> <406B5D64-4F0E-4E71-BC60-A113FB367652@gmail.com> <46112F69-05F0-4E50-A808-287B06AE8E5F@cs.stanford.edu> <E045AECD98228444A58C61C200AE1BD842D1A9FA@xmb-rcd-x01.cisco.com> <1E250FB9-1BBD-4074-9296-C269D6C409D7@ece.iisc.ernet.in>
To: Anand SVR <anand@ece.iisc.ernet.in>
X-Mailer: Apple Mail (2.1510)
X-Scan-Signature: 5d5bd4b8133540f30bea22ef470d169d
Archived-At: http://mailarchive.ietf.org/arch/msg/roll/pXsrpZQXU64uDAb2tV2Z8ItTwLg
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: Wed, 06 Aug 2014 04:57:43 -0000

I totally agree that the document leaves the question open of whether there could be future uses. The use of the flow label in that way doesn't go against the spirit of the document and so we shouldn't reject the idea out of principle. But it does go against the letter of the document -- hence the need for an Updates: or other explicit note that this is the case.

Phil

On Aug 5, 2014, at 10:18 AM, Anand SVR <anand@ece.iisc.ernet.in> wrote:

> Hi,
> 
> The discussion has been very interesting, more so because it is bordering on the legality of the usage of the word MUST. I agree with Philip's take on this. But after reading the RFC, I got this impression that the RFC meant to be a facility or a feature with certain usage guidelines. The MUST usage is more to imply stronger than SHOULD so as to discourage people from modifying it. I suppose at the time of writing, the authors might not have foreseen that in some point in future the value can be changed for other reasons. Therefore the use of MUST MUST be taken with the right spirit it is meant to be taken rather than literally :) 
> 
> Anand
> 
> 
>> On 05-Aug-2014, at 1:41 pm, "Pascal Thubert (pthubert)" <pthubert@cisco.com> wrote:
>> 
>> 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
>> 
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>> 
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>> 
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>