Re: Last Call: <draft-ietf-6man-rfc4941bis-10.txt> (Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6) to Proposed Standard

Nick Hilliard <nick@foobar.org> Thu, 10 September 2020 11:59 UTC

Return-Path: <nick@foobar.org>
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 684B13A094C; Thu, 10 Sep 2020 04:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level:
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.948, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 HZThYiqn7SoB; Thu, 10 Sep 2020 04:58:59 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71A1D3A094B; Thu, 10 Sep 2020 04:58:58 -0700 (PDT)
X-Envelope-To: last-call@ietf.org
Received: from cupcake.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id 08ABwtox026228 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2020 12:58:56 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be cupcake.local
Subject: Re: Last Call: <draft-ietf-6man-rfc4941bis-10.txt> (Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6) to Proposed Standard
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Cc: last-call@ietf.org, draft-ietf-6man-rfc4941bis@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>, 6man Chairs <6man-chairs@ietf.org>
References: <159969199185.9541.8823907519726516405@ietfa.amsl.com> <CAKD1Yr1fVnhr3ZM64vLxtXg-9WAKemDuzW2gMupviv-i9V-GiA@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <697849ac-423c-cc55-1acd-fbd624515cf3@foobar.org>
Date: Thu, 10 Sep 2020 12:58:53 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:52.0) Gecko/20100101 PostboxApp/7.0.28
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1fVnhr3ZM64vLxtXg-9WAKemDuzW2gMupviv-i9V-GiA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/fGAUZRU0FXkrlhNj3mrkfSWU45w>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 10 Sep 2020 11:59:01 -0000

Lorenzo Colitti wrote on 10/09/2020 12:26:
> 1. I think it should not include section 3.3.2. The reason is that it 
> needlessly suggests an algorithm that is much more complex than simply 
> using an existing random number generator which all nodes likely already 
> have.

in theory you're probably right.  In practice, some vendors take serious 
short-cuts when it comes to prngs, particularly in the bulk-produced, 
low-cost device market. This will particularly be an issue for IoT and 
on wifi where DAD's single-shot approach is intolerant of loss.

3.3.2 only ensures that extra entropy is injected.  This probably isn't 
a bad thing.

Also the algorithm is based on rfc7217, so if there's a problem with 
this approach then that's possibly a wider discussion.

> 2. I think the text mentioning shorter IID lengths (3.3.1 bullet #2) is 
> not useful to implementers, because all it says is that it is possible 
> to implement a behaviour that for in all practical cases is forbidden by 
> RFC 4291.

It refers non-normatively to 7421, which provides a useful and nuanced 
discussion of the issue.  There doesn't seem to be any particular 
ambiguity here?

Nick