Re: [Technical Errata Reported] RFC6936 (4341)

Brian Haberman <brian@innovationslab.net> Tue, 21 April 2015 12:07 UTC

Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 767441AC40E for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 05:07:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_74=0.6] autolearn=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 F0sJEk1f7Yfx for <ipv6@ietfa.amsl.com>; Tue, 21 Apr 2015 05:07:52 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0F1C1AC40F for <ipv6@ietf.org>; Tue, 21 Apr 2015 05:07:46 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id A43E9880F3; Tue, 21 Apr 2015 05:07:46 -0700 (PDT)
Received: from Brians-MacBook-Pro.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id BA59A136832A; Tue, 21 Apr 2015 05:07:45 -0700 (PDT)
Message-ID: <55363D89.2070001@innovationslab.net>
Date: Tue, 21 Apr 2015 08:07:37 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, gorry@erg.abdn.ac.uk, Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: [Technical Errata Reported] RFC6936 (4341)
References: <5535D626.6020405@bogus.com> <791835886.1217669.1429602424845.JavaMail.yahoo@mail.yahoo.com> <6ab2a83537cbb5a11d2509478a75dd9d.squirrel@erg.abdn.ac.uk> <55360E18.2000008@ericsson.com>
In-Reply-To: <55360E18.2000008@ericsson.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="tRhMeiNiaONImLI0GrWR2lxmQfSMQbwRK"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/d3Dy23OVcs3_bHn8Ick_HaMrmxQ>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "terry.manderson@icann.org" <terry.manderson@icann.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2015 12:07:53 -0000

Hi all,
     While I agree with the sentiment that the proposed updated text is
more appropriate, we are on a slippery slope as to this being errata.
This is a technical change and not fixing an error.  Can someone point
to a discussion where a reference to 6438 and stateless methods occurred
and there was consensus to put that in 1.3.5?

     If not, this seems more like a new draft to obsolete 6936.

Regards,
Brian

On 4/21/15 4:45 AM, Magnus Westerlund wrote:
> I also support approving this Errata.
> 
> Cheers
> 
> Magnus
> 
> gorry@erg.abdn.ac.uk skrev den 2015-04-21 10:09:
>> I agree with this update. I think it is a useful correction.
>>
>> Gorry
>>
>>> I agree with Brian's update, I think stateless LB is better.
>>> (Strangely and coincidently, my OpenWRT router reported I received one
>>> today:
>>> [ Â 422.320000] IPv6: udp checksum is 0
>>>
>>> )
>>>
>>>
>>> Regards,Mark.
>>>       From: joel jaeggli <joelja@bogus.com>
>>>  To: RFC Errata System <rfc-editor@rfc-editor.org>; gorry@erg.abdn.ac.uk;
>>> magnus.westerlund@ericsson.com; brian@innovationslab.net;
>>> terry.manderson@icann.org; bob.hinden@gmail.com; otroan@employees.org
>>> Cc: ipv6@ietf.org
>>>  Sent: Tuesday, 21 April 2015, 14:46
>>>  Subject: Re: [Technical Errata Reported] RFC6936 (4341)
>>>
>>> anyone care to comment?
>>>
>>> joel
>>>
>>>
>>>
>>> On 4/20/15 9:35 PM, RFC Errata System wrote:
>>>> The following errata report has been submitted for RFC6936,
>>>> "Applicability Statement for the Use of IPv6 UDP Datagrams with Zero
>>>> Checksums".
>>>>
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> http://www.rfc-editor.org/errata_search.php?rfc=6936&eid=4341
>>>>
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>
>>>>
>>>> Section: 1.3.5
>>>>
>>>> Original Text
>>>> -------------
>>>> The ingress of a tunnel seeking to provide good
>>>> entropy in the flow label field would therefore need to create a
>>>> random flow label value and keep corresponding state so that all
>>>> packets that were associated with a flow would be consistently given
>>>> the same flow label.  Although possible, this complexity may not be
>>>> desirable in a tunnel ingress.
>>>>
>>>> Corrected Text
>>>> --------------
>>>> The ingress of a tunnel seeking to provide good
>>>> entropy in the flow label field would therefore need to create a
>>>> pseudo-random flow label value using a stateless method
>>>> as described in [RFC6438] so that all
>>>> packets that were associated with a flow would be consistently given
>>>> the same flow label.
>>>>
>>>> Notes
>>>> -----
>>>> It is incorrect that a stateful method is needed, and presumably that
>>>> was the complexity judged undesirable. Also, we shouldn't say "random"
>>>> when we mean "pseudo-random."
>>>>
>>>> Instructions:
>>>> -------------
>>>> This erratum is currently posted as "Reported". If necessary, please
>>>> use "Reply All" to discuss whether it should be verified or
>>>> rejected. When a decision is reached, the verifying party (IESG)
>>>> can log in to change the status and edit the report, if necessary.
>>>>
>>>> --------------------------------------
>>>> RFC6936 (draft-ietf-6man-udpzero-12)
>>>> --------------------------------------
>>>> Title              : Applicability Statement for the Use of IPv6
>>>> UDP Datagrams with Zero Checksums
>>>> Publication Date    : April 2013
>>>> Author(s)Â  Â  Â  Â  Â  : G. Fairhurst, M. Westerlund
>>>> Category            : PROPOSED STANDARD
>>>> Source              : IPv6 Maintenance
>>>> Area                : Internet
>>>> Stream              : IETF
>>>> Verifying Party    : IESG
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>
>>
>>
> 
>