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

"Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Fri, 10 May 2019 20:59 UTC

Return-Path: <bzeeb-lists@lists.zabbadoz.net>
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 B04AE1200C1 for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 13:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 U9GxoqCqXUwc for <ipv6@ietfa.amsl.com>; Fri, 10 May 2019 13:59:36 -0700 (PDT)
Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE920120052 for <ipv6@ietf.org>; Fri, 10 May 2019 13:59:36 -0700 (PDT)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id EF9048D4A179; Fri, 10 May 2019 20:59:33 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id CB4C3E7085E; Fri, 10 May 2019 20:59:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id nnNcAIIDEZRX; Fri, 10 May 2019 20:59:31 +0000 (UTC)
Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id D0D9DE7085D; Fri, 10 May 2019 20:59:29 +0000 (UTC)
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: 神明達哉 <jinmei@wide.ad.jp>, 6man WG <ipv6@ietf.org>
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
Date: Fri, 10 May 2019 20:59:29 +0000
X-Mailer: MailMate (2.0BETAr6137)
Message-ID: <7C73EFE8-5459-424E-998B-83D01485CBC9@lists.zabbadoz.net>
In-Reply-To: <alpine.DEB.2.20.1905102204270.1824@uplift.swm.pp.se>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/yL0Huw2r-Pz5DtWEny5JCq__m-M>
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: Fri, 10 May 2019 20:59:39 -0000

On 10 May 2019, at 20: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?

As a non-native English speaker, would adding a “.. attempt any 
 >>further<< IPv4 operations, ..” reflect what you mean?

/bz