Re: [v6ops] IPv6-Only Preferred DHCPv4 option

Ted Lemon <mellon@fugue.com> Mon, 09 December 2019 14:58 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B049B12000F for <v6ops@ietfa.amsl.com>; Mon, 9 Dec 2019 06:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Khp_r5sMR84V for <v6ops@ietfa.amsl.com>; Mon, 9 Dec 2019 06:58:18 -0800 (PST)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (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 04D7E1200B6 for <v6ops@ietf.org>; Mon, 9 Dec 2019 06:58:18 -0800 (PST)
Received: by mail-pg1-x52f.google.com with SMTP id s64so537257pgb.9 for <v6ops@ietf.org>; Mon, 09 Dec 2019 06:58:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=8Vh5nhH1lUDKBMQt25+6cxJ7yrfseUvHXvfn3i4ZOBQ=; b=zr9Bjk7yzCo20JpXQikh1cUnsyCuTgEo12bpPTf1Hnrg37SKAbZzaSqFAFSxlwcklP JrGhCqV9Cvd2HJHgUBv8RcyRhGkxYXxySDJ6zDkuskbpJqToGnf2W5WP2D4pkgtagxOh UlvdEVlRHMblXvDl/ZTLuS6zT8Rh0A+3GBdwDakMEp4qWtk6meN95xgfhDAoY8ZyURI8 7dvL2fkHDAHlvQ3oH7LOwMu4itWxjwbPsQtXHGLdDPshTFOt0g+lNPNmvz8XFgcf4Tk+ Ohb8Pfi4Ohi/iMy+/04baWoWQdb19uAUAWGNP3o+ZzvxdTnJKGDOqPCyMPKug+LEY0r4 nO+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=8Vh5nhH1lUDKBMQt25+6cxJ7yrfseUvHXvfn3i4ZOBQ=; b=OSNCvIyf3NX4JdNAdbVjx/Ia5D7qd0x2maS1sUJ4CTd4fMHIhF6Pwsx48eBHY9g6Je ue9N4XnlAKT7Ac0oe53NgmWRx4JR4tagZT6xPlmqyZbxa+byccltLBb6HUaaXLavrX7M zst9To3mUKUU+uk3K7lJBkj+FvYzWADLiZ8ESp3rFbTcAhAOiGZBT4+9cWY5M7sCOVKL D27D2umfBaxMwKQGvJcFZDVh7b64LDZWbPjYiucFzfVCqQPTVgh7j7Txw39wtimYWhrN LMlkQ9E+yFW2ckaozedTInNmfNoJDeo1x4PY0bmiTz/R/nEvO+gqv6UCQq6MtLvp6m7U 2gCA==
X-Gm-Message-State: APjAAAWoGX6uCu206pP381Skmzgaj6YPOfiiHMOPpvDz2ZY1t0ngCGVy UqQ1PFstqZt+p7rM0KTiNNyr/A==
X-Google-Smtp-Source: APXvYqwZQ0vqwP6l/LUWiy5vLcAKhE2DQxEMfVZLSf5J0nYwXaaYfqqbX6C6pmwZ1ShDkrdgtsbHmQ==
X-Received: by 2002:a63:6704:: with SMTP id b4mr19609101pgc.424.1575903497366; Mon, 09 Dec 2019 06:58:17 -0800 (PST)
Received: from encantada.scv.apple.com ([17.192.138.54]) by smtp.gmail.com with ESMTPSA id j18sm25321492pgk.1.2019.12.09.06.58.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Dec 2019 06:58:16 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <0E2261B8-032E-43C2-ABFE-4D68A4E47FD3@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DF636303-767E-4706-8711-5C9CFDC782A1"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3600\))
Date: Mon, 09 Dec 2019 06:58:15 -0800
In-Reply-To: <F5AAD5B7-22BD-4474-9A1E-1A97AFFE47FC@cisco.com>
Cc: Lorenzo Colitti <lorenzo@google.com>, V6 Ops List <v6ops@ietf.org>
To: "Bernie Volz (volz)" <volz@cisco.com>
References: <9102C9A8-DA3A-4460-88AD-13E24561B901@cisco.com> <CDC50564-D289-4E73-9924-4F00E93F9C7C@fugue.com> <F5AAD5B7-22BD-4474-9A1E-1A97AFFE47FC@cisco.com>
X-Mailer: Apple Mail (2.3600)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/zTt81HaMUu5E4BtGgUUTCUzirKA>
Subject: Re: [v6ops] IPv6-Only Preferred DHCPv4 option
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Dec 2019 14:58:21 -0000

On Dec 9, 2019, at 6:31 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
> No, I am strongly arguing for no change.

Yes, but why?

My concern here is for the end state in ten years.   In ten years, it should be the case that virtually every client supports this feature, and virtually every network offers it.  We don’t want there to be a DHCPv4 server on this network at all.   What we want is a dumb little thing sitting in the router on the link that, when it gets a DHCPDISCOVER, immediately responds with a directive to use IPv6.   So I want to optimize for what that little stub should look like, /not/ what your solution should look like now.

I think it’s pretty clear that that little stub should not offer an IPv4 address at all.  What is the utility of offering one?   We’ve seen several proposed hacks for this, but they are just that: hacks.  They are additional complexity we don’t need.

So that leads me to want you to think really hard about why you want to do something else, and not just strongly argue for no change.   Would you mind doing that?  It’s quite possible that there is some problem with what I’m proposing that you haven’t yet articulated, because you’re satisfied by the superficial answer.  It would be nice to figure out why, for example, the compromise I proposed is unacceptable to you.  What is bad about that solution?  You could, if you chose, make no changes to your server forever, and I could implement my trivial stub in the router, and I think we’d both be happy.

Why do you think we wouldn’t both be happy?