Re: [v6ops] Implementation Status of PREF64

Lorenzo Colitti <lorenzo@google.com> Mon, 11 October 2021 03:35 UTC

Return-Path: <lorenzo@google.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 823FA3A0D0B for <v6ops@ietfa.amsl.com>; Sun, 10 Oct 2021 20:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.097
X-Spam-Level:
X-Spam-Status: No, score=-18.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, 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=unavailable 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 gI_3J1gY9HvP for <v6ops@ietfa.amsl.com>; Sun, 10 Oct 2021 20:35:16 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 7A6163A0D09 for <v6ops@ietf.org>; Sun, 10 Oct 2021 20:35:16 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id t2so51367221wrb.8 for <v6ops@ietf.org>; Sun, 10 Oct 2021 20:35:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/UN2ja1c3G1eu6NOAG8Pi892Bqctdc/cmhAqn8VThmA=; b=YBSVVbKpkE6bYq6fQre5uij46ekS0glvxYu/aPUTtrqm2ZHe8SCO7jkvqbcTS0R3do 5LRgWaWlG2WaSeS9e0g26BaZJZciAPgsmjN5+qXhfssTQyc1z1ybr4Z3EuH5MOnBG0Pq dxaoQVVhsSfVb0kE+0LVTFMw/eUKgPnfCBxvYOpSBm6Cdh0fId4aQYzlqSHsZPtBbTbh p/PfTWeiTI31Z3lUCddVHFsuGtR7V9Sw3f9Bbkkm3vth9YUFbXl0pItso7eQw/YApgw/ VlkugqIcdrOse4ewvKU0N07E7+8P2HfdftFvGzshXRFQyQ7TeuA4nKBCBFEbnhAGEzK5 RQ6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/UN2ja1c3G1eu6NOAG8Pi892Bqctdc/cmhAqn8VThmA=; b=GAXBxKNBASLvQSDid0czWeS53F761ZX9os1mri59T0MYDtSPPbc67YsIEIkRZLbrp0 iFJ93f+gx7OxP9TJdE8UjPQSO30ZngJFCHunon0jLTO2NXh9/g/ltmtnxzK1Nk/qeUqA 6wgKVYzBsgVk7yYqsGQpO7P5BAhGMpXXLsb/OP6qYthACmHqIySO2qVgBCaCwWJgsp1n q1+jMEdb7CTIDR5p82WSfUo3IyVPwf7cGhmVfoDQa3Mk9r7RbPmmKvGKiSmdEbm6yTxL gkj1vbtLlCjYTPPNJruUFM8Adwz2kydPRuBO1DgIbODc/IQhyH/WG7YvmX9XNNT/L1zM 87OA==
X-Gm-Message-State: AOAM532Qm/K3tv6lcwHJCASBuQez6yIr5uNDKM/nEXmUImZGfbgxJPys EmsG7CEiqrUJqnfK5jonrp/bSUzzhFmH+VbTWeWnVQ==
X-Google-Smtp-Source: ABdhPJzNKj8yQ42MGnOhxmK/1gEkmx/xh1OyaUeEn83d2wKPi90omrFSsQTbB9dwDkbINI0FB+tO7B6G0PwRRGACj4w=
X-Received: by 2002:adf:e584:: with SMTP id l4mr12164881wrm.173.1633923312647; Sun, 10 Oct 2021 20:35:12 -0700 (PDT)
MIME-Version: 1.0
References: <DDA36020-90CC-471B-83AD-3D98950F1164@delong.com> <CAKD1Yr0T-7t-UHbsJBMLpTjKhPAV5uUQkux6oby89TVUue7PyA@mail.gmail.com> <CO1PR11MB4881D400EA4681F1505040D2D8AA9@CO1PR11MB4881.namprd11.prod.outlook.com> <CAKD1Yr3TmqFxjKuZ57wS7VuPOf6rJvOwnvnQdFrRLQ=DkZ+CCw@mail.gmail.com> <CO1PR11MB4881F411A4D5BEA7A8479726D8AA9@CO1PR11MB4881.namprd11.prod.outlook.com> <D8AEA194-293B-43E4-BCAE-33CD81FB7D8C@delong.com> <CAKD1Yr2Tug-PFV7wAh0s6-gw8W3LcLG7wC1fD7Lu_hMZQYKdtw@mail.gmail.com> <08D2885E-B824-48E8-9703-DCA98771FA37@delong.com> <CAKD1Yr2EVsY3tYUf56R0Q1+KVrowtqh-HgwXj5vxzy4wd-vkTg@mail.gmail.com> <1A6ED87B-666E-439C-852F-2E5C904C0515@delong.com> <CAKD1Yr23fY2DJDvB-9eVFRsxnBnZQ0kZuZfYUfRUHYW=_D=enA@mail.gmail.com> <CAN-Dau1z0q0R61x7iY+Wg_cFRU0jmqr+fR0y=bSXxj+K-n722w@mail.gmail.com> <CAKD1Yr1T_mXfxJGHOrBfqZfexm6GTrUqnFi57710pTroKQK6uQ@mail.gmail.com> <702CB018-1A02-4B32-B9AA-7C7B31521F12@delong.com> <CAKD1Yr0jZR8Efzr_Y6FeiBvHYS8ATmDupx2ABTXXy-rSA_QjmA@mail.gmail.com> <1adb70a8-db0a-4ea6-f721-c1035343cda3@foobar.org> <DM6PR02MB69249D4F0A8003E77EC9F153C3B19@DM6PR02MB6924.namprd02.prod.outlook.com> <E1FED93B-674C-46DD-8C39-F6C30475C48A@delong.com>
In-Reply-To: <E1FED93B-674C-46DD-8C39-F6C30475C48A@delong.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 11 Oct 2021 12:35:00 +0900
Message-ID: <CAKD1Yr34jv_N0jGKdg=sG76oGU7PdRjYFC_-w9Uvzs=7oGm38w@mail.gmail.com>
To: Owen DeLong <owen=40delong.com@dmarc.ietf.org>
Cc: "STARK, BARBARA H" <bs7652@att.com>, Nick Hilliard <nick@foobar.org>, v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a46b6905ce0b6a4e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/l301YcIyqIaTvH3MLYsbOOeZZTo>
Subject: Re: [v6ops] Implementation Status of PREF64
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, 11 Oct 2021 03:35:22 -0000

On Mon, Oct 11, 2021 at 9:16 AM Owen DeLong <owen=
40delong.com@dmarc.ietf.org> wrote:

> Agreed, but the device manufacturer, OTOH, is somewhat in control of what
> their device will or won’t do and if Lorenzo/Google want to impose that
> limitation on their implementation, the IETF shouldn’t be able to stop them
> any more than it should be able to dictate that they must do so.
>
> Guess what, Lorenzo… That’s the current situation. The IETF is mute on how
> many devices must be provided via IA_NA or whether or not you can implement
> some minimum acceptable number or disable the IPv6 stack as a result.
>
> Therefore, you are not prohibited from doing so.
>

Ok, but would that solve the issue in this thread?

Suppose an OS developer ships a DHCPv6 implementation that requires N
addresses and does not enable the IPv6 stack unless it receives all of
them. How does that do anything to address statements such as, "my network,
my rules" that have been made on this thread? Any operator that wants to
assign only one address per device still cannot use such hosts on their
network, and can still criticise the implementation for not doing what they
want.

What I think David was suggesting is: if we reach consensus on some
reasonable value of N, then the IETF could write a BCP to that effect. That
would help to some extent, because if an operator complains that the
implementation does not work on a network that has N=1, the OS developer
could point to the BCP as justification for why.