Re: [v6ops] Implementation Status of PREF64

Philip Homburg <pch-v6ops-10@u-1.phicoh.com> Tue, 12 October 2021 09:33 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 672703A11F0 for <v6ops@ietfa.amsl.com>; Tue, 12 Oct 2021 02:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
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 7tpi7ktnZo0B for <v6ops@ietfa.amsl.com>; Tue, 12 Oct 2021 02:33:21 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6.hq.phicoh.net [IPv6:2001:981:201c:1:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A6143A0CC5 for <v6ops@ietf.org>; Tue, 12 Oct 2021 02:33:20 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #158) id m1maE9u-0000HxC; Tue, 12 Oct 2021 11:33:18 +0200
Message-Id: <m1maE9u-0000HxC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-10@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <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> <CAKD1Yr10OKMJ1y8bs5xpt6jS8ZWsqs66oFCXmp-QLySS5Yn4hg@mail.gmail.com> <5DF8D1AE-4B54-429F-962A-488F2AA1F895@delong.com> <CAPt1N1ma45GKqXcvjHUGCYFKVbEGp3OuT013pZhrnOkFFLMiQA@mail.gmail.com> <CAKD1Yr2Pe+=tNkA7Ou9KeMkgFhcdSb8WxgVn1w9MauusMEhRcw@mail.gmail.com> <CO1PR11MB4881076DFF8A145C8CD818B8D8B69@CO1PR11MB4881.namprd11.prod.outlook.com> <YWVLM4jsgVtKsf0B@Space.Net>
In-reply-to: Your message of "Tue, 12 Oct 2021 10:45:39 +0200 ." <YWVLM4jsgVtKsf0B@Space.Net>
Date: Tue, 12 Oct 2021 11:33:17 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/DmQRh8lJ1GYS8i4gtfqstpErSqQ>
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: Tue, 12 Oct 2021 09:33:24 -0000

In your letter dated Tue, 12 Oct 2021 10:45:39 +0200 you wrote:
>Now, "something which will aggregate to a /64 in total, for an arbitrary
>number of devices" - like, a /96, given 4 billion addresses each to up to
>4 billion devices - would definitely be something nice to have.
>
>But I assume that this is not going to work, as I hear that this is 
>not (only) for "things happening inside the device" but also "tethering",
>which would require a /64 then.  Which, incidentially, is a use case
>not desired in Enterprise context.

I don't see why tethering would require a /64. If the downstream devices
supports DHCPv6 IA_NA then it would work just fine.

Actually, for tethering with DHCPv6 IA_NA, you don't need PD. You can just
relay the request from the downstream device. (Whether actually relay,
or generate a new request). Obviously PD would help if ND state in the
first hop router is an issue. 

It is only when the downstream device insists on SLAAC that you would need
a /64.