IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 09 January 2024 14:12 UTC

Return-Path: <mcr+ietf@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 9BFABC14F6FD for <dhcwg@ietfa.amsl.com>; Tue, 9 Jan 2024 06:12:10 -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=ham 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 skU2ebNxCFRW for <dhcwg@ietfa.amsl.com>; Tue, 9 Jan 2024 06:12:06 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 820C4C14F6A4 for <dhcwg@ietf.org>; Tue, 9 Jan 2024 06:12:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C8F931800D; Tue, 9 Jan 2024 09:12:03 -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 VtbQgjGnIs93; Tue, 9 Jan 2024 09:12:02 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 83DD21800C; Tue, 9 Jan 2024 09:12:02 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1704809522; bh=HcZ1as2BFZeg6XbwpvXgWroTDBnYZIfFabdh8gYEN3g=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=Q//A8ooEHU2EeI/qKM+d6Jfnsy8HRD0WhJOzIz591lnyuZsw96td+xzzPBCtLC4Ef PArcSTdj+Nog88mv4Yfr7JfUpl/k63HNoZrnqMKA1gEQ/GcB0qjqDoT7WM3dHIENA1 jtnRzB7Z0hgdLkbwjITDFyt69mQSx44uK2VMeVYOTuDPYENWGMMRGc6R/n0wGWjsaA KBTFXh5ukSg+3SE6g5D8RbgmO6UjuWpGqUUatQzyw1qblEJAMCtq+w0IHGQfeTm/vC evQogPmMSDJyXv5X64k05IjdZc71hpZ9pBlNc82fGTuYdyZqeeEg+g/Q6MRChtVhox OEpB/NUYzk+Hw==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7B82F14F; Tue, 9 Jan 2024 09:12:02 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Lorenzo Colitti <lorenzo@google.com>
cc: dhcwg@ietf.org, Daryll Swer <contact=40daryllswer.com@dmarc.ietf.org>
In-Reply-To: <CAKD1Yr2TSv7cTVVDDj6sxjVY++PN-iybg3g7N3BM3vFWCU=YMg@mail.gmail.com>
References: <CACyFTPE0+aV35JgVCL62T3NKL_tFkxuvM=Wfq0xpcw5_Ra-u_A@mail.gmail.com> <15477.1703435979@localhost> <CAKD1Yr2TSv7cTVVDDj6sxjVY++PN-iybg3g7N3BM3vFWCU=YMg@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: Tue, 09 Jan 2024 09:12:02 -0500
Message-ID: <30300.1704809522@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/MiUaAg3xvnC98wWIjO3bc2Tw8qo>
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: Tue, 09 Jan 2024 14:12:10 -0000

Lorenzo Colitti <lorenzo@google.com> wrote:
    > Regarding your "enterprises won't be happy without this" comment... why do
    > you say this? One of the goals of this document is to get
    > roughly equivalent forensics and logging abilities to what we have with
    > IA_NA today (assuming cooperating hosts). But AFAICT the hierarchical

Right.  So forensics today will point at the IPv4, where the kubernetes or
VirtualBox installation exists, and which connect via NAT44.
Upgrade to IPv6, and it's a PD delegation.  I agree that it's probably enough
to be equivalent; but is it really what they want?

    > notifications you describe aren't something that exists today with IA_NA.
    > The enterprise either uses a local DHCPv6 server that is authoritative for
    > the local prefix, or it uses a centralized DHCPv6 server to assign all
    > addresses. In the former case, the only information about which addresses
    > are assigned locally is in the logs of the local DHCPv6 server. The
    > mechanism being proposed in this draft has the same properties.

I will withdraw my suggestion that we do something, but I think that we need
to say something about this situation, even if it's "out of scope"

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email