IETF Logo Mail Archive

Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023

Michael Richardson <mcr@sandelman.ca> Fri, 29 December 2023 17:02 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B5FC157924 for <dhcwg@ietfa.amsl.com>; Fri, 29 Dec 2023 09:02:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.406
X-Spam-Level:
X-Spam-Status: No, score=-4.406 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 BqIt_QHBjIc3 for <dhcwg@ietfa.amsl.com>; Fri, 29 Dec 2023 09:02:52 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDE31C15107C for <dhcwg@ietf.org>; Fri, 29 Dec 2023 09:02:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 7778F1800E; Fri, 29 Dec 2023 12:02:51 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vtEiyTxpDOC3; Fri, 29 Dec 2023 12:02:50 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 730E91800C; Fri, 29 Dec 2023 12:02:50 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1703869370; bh=x6IkSmw1VWiKYpC+URZPH92xjnyS/gSqvn619r5NTx8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=sX/dH5IZLDY0Ogxir6vPbVg82eY0z0g4k+GBbgi3RT8ViygHauVlf+qf/Z4NwOEdB k3s9TKDJZLpPYBBq38+93nryGAjbMh0F58ymhKp0s6c2smkivmh+52SuaT18rSqpzW ktHhzFD3aVvydIBCp+pgKHOfyyj2HcwCmjwo10udIdG+IeMjHwLF+7WPz38ab/rVP0 USzfPfBWR6W6+RTIjrS9FT9UbWKE8kOQ+KgxUIxf/WU351px52LzdOT1T03jxPJjaa HC9mT6RjoijtNNTHuod54ckFD6uhy/BifDMS2Q3z6RzAxff218yO8L2x6QgN61QzrH hhNTVAlf0KxDQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6EA421BF; Fri, 29 Dec 2023 12:02:50 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Jen Linkova <furry13@gmail.com>, dhcwg@ietf.org, Daryll Swer <contact=40daryllswer.com@dmarc.ietf.org>
In-Reply-To: <CAFU7BATNwBjbY7k_i7ft8nf2b_HhRqV2yyd4LKc=ou1kLmjwXQ@mail.gmail.com>
References: <CACyFTPE0+aV35JgVCL62T3NKL_tFkxuvM=Wfq0xpcw5_Ra-u_A@mail.gmail.com> <15477.1703435979@localhost> <CAFU7BATNwBjbY7k_i7ft8nf2b_HhRqV2yyd4LKc=ou1kLmjwXQ@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 29 Dec 2023 12:02:50 -0500
Message-ID: <22712.1703869370@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/TmahovNFWi79anfySifZIP0O5pM>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Dec 2023 17:02:58 -0000

Jen Linkova <furry13@gmail.com> wrote:
    >> I wrote some text:
    >> https://github.com/wkumari/draft-wkumari-dhc-addr-notification/pull/68
    >>
    >> and I'm sorry to open this can of worms, but I don't think that enterprises
    >> will be happy without this.

    > I have some concerns.
    > 1. The desired result can be achieved by relaying the messages - and
    > it would using the standard DHCP mechanism. What you are proposing
    > requires developing a new mechanism for proxying (and we'd need to
    > either sacrifice security, or let the proxy use a spoofed source
    > address).

I agree: it seems like overkill.

    > For #2.1  I'd expect the enterprise to collect that data from the
    > router (the same way they would need to do it for DHCPv[46] assigned
    > addresses). That information doesn't need to be collected  in real
    > time, so existing monitoring/telemetry mechanisms would do.

I can live with this.

    >> In particular, our desire to enable more
    >> (permissionless) DHCPv6-PD downstream will get the same pushback that has
    >> lead to this document.

    > I'm not sure what you mean about "permissionless' '. As long as the
    > server delegates the prefix, the administrator knows which device that
    > prefix was delegated to.
    > So accountability is there.

I agree that it's not quite a permissionless as NAT44 is; my point is that I
think/hope that enterprises will come to regard enabling anything to do
DHCPv6-PD will become ubiquitous.  That it's way better than hosts doing
NAT44 from an accountability point of view.  That's the tradeoff where the
admin wins.  Maybe for the host-with-VMs/containers relaying the addr-reg
messages is the right answer.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email