Re: [v6ops] IPv6-Only Preferred DHCPv4 option

Jen Linkova <furry13@gmail.com> Mon, 09 December 2019 01:48 UTC

Return-Path: <furry13@gmail.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 C7D481200CC; Sun, 8 Dec 2019 17:48:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 eGrbqc1I_eKw; Sun, 8 Dec 2019 17:48:00 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 89D5312007C; Sun, 8 Dec 2019 17:48:00 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id g15so11677641qka.8; Sun, 08 Dec 2019 17:48:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=oYnWaUoZzty5Inf6hsSqeDCfitix0GWLkCyFEkn3oEE=; b=j3lud/0+3UhCZ9p7l89tywmF7yjGGTT4Qq9KewwGzc0kao8ed16yyLCRF4nlopM5l5 /PTxc4rzeCMo/27QKbJbeDWQ0HTw25juLwNO9HxH3OGijni/YC1OBTfmKhewhiobzJ/6 vasxarzN6T7JiKWE0QvspRhWJPwOAjc0GgHwXkfgcL+sXDnSs3OT3m5J5fFBML9w8y0x a5QsupztNNkym8zgYfXGq82botUXrpoHEuK+gdKq+CqovERFI1KWYMVUFjYuN9iEXCgP 731yuKk8mRT7xCmcGqeMF70IysWLncM/4Yffr8OoQdyzjzNu0G4uo0furSiLif0BLDdx 94/w==
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:content-transfer-encoding; bh=oYnWaUoZzty5Inf6hsSqeDCfitix0GWLkCyFEkn3oEE=; b=iyECYi5+GzFRKlbOXOJaNcL5iM1Qhwbe0tw1ElgdTFWAEzP3z3TQKkS7WR3BQNKX/8 st4kZOSd9+tXNeOZW/W51OiC6rWskgOCsGOJZ3SBr8N/L/Ll7ffURvMjsJaVkmcjZHJo RUsijF15XbWYvsUqhxdUa2G+ancj0DZK/b1jLoLqeb9p5uMgTboizGxlBk+Wcx1ooRb7 MdOG9yJHOlom2AuFi6aFFbuap3onJg7Osh7OKf5Tw/HM7eZPTg3StnN30RouimUMc+1c dHS5pNPS0/pzDmglEurBj6Db3pQHa8VpUeffGjyrcEu1LF9HabfO1zW+ZyLKTI8sSfAK r4+A==
X-Gm-Message-State: APjAAAWiWbL267zeNFgrBcXvErNkzG5g++97pWVAZOCwDChWM6f/SDMN KlajCuVsbwJnI/Oq1mntTvw4ZKK9NkxN41JGbJsvGQ==
X-Google-Smtp-Source: APXvYqzkfF2NhyMiMorVwFKbL2zBfsoWG4C09AmdGDs2qVTsGis9q63v9FMyp5mVxfW6u/zFoS9CNMii3NBSjpByiaI=
X-Received: by 2002:a37:9fce:: with SMTP id i197mr23943514qke.466.1575856079229; Sun, 08 Dec 2019 17:47:59 -0800 (PST)
MIME-Version: 1.0
References: <m1idEJQ-0000KPC@stereo.hq.phicoh.net> <EF1F2FB2-4FA0-4BCC-82B8-948EBE7915A6@fugue.com> <DM6PR11MB413793BCC3AFF44F7B8E101DCF5F0@DM6PR11MB4137.namprd11.prod.outlook.com> <8FD2BAAB-96D1-41F0-97A2-2D16CDAF999E@fugue.com>
In-Reply-To: <8FD2BAAB-96D1-41F0-97A2-2D16CDAF999E@fugue.com>
From: Jen Linkova <furry13@gmail.com>
Date: Mon, 09 Dec 2019 12:47:47 +1100
Message-ID: <CAFU7BAS_Cst0m9z5e_an__ZTtXSTWa9iXwgve4nc5f3adFcyiw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/9vUCKf_O6PNg_qx3A6TjwzDDLOI>
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 01:48:02 -0000

On Sat, Dec 7, 2019 at 3:02 AM Ted Lemon <mellon@fugue.com> wrote:
>> Personally, I would NOT recommend breaking the semantics of a DHCPOFFER and always include an address because you never know how intermediate devices that may be "snooping" this traffic will handle this; for example, the intermediate device might drop what it feels is an invalid packet.
>
> This is definitely not an issue, though, because the network operator is choosing to deploy this.  They can be responsible for ensuring correct behavior if there are any middleboxes intercepting the DHCPv4 traffic and doing stuff with it.   Expecting this to Just Work with no infrastructure changes seems unnecessary.

The question is: how massive those infrastructure changes are and
what's the failure scenarios are expected. We might impede or even
completely prevent the adoption if the entrance barrier is too high.
Also in many cases people operating services (like DHCP) are not the
same people who are looking after the network infrastructure.

I see a big difference between 'incrementally enabling smth on clients
and servers' and 'getting switching and WiFi vendors involved and
upgrade the network infrastructure - which means moths or years of
delay, not mentioning non-obvious failure scenarios, when only some
clients are connected to way-too-smart-boxes'.
If we can make it transparent to the switching infrastructure we
probably should.
--
SY, Jen Linkova aka Furry