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

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Mon, 13 July 2020 12:41 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 AA7A33A116A for <ipv6@ietfa.amsl.com>; Mon, 13 Jul 2020 05:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.267, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 e9-qp0gRyux8 for <ipv6@ietfa.amsl.com>; Mon, 13 Jul 2020 05:41:05 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B98E3A1161 for <ipv6@ietf.org>; Mon, 13 Jul 2020 05:41:05 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1juxlS-0000GLC; Mon, 13 Jul 2020 14:40:58 +0200
Message-Id: <m1juxlS-0000GLC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Subject: Re: Adoption Call for "Improving the Robustness of Stateless Address Autoconfiguration (SLAAC) to Flash Renumbering Events"
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
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>
In-reply-to: Your message of "Sun, 12 Jul 2020 13:59:54 +0900 ." <CAKD1Yr1nOPVatXsG+1gdQEpBDmMc6-iby6x_vEN9cVpSY6sNpg@mail.gmail.com>
Date: Mon, 13 Jul 2020 14:40:57 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aieJVuidUIvogLu9mYMRAWEOwII>
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 12:41:07 -0000

>    I think there are parts of the
>    document that many participants agree on, and we should keep
>    them, so the document can advance more easily.  It seems pretty
>    likely to me that if we remove section 4.5 from the document,
>    a lot of the objections would go away and we would end up with
>    a document that would be much more likely to be adopted without
>    controversy, and advance to publication quickly and without lots
>    of disagreement.  We can always put the more controversial
>    changes into a separate document which then can be debated
>    separately.

In my opinion, Section 4.5 is that part that actually solves the problem, 
i.e. how can a host handle a flash renumbering situation.

I do not object moving the changes to valid and preferred times to a 
separate document, however, that doesn't deal with problem that this document
tries to solve.

My recollection of the IPv6-only flag is that it failed in sunset4 and then
failed here as well. Note that during the IPv6-only flag discussion it was
proposed that DHCPv4 was used to signal lack of IPv4, which was reject by the 
authors. It is not a surprise that a solution that involves DHCPv4 met a lot
less resistance, however the IPv6-only DHCP option does not solve what the
authors of the IPv6-only flag tried to do.

If we only a adopt a document when it has rough consensus, then why adopt a
document at all, and not go to WGLC directly?