Re: [v6ops] Implementation Status of PREF64

Lorenzo Colitti <lorenzo@google.com> Mon, 11 October 2021 06:12 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 5F43D3A0938 for <v6ops@ietfa.amsl.com>; Sun, 10 Oct 2021 23:12:58 -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=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 0-gAKgvXqLTy for <v6ops@ietfa.amsl.com>; Sun, 10 Oct 2021 23:12:53 -0700 (PDT)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 4499B3A0931 for <v6ops@ietf.org>; Sun, 10 Oct 2021 23:12:53 -0700 (PDT)
Received: by mail-wr1-x42d.google.com with SMTP id i12so39683258wrb.7 for <v6ops@ietf.org>; Sun, 10 Oct 2021 23:12:53 -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=fwlO96f0m/E1lMk9h1g/hhwlF6r0bKJowVrNxGnbJx0=; b=NB4X3PrQOEbQTxdVKdJ7qvvMr0WYaqjGyFcC5vVEtEi4FjH8udqnSVqAb8VIJjIEAU MLBQdEDpAMx+JokGYNwBL6ieDgGcsQ4CewLcWEmJIhNL0AqtZyNwTOnvRi1C0Db1xe6A No2rNorycQ4R6URtdVZFCNX4vScELYVXLdAXQTTh6GPINdszWQw2yZVggdMnj0+R34Td T8574ZYniipUVHby5OPzPYkkoLb3dte5QmoecfsT+Ewn+cfFWZAkzDg+9XAjQ7eL1BxK 0A3/mg7cobwahC9eQwOne8q9TNaV5rREDSbB0QrC+HFkvWri+UNxTg1+LOfUaXMhnqu7 wvFg==
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=fwlO96f0m/E1lMk9h1g/hhwlF6r0bKJowVrNxGnbJx0=; b=gyovOueNQ8XrxpbIM5QJ0kXe1z3t6vRGHWaaxuu3JwRpf48DB+wT0Drk+CfKz/wemu q2vz2ce7u+hDxFjnNNvJhGFkbODgUCmfQP/2yu/lxjvSWxViXyIbRY+AMtYFX1KKHgDg A5IPvKhOvqWDMHZnzGVvZKHT1CvnMjBZ/sxXG7W4+gbI/bVpEOduFc3H3pntB6v0CaqY KWgk727EkQBYISn5pPA27MmD8eUIF4Ry6qQMEUrSargkyOEg6gSV9DEE4GBd4Ha/8vHz wdWHWb6FVPGtQxBaa7AALBCo7mxVUDu/l0LHbL9w3osDPI2oLAJuGWGYjw1IHMpQPcSo 9LNg==
X-Gm-Message-State: AOAM533VUjb4liHHVhHJAL/3ngKK/BfMEUm6HT6x98GsOVdq+bJpjpGg pFWx2AuZguMOWWXJbXmFds6TL+ca+NKgY/3GvWjSFw0w716A5g==
X-Google-Smtp-Source: ABdhPJwBi+lDBFEY2b29to+RqRlDw/asqoY/lgyAA43zBQLn76Wa4A6V+90EDKJxoPZy/T3HEFUw2Kx4X6Mixxxw13I=
X-Received: by 2002:adf:e584:: with SMTP id l4mr12722653wrm.173.1633932771053; Sun, 10 Oct 2021 23:12:51 -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> <CAKD1Yr34jv_N0jGKdg=sG76oGU7PdRjYFC_-w9Uvzs=7oGm38w@mail.gmail.com> <E6316781-AC7D-438F-B216-75B1DF9217DC@delong.com>
In-Reply-To: <E6316781-AC7D-438F-B216-75B1DF9217DC@delong.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 11 Oct 2021 15:12:38 +0900
Message-ID: <CAKD1Yr10OKMJ1y8bs5xpt6jS8ZWsqs66oFCXmp-QLySS5Yn4hg@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="0000000000006875b505ce0d9efd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OUXXDhm82Cvni__uxelPGqa4e2s>
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 06:12:59 -0000

On Mon, Oct 11, 2021 at 1:36 PM Owen DeLong <owen=
40delong.com@dmarc.ietf.org> wrote:

> 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.
>
> At least it provides a possible way forward for networks that don’t want
> to assign addresses outside of IA_NA or IA_PD to provide addressing to
> android devices.
>
> Surely a single IA_NA + a routed IA_PD would meet your requirements, right?
>

IA_PD, even by itself without IA_NA, has none of the concerns in this
thread. RFC 7934 explicitly recommends it, actually. Not sure if enterprise
network operators can or would want to deploy IA_PD though. Is that
something that we can nudge the industry towards?

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.
>
> I don’t think that’s really necessary. I think there are already adequate
> documents about single-address is less than ideal in the existing RFCs/BCPs.
>

The existing BCPs also say that running an IA_NA-only network is not
recommended, but that doesn't prevent folks from saying it's necessary. I
think we'd want to make a stronger statement than that.