Re: [v6ops] New Version Notification for draft-collink-v6ops-ent64pd-01.txt

Nick Buraglio <buraglio@es.net> Tue, 20 December 2022 18:02 UTC

Return-Path: <buraglio@es.net>
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 E7813C14F739 for <v6ops@ietfa.amsl.com>; Tue, 20 Dec 2022 10:02:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=es.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MYyE6lO9A-iq for <v6ops@ietfa.amsl.com>; Tue, 20 Dec 2022 10:02:08 -0800 (PST)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E9D1C14F72A for <v6ops@ietf.org>; Tue, 20 Dec 2022 10:02:08 -0800 (PST)
Received: by mail-ed1-x531.google.com with SMTP id e13so18610373edj.7 for <v6ops@ietf.org>; Tue, 20 Dec 2022 10:02:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=es.net; s=esnet-google; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8IUEB8Qk1aba33yh39NXfPtheD10fs6FXBeSkMtvxUQ=; b=c6ULnBW4GtVGa9XcX2nvvoK1JESfLRMCEcX1NLwBMhOWE25Mp5t5qVy+0tRNSsVrZV VuPXgFYynofq+wGInN1fH7Rvh/qijILsydqPyqfHo1Te5VESxzzIZK26HKqEPKPHfIAb q2+s9s2XZkRgORRylLZw4TUuLilb4TgtuNi5g33tC1TBubZD5WBuX++4uB7Vk4buLk6Q KCIqjnmi4HHWlQ+b3WDCxsduzqXsWqWvdLivIb1MQwHMQdKpDYlEPJjYw3rA4b0qtYmL 5sWVPWwk4qnca/iXgc68Hbwbk9lGfJRBJH5HnCYORWqxAiy+NxH9iknaUa4Fhobka030 K8Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8IUEB8Qk1aba33yh39NXfPtheD10fs6FXBeSkMtvxUQ=; b=Zbs3HISP3z3wJUQwXTXpLYYhHTKMYPvMlzPyvyMqqg6hrG9pp0DuG7qt9YXNUAoNsu H8oWkMwmE86LDMNnJkBOkrjoa5tASARgpjElvH8+xUTQ55eQVWezGbGVORDGK2UFKUJ5 SEYjeswZl8YASRXOcUzGZGKKOKGcVVUqe8bmgJwbvJOIM9JrP9O5bO7gaS9LGk8ucWKS nUkpW25mrRGTCNFXKywW9CqM5rp7Cxislm6xSM+q8IQEBvQFHUX6Z7YaX4QoOBC58NGI bCkA5yETJ4BeDf2MVIffdkQZ5bBxw6anDpaDeSk16OxzNhSj4UnK4s1BlfbE1Rp0cCqj BJWQ==
X-Gm-Message-State: ANoB5pkoqhwXSAp+q9Kvs3RRJVtrrahJB3HRt89smugVsJ9SDt7IKe2r c9+jMjMURpcmvSiBkekB8kfI/XixXaJx+Qeu5ySB30w+cPh9XjEg8aJBcYjoylKej6Kh6crYXnL DtBCfC7EeIYMUMyq5ZtRmML1UQdnOpR9n45kzfqJ6Iw1TXwpcisXfwEYv6P9TJiOB753Bv7IM68 Y=
X-Google-Smtp-Source: AA0mqf6Q3zg+SQ5oKhtI8etb6/bdA+IwhxOYKKbX2FLp5HUcXs+wd2vSZ2eKAq6Quo0KLUMfjbAmKxJshQyQI7EQz40=
X-Received: by 2002:a05:6402:3210:b0:46c:6f53:6176 with SMTP id g16-20020a056402321000b0046c6f536176mr22589973eda.190.1671559326491; Tue, 20 Dec 2022 10:02:06 -0800 (PST)
MIME-Version: 1.0
References: <167107554671.48477.568330207202509840@ietfa.amsl.com> <CAFU7BATp=gEB3S8AzhCYDMN3fzLQrYY9pzcWJ=LQnrjC9bRKEA@mail.gmail.com> <a2b83708c99344b2afb5e65c899b2f76@huawei.com> <63C4488F-AF94-41EB-A892-EFAB788CF0A3@gmail.com>
In-Reply-To: <63C4488F-AF94-41EB-A892-EFAB788CF0A3@gmail.com>
Reply-To: buraglio@es.net
From: Nick Buraglio <buraglio@es.net>
Date: Tue, 20 Dec 2022 12:01:54 -0600
Message-ID: <CAM5+tA9_-oppO3n-smXW2JEc_Q+BazUwL8iWK7QdNE9MmC56pw@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, V6 Ops List <v6ops@ietf.org>, "xiaom@google.com" <xiaom@google.com>, "draft-collink-v6ops-ent64pd@ietf.org" <draft-collink-v6ops-ent64pd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e0d87a05f0463b9a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/MkYf3iiKb7DcsEfwHWRrJ2eGiZQ>
Subject: Re: [v6ops] New Version Notification for draft-collink-v6ops-ent64pd-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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, 20 Dec 2022 18:02:12 -0000

----
nb


On Sun, Dec 18, 2022 at 10:18 PM Fred Baker <fredbaker.ietf@gmail.com>
wrote:

>
>
> > On Dec 15, 2022, at 6:23 AM, Vasilenko Eduard <vasilenko.eduard=
> 40huawei.com@dmarc.ietf.org> wrote:
> >
> > 1.    What is the point to keep SLAAC if DHCP infrastructure is
> mandatory?
>
> What I might suggest is to make SLAAC normal (as s the current case, e.g.,
> retaining backward compatibility) and provide a way to tell hosts that they
> should request a prefix via DHCP-PD.


Signalling via SLAAC piqued my interest, mostly because that seems like an
achievable and easily consumable way to quickly further operational
adoption. I am personally a fan of keeping with the /64 model, and I do
agree that it dilutes some privacy concerns, but realistically I don't see
much of a difference between a host using a /64 and a group of hosts using
a /64, systems can be enumerated in both scenarios - perhaps I am being
obtuse.


nb

>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>