Re: Eric Rescorla's No Objection on draft-ietf-6man-rfc6434-bis-08: (with COMMENT)

Eric Rescorla <ekr@rtfm.com> Wed, 04 July 2018 03:54 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6773D130EAA for <ipv6@ietfa.amsl.com>; Tue, 3 Jul 2018 20:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 S41-HfXlktnY for <ipv6@ietfa.amsl.com>; Tue, 3 Jul 2018 20:54:31 -0700 (PDT)
Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (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 63452130EBD for <ipv6@ietf.org>; Tue, 3 Jul 2018 20:54:31 -0700 (PDT)
Received: by mail-yb0-x22d.google.com with SMTP id e84-v6so1570844ybb.0 for <ipv6@ietf.org>; Tue, 03 Jul 2018 20:54:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=984/yd2swtJ1ZqaAdiOsCkNd+BR5t21AamtYpCiIx64=; b=pvyvheP0+nDka37jHtg5PFepJeNsfmfC7RGCmnj+DMNhbFO6Q074VHgNtD15rQfA/s 3sdPLldw+6010T2v8d0cIrt9SNe+HC5LAck6IsQrcj/7T7Tc/3It4XuJi4zqPnhkn9/n V0M0I1p/votEWR3CaK25Zk/3iPtU20bnbBzKwCBQWAJTbOelB4DOcEbV/wnI4c0FVPcG 3zao8Sjj/cKLKrbQhuaQXNOET8HmhGRQhHEL8w3qlg6smPxtX5V9On9kcD9lYBLgKw5P d/YW8wCPlhfIwYyYCWnp6Cwl22QV2NEi8y0bJ24w/M4/gf+pICqLnXEu2AHjvK5yukYC aQDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=984/yd2swtJ1ZqaAdiOsCkNd+BR5t21AamtYpCiIx64=; b=URVJub8Ep5CJod4XT1DKCc1nWGqgTgQUHxMkYwnS2l93h37pqFKnQwsRxQFo+jnuxm +DWLGmAnBQQz1Lor91MX38PTZDoqgWUXqhGmTZMSHIV0kbvaQRnnHQtXPxc5dEnuCBEh fFu8RHGAIizOmNTN0FoHniR8yRK+vDd5QCva/7UhcBVEc9TfM8k1lLasb+2aHsdqH6W5 wW/708hlftyn51SiLvDQN2OER/u7oaC30M1y9kaom9DoZBb2SChrUU+sWe2Baq3ZW/ug FQQByvqddURcgteMmzE+U88j8XWjkQus8nPz746sW9/n6qSCtOvubdXzrsDSaZKRaAB9 Sbkg==
X-Gm-Message-State: APt69E097CS8XFB77cZOK3bTXA3rqHJoWXKZ89NoYxyDanYmVLHMfxsf 1S+RX1YhtriM4m+U2wU59KWwWPF599SDR7542qLD0A==
X-Google-Smtp-Source: AAOMgpfBdhXB0MELUVgQvQSXTIv6FqWKuymYhwj8p7NfPna8gpxe6CkLPyfoweUBPIDK3pgXKnrvTerheXJJaZRKPFU=
X-Received: by 2002:a25:acd0:: with SMTP id x16-v6mr167438ybd.407.1530676470618; Tue, 03 Jul 2018 20:54:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a81:6b83:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 20:53:50 -0700 (PDT)
In-Reply-To: <6a9387bb-e004-a3c4-88ed-c990d723aa6b@gmail.com>
References: <153065994532.5103.6344190871409427105.idtracker@ietfa.amsl.com> <6a9387bb-e004-a3c4-88ed-c990d723aa6b@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 03 Jul 2018 20:53:50 -0700
Message-ID: <CABcZeBMv2xJVssPm_O5XKALQRS9X6Bc9=R+LR8p2YEuvQRx1nQ@mail.gmail.com>
Subject: Re: Eric Rescorla's No Objection on draft-ietf-6man-rfc6434-bis-08: (with COMMENT)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: The IESG <iesg@ietf.org>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, draft-ietf-6man-rfc6434-bis@ietf.org, 6man Chairs <6man-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004c2e7d0570246317"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5PSp8gVFJK_vPeHSL2h_rvg88nI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 04 Jul 2018 03:54:35 -0000

On Tue, Jul 3, 2018 at 8:49 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 04/07/2018 11:19, Eric Rescorla wrote:
> ...
> > S 5.1.
> >>      field as defined in the IPv6 Flow Label specification [RFC6437].
> >>      Forwarding nodes such as routers and load distributors MUST NOT
> >>      depend only on Flow Label values being uniformly distributed.  It
> is
> >>      RECOMMENDED that source hosts support the flow label by setting the
> >>      Flow Label field for all packets of a given flow to the same value
> >>      chosen from an approximation to a discrete uniform distribution.
> >
> > Is there a reason you are using "approximation" here?
> >
>
> RFC6437 says:
>
>    In statistics, a discrete uniform distribution is defined as a
>    probability distribution in which each value in a given range of
>    equally spaced values (such as a sequence of integers) is equally
>    likely to be chosen as the next value.  The values in such a
>    distribution exhibit both variability and unguessability.  Thus, as
>    specified in Section 3, an approximation to a discrete uniform
>    distribution is preferable as the source of flow label values.
>    Intentionally, there are no precise mathematical requirements placed
>    on the distribution or the method used to achieve such a
>    distribution.
>
> [and in Section 3]
>
>    It is therefore RECOMMENDED
>    that source hosts support the flow label by setting the flow label
>    field for all packets of a given flow to the same value chosen from
>    an approximation to a discrete uniform distribution.  Both stateful
>    and stateless methods of assigning a value could be used, but it is
>    outside the scope of this specification to mandate an algorithm.
>
> The reason for saying "approximate" is basically that at least one
> mathematician (my colleague Prof. Cristian Calude) pointed out that
> (apart from quantum processes) there is no way to generate a truly
> random distribution. So you can regard it as mathematical pedantry;
> I have no strong feelings whether that's useful in the present draft.
>

Yeah, I tend to think "approximate" is a bit nitpicky here, but this is a
comment, so I leave it to the author to deal with it as they see fit.

-Ekr


>    Brian
>