Re: Adoption Call for "Improving the Robustness of Stateless Address Autoconfiguration (SLAAC) to Flash Renumbering Events"

Fernando Gont <fgont@si6networks.com> Mon, 13 July 2020 16:54 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 C4DEC3A164C for <ipv6@ietfa.amsl.com>; Mon, 13 Jul 2020 09:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 GAXJudnL5apX for <ipv6@ietfa.amsl.com>; Mon, 13 Jul 2020 09:54:00 -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 76B093A161C for <ipv6@ietf.org>; Mon, 13 Jul 2020 09:53:58 -0700 (PDT)
Received: from [IPv6:2800:810:464:1f7:603e:8516:bae8:27ff] (unknown [IPv6:2800:810:464:1f7:603e:8516:bae8:27ff]) (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 95FEA280CE6; Mon, 13 Jul 2020 16:53:52 +0000 (UTC)
Subject: Re: Adoption Call for "Improving the Robustness of Stateless Address Autoconfiguration (SLAAC) to Flash Renumbering Events"
To: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IPv6 List <ipv6@ietf.org>
References: <CC295D49-5981-41C3-B4DB-E064D66616CE@gmail.com> <CAFU7BAQX8B2n3FFjQ3h-9VLP7zR=zy0nO0z7bEtz3KXZ7wp=eg@mail.gmail.com> <42267b42-2e29-1bc9-1440-e1a847002efd@gmail.com> <CAKD1Yr1nOPVatXsG+1gdQEpBDmMc6-iby6x_vEN9cVpSY6sNpg@mail.gmail.com> <15379.1594601257@localhost> <CAKD1Yr1edFvRsUwcgwB2LyakSVgof+i9tBtBjf6Y6KchiLLL-A@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <9c1d6c3b-bedd-757a-261d-ff40f8875d72@si6networks.com>
Date: Mon, 13 Jul 2020 13:43:35 -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: <CAKD1Yr1edFvRsUwcgwB2LyakSVgof+i9tBtBjf6Y6KchiLLL-A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/DTMa-W3WSuhb2V2geZ9C_suLV8c>
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: Mon, 13 Jul 2020 16:54:06 -0000

On 13/7/20 00:52, Lorenzo Colitti wrote:
> On Mon, Jul 13, 2020 at 9:47 AM Michael Richardson 
> <mcr+ietf@sandelman..ca <mailto:mcr%2Bietf@sandelman.ca>> wrote:
[...]
 >
> Actually I don't think so. I think the problem we faced is that once a 
> document is adopted it becomes a WG document and the sunk cost fallacy 
> prompts participants to continue to work on it. If instead we had 
> decided that there was not enough consensus to adopt the IPv6-only flag, 
> then the authors could have looked for other solutions. As it happened 
> the solution that ended up being more successful wasn't even in this WG, 
> it was in dhc.

Participants spend a quite different amount on energy on individual 
documents vs on wg documents (or documents that would otherwise clearly 
become wg documents).

As such, it is no surprise that when the ipv6-only flag I-D became a wg 
document, more people looked into it, and some felt that the document 
wasn't in shape to ship or continue progress.

Similarly, most of the folks who have had objections to Section to 4.5, 
had not argued against Section 4.5, and have also noted how they think 
Section 4.5 should be tweaked or replaced (you, for one, made one of 
such suggestions).

It would seem to me that adoption of a document is indeed about the 
deciding to actively work on a document, and, in the case of Section 
4.5, such work is what's needed to replace or tweak Section 4.5 such 
that the WG is happy with it.

I think it is hard to make any sort of progress on anything if folks are 
simply essentially going to object against text upon WG call for 
adoption without much detail, and without hints or guidance regarding 
how their objections can be addressed.

My understanding is that wg adoption implies the desire of the wg to 
actively work on a document, such that objections that can be addresses 
are addresses, and otherwise text that cannot be improved for the wg to 
have consensus is stripped out or moved into a separate document.

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