Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 11 May 2019 01:12 UTC

Return-Path: <brian.e.carpenter@gmail.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 CD8AA120224 for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 18:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jzzy9HdtidSY for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 18:12:27 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (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 ED2C912017C for <ipv6@ietf.org>; Fri, 10 May 2019 18:12:26 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id i21so3778027pgi.12 for <ipv6@ietf.org>; Fri, 10 May 2019 18:12:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=I3KNqFEzrEFHrQZQmkPFuyd7ewwSu/Pwmgcc+eZF/0Y=; b=Fgf324PS80kEB8CjKJA7E/y0HOhLW8MprQN9pZYdkyJxiGqv+3DbwT/3KRjH3aSM6+ NWMm6kkanDniTn0Tk/XVU/egBcdxFjsw39R1r6gZjRQxhIlDm46x3GGNUbw5M+V2S9e8 vC2UAwJISOUr2auhUdjfXD7/mx/5wbZWvVqB7ragGAtfcLDWgtGZS3/1+c6Qhfb9SIbX xEGXu2/Z4xMrbZc66SlMoFZXekzNfJbDcoEMOWNymm0JFXkYmAD0/AEKbhuwiMV0bIiC 7/kkunZzawDeQGhgBblsdD/SFJvrfSIXKZ6+14NI5u1/FAHK4XSvFkMHpZhTOoGxjuqr VwXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=I3KNqFEzrEFHrQZQmkPFuyd7ewwSu/Pwmgcc+eZF/0Y=; b=nY5lMFu+0KfWXcq1prK3TWm9SRk5MG3N4OGXnk3jLjuMcvYgiHuZAv7oF3QnOlg3mk OecRWfPTCqHd1v8gIVWkLrwYnI9S/B9BxqQyZmo+PpPbrdeZXjij1t/R17rzeE/zuKDW jlXV9soz9va/izOvOKvHpsZZglFxWZza1EAPAl3FsUy/L0IV+2pfFsE5TyDoeoALGKud gMylkFrmCtflgegc20dwiTU7aF50rxYm8voMRiYQfnC68Vw9wsoB4dHsILMno7iVzTt1 SiY4/UrP0kCQlJcKoEsjIXSVP/LUhzhi60uiRJCBMC6N6UsJQVj/BUxDf8z3bdgdV0/X xoDQ==
X-Gm-Message-State: APjAAAWoViIjELiXYgvqYHb4DMioPwNpshqxBAOIGuJKepT6gG5Mzh5O EffjIs9tmo0nyLfO1OCjnwjJ2UAA
X-Google-Smtp-Source: APXvYqzBYMiQoGiQ8O3NW0PI8VsagOy0UpXsFoifYro4D2slvM7+4TrhvG4z5FVVjKopNopnj4RNQQ==
X-Received: by 2002:a63:1701:: with SMTP id x1mr17113318pgl.153.1557537146073; Fri, 10 May 2019 18:12:26 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id n7sm8647601pff.45.2019.05.10.18.12.24 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 May 2019 18:12:25 -0700 (PDT)
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: ipv6@ietf.org
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <alpine.DEB.2.20.1905091054560.1824@uplift.swm.pp.se> <CAJE_bqeDE9bwkMm63p_Dz+ha7_tLa38wA27YRK2n59D1g-qLrA@mail.gmail.com> <alpine.DEB.2.20.1905102204270.1824@uplift.swm.pp.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <98d88cbb-fa92-42b0-f707-37b4eedf4782@gmail.com>
Date: Sat, 11 May 2019 13:12:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.20.1905102204270.1824@uplift.swm.pp.se>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/czIa2K0Vy3Sd_oqTJ8YHXc1fzt8>
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: Sat, 11 May 2019 01:12:29 -0000

On 11-May-19 08:08, Mikael Abrahamsson wrote:
> On Fri, 10 May 2019, 神明達哉 wrote:
> 
>>> "   A host that receives only RAs with the flag set to 1 SHOULD NOT
>>>     attempt any IPv4 operations, unless it subsequently receives at least
>>>     one RA with the flag set to zero.  As soon as such an RA is received,
>>>     IPv4 operations MAY be started.
>>> "
>>
>> This text doesn't read to me that "a host SHOULD NOT start IPv4
>> operations until it has received an RA with the ipv6only-flag
>> cleared".  At least literally, it just talks about the host's behavior
>> *after* it receives an RA with ipv6only-flag on.
> 
> Some people seems to have read "attempt" in the above text as "should not 
> start", meaning it should delay starting IPv4 operations until it knows 
> about the status of this flag (the host has no idea about the flag status 
> until it has received RAs at attach time).
> 
> If we don't want this to happen then the current text in -05 is not clear 
> enough on this case. I believe several people have voiced their opinion 
> that they would accept the flag being part of the heuristic of deciding 
> whether to continue doing DHCPv4 and/or IPv4 LL (or not). The -05 text 
> doesn't seem to actually say this, so it should be changed?

It's always been my opinion that the flag is input to a heuristic; but
from time to time we've had pushback asking for it to be more definitive.

Since I'm remarkably bad at predicting the future, despite much practice,
I really don't know what will be the right heuristic ten or twenty years
from now.

(The Google statistics were up to 28.02% IPv6 on May 4th. The future seems
to be getting closer.)

    Brian