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

Lorenzo Colitti <lorenzo@google.com> Mon, 26 October 2020 00:52 UTC

Return-Path: <lorenzo@google.com>
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 80C5B3A171F for <dhcwg@ietfa.amsl.com>; Sun, 25 Oct 2020 17:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 YQAeghsQ8fhl for <dhcwg@ietfa.amsl.com>; Sun, 25 Oct 2020 17:52:29 -0700 (PDT)
Received: from mail-il1-x141.google.com (mail-il1-x141.google.com [IPv6:2607:f8b0:4864:20::141]) (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 2ABB93A171E for <dhcwg@ietf.org>; Sun, 25 Oct 2020 17:52:29 -0700 (PDT)
Received: by mail-il1-x141.google.com with SMTP id q1so6735005ilt.6 for <dhcwg@ietf.org>; Sun, 25 Oct 2020 17:52:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=opZrg+ecCz0rBgzUGIb8xU31Dry7/Pa5ifqVgibmmQg=; b=sqeTlujGnGYBDmfZJ0BAxwD5f6tw4mg+1peGKzEuLMrLV8+T1H8NXh6pWyR/DmJ0wC 7J/L/LIwiEzaD5nS279MIQDH6NEwCt82WUK8HrPdt9fska8oqnXGPcQYNq2SJw14rxSB 3eaGG6UkCJyFOqRXU+zHpSf3GuW5p3lEthOofXthQEKLYIIzS2OnN+ddhypV0Qsj+9fl Oe85E3AVgTG+pxNkQjCxhyBpY3VMebJXUR6KHzntFDNtH+3w9cVthu6ujsYBWlkR+WUU XEobn5LCykh25CcbmoqqlSO8p+oVjt4Z5DCXFoZlqHPAgWbAjaUWy/TWmjjGMSVJ+1Vy lWmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=opZrg+ecCz0rBgzUGIb8xU31Dry7/Pa5ifqVgibmmQg=; b=IlQsdIngc2xSPZf6rnEHKjjFQnyqtHiXd7E8C6StIZ5KNMF4UwkPWnVDBofli8A2f7 ckz/WcJiWfV8suA2dV1PBzmB4wIc9G1NWvzo6l/RljN7elQ0vkjemQizwHkJIXRdWVJ3 nNYaS/P/rZPg+4/Q8h003K1sPLjcjHTXmom26XIUlvgyhc/kVQO5V8/Fp85SCEHP4mkg 3lgURo0EXdhCn4cK0niyqV9bktKtHMEFEzasa9Zb74RmMXCEoPAOIzSCQFv4tY5AXw4M xgmws4yiodpr3sRfmhZNRdNVrAW+8ngWVdvy/c2RykPQmQo1YD0jffSONSmVobW/VtZf vqyA==
X-Gm-Message-State: AOAM533k2kWV/xM65GdvE9uotdv4qrkD1E/5GENTd2WT6TeDO+x9gPc2 CH7MvRXcLsjQmY+yM/Qq5BofCHr3/Ssay2Pw0H5nO15/Kl4FeA==
X-Google-Smtp-Source: ABdhPJwL3MGZwIRyDDEjBnDTbXwhwN7aMfFtyBOM4Bp1om1ay9Tz6LUGx2eRY4ZmUswLABhC8J1gJmmQ9xmSp6Q2T24=
X-Received: by 2002:a05:6e02:931:: with SMTP id o17mr9233228ilt.273.1603673548179; Sun, 25 Oct 2020 17:52:28 -0700 (PDT)
MIME-Version: 1.0
References: <20201017125300.02DF3F40710@rfc-editor.org> <e935457a-eb2c-93a6-6ffe-959d7e358f17@marples.name>
In-Reply-To: <e935457a-eb2c-93a6-6ffe-959d7e358f17@marples.name>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 26 Oct 2020 09:52:16 +0900
Message-ID: <CAKD1Yr0j7ip7axs8Mu_jr23aj28fR5pWADSa1knPR4hVrMbo9g@mail.gmail.com>
To: Roy Marples <roy=40marples.name@dmarc.ietf.org>
Cc: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002d48a105b288582b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/uaexKpVXhzuJVD-Cas-FxunvQC0>
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: Mon, 26 Oct 2020 00:52:31 -0000

On Mon, Oct 26, 2020 at 5:06 AM Roy Marples <roy=
40marples.name@dmarc.ietf.org> wrote:

> 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.
>

While it's true that the SELECTING state is not explicitly mentioned, I
think it's implicitly dealt with by this text:

   If the client waits for multiple DHCPOFFER responses and selects one
   of them, it MUST follow the processing for the IPv6-Only Preferred
   option based on the selected response.  A client MAY use the presence
   of the IPv6-Only Preferred option as a selection criterion.


> 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.
>

I think this is documented in the text that you quoted above. If the client
is in RENEWING or REBINDING, it SHOULD continue to use the assigned IPv4
address. That means accept the DHCPACK, continue to use the address, and
later, when the appropriate timers fire, enter RENEWING and REBINDING as
specified by RFC 2131.

Cheers,
Lorenzo