Re: Alvaro Retana's No Objection on draft-ietf-6man-rfc4941bis-11: (with COMMENT)

Fernando Gont <fgont@si6networks.com> Tue, 20 October 2020 19:37 UTC

Return-Path: <fgont@si6networks.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 367AF3A134A; Tue, 20 Oct 2020 12:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Level:
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ZNdwhMuJdgF3; Tue, 20 Oct 2020 12:37:55 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78EF83A1347; Tue, 20 Oct 2020 12:37:51 -0700 (PDT)
Received: from [IPv6:2800:810:464:b9c:69b8:4602:916c:a007] (unknown [IPv6:2800:810:464:b9c:69b8:4602:916c:a007]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 111642839E9; Tue, 20 Oct 2020 19:37:45 +0000 (UTC)
Subject: Re: Alvaro Retana's No Objection on draft-ietf-6man-rfc4941bis-11: (with COMMENT)
To: Alvaro Retana <aretana.ietf@gmail.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-6man-rfc4941bis@ietf.org, 6man-chairs@ietf.org, otroan@employees.org, ipv6@ietf.org
References: <160313378187.7246.8644532996867850166@ietfa.amsl.com> <d0771c09-a0b6-95b3-ff0c-29cfa9fba7c5@si6networks.com> <CAMMESsz88x2BAF3c6RGnCFNQqgaiF1HD7EH9a=4XgrBnHsPQRA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <85310bac-c72b-57b7-fe0e-d6a494b8d446@si6networks.com>
Date: Tue, 20 Oct 2020 15:51:40 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CAMMESsz88x2BAF3c6RGnCFNQqgaiF1HD7EH9a=4XgrBnHsPQRA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_LKz86TN_ZH8hiwzHLBgHojBZhE>
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: Tue, 20 Oct 2020 19:37:57 -0000

Hello, Alvaro,

On 20/10/20 15:34, Alvaro Retana wrote:
[....]
>>> Please clarify the text one way or the other: by eliminating "examples"
>>> from §3.3, or removing the text in parenthesis in §3.4.
>>
>> How about changing that paragraph as:
>>
>> OLD:
>> 6. New temporary addresses MUST be created by appending a randomized
>> interface identifier (generated as described in Section 3.3 of
>> this document) to the prefix that was received.
>>
>> NEW:
>> 6. New temporary addresses MUST be created by appending a randomized
>> interface identifier to the prefix that was received. The
>> randomized interface identifier MUST comply with the design
>> guidelines from Section 3.1. Section 3.3 specify some example
>> algorithms that comply with the aforementioned design goals.
> 
> 
> I'm ok with this suggestion, except for the "MUST comply with the
> design guidelines from Section 3.1" part.  There's no interoperability
> required to justify normatively pointing at §3.1, most of the bullets
> there don't apply to the generation of random IIDs, and I don't see a
> strong reference to §3.1 anywhere else in the text.
> 
> I would be very happy by simply changing that second "MUST" to "must".
> 
> Having said that, my comment was non-blocking, so I trust you and the
> Responsible AD to make the right decision.

Ok. Question for Erik: which of the three proposed changes (or Alvaro's 
suggested s/MUST/must/) would be best for you?

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492