Re: [dhcwg] RFC 8925 on IPv6-Only Preferred Option for DHCPv4

Roy Marples <roy@marples.name> Sun, 25 October 2020 20:06 UTC

Return-Path: <roy@marples.name>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF573A15C5 for <dhcwg@ietfa.amsl.com>; Sun, 25 Oct 2020 13:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.325
X-Spam-Level:
X-Spam-Status: No, score=-2.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.247, NO_DNS_FOR_FROM=0.001, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=marples.name
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 1lSd5uTAJfCs for <dhcwg@ietfa.amsl.com>; Sun, 25 Oct 2020 13:06:19 -0700 (PDT)
Received: from relay2.marples.name (relay2.marples.name [IPv6:2a00:da00:1800:80d6::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE1793A15C0 for <dhcwg@ietf.org>; Sun, 25 Oct 2020 13:06:19 -0700 (PDT)
Received: from mail.marples.name (mail.marples.name [IPv6:2001:470:690c:1::59]) by relay2.marples.name (Postfix) with ESMTPS id 98515854 for <dhcwg@ietf.org>; Sun, 25 Oct 2020 20:06:11 +0000 (GMT)
Received: from [10.73.1.30] (uberpc.marples.name [10.73.1.30]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail.marples.name (Postfix) with ESMTPSA id 0B6245164 for <dhcwg@ietf.org>; Sun, 25 Oct 2020 20:06:11 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marples.name; s=mail; t=1603656371; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=O12Xst3ivju2/Nptzj0TC1h9mj79P4mlJ1Se8iFZ/Sk=; b=YUn0UgjXJhnzJjfGLPNdDchzL32ZK0nJp326KfP5JNbf3Zpndk+Ocx6Gt8kg14d+vRKdnb 5sUmWuQZMB4XB0gVTVybj9t3ek8IqsPeGq1i7kKrTImbSGFz9fyUC6h/wyLqpp7FHdDE70 Jp3bwvrDMqMr2f1IiGHF7HGRfwov4r8=
To: dhcwg@ietf.org
References: <20201017125300.02DF3F40710@rfc-editor.org>
From: Roy Marples <roy@marples.name>
Message-ID: <e935457a-eb2c-93a6-6ffe-959d7e358f17@marples.name>
Date: Sun, 25 Oct 2020 20:06:10 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <20201017125300.02DF3F40710@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/TBC4ruKmZTuJTB7XZT05tFVNj8U>
Subject: Re: [dhcwg] RFC 8925 on IPv6-Only Preferred Option for DHCPv4
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 20:06:21 -0000

On 17/10/2020 13:53, rfc-editor@rfc-editor.org wrote:
> A new Request for Comments is now available in online RFC libraries.
> 
>          
>          RFC 8925
> 
>          Title:      IPv6-Only Preferred Option for DHCPv4

Just reading through this and I find this in section 3.2

-------------------------------------------------------------------------------
The IPv6-Only Preferred option SHOULD be included in the Parameter Request List 
in DHCPREQUEST messages (after receiving a DHCPOFFER without this option, for an 
INIT-REBOOT, or when renewing or rebinding a leased address). If the DHCPv4 
server responds with a DHCPACK that includes the IPv6-Only Preferred option, the 
client's behavior depends on the client's state. If the client is in the 
INIT-REBOOT state, it SHOULD stop the DHCPv4 configuration process or disable 
the IPv4 stack completely for V6ONLY_WAIT seconds or until the network 
attachment event, whichever happens first. It also MAY send a DHCPRELEASE 
message. If the client is in any other state, it SHOULD continue to use the 
assigned IPv4 address until further DHCPv4 reconfiguration events.
-------------------------------------------------------------------------------

It's the last line of the paragraph which is of interest. It implies that this 
option only works in the INIT-REBOOT state. The lack of the SELECTING state is 
pretty glaring but a minor omission.

Am I correct in thinking that RENEWING and REBINDING states pretty much ignore 
this option if it was absent and is now present? Or is the intent to stop using 
the address when in these states as they are "DHCPv6 reconfiguaration events"?
Or just wait until it naturally expires? It's not clear what the expected action 
here should be.

Roy