IETF Logo Mail Archive

Re: [dhcwg] I-D Action: draft-ietf-dhc-addr-notification-06.txt

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 November 2023 09:30 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 ADEB9C16F3E7 for <dhcwg@ietfa.amsl.com>; Wed, 15 Nov 2023 01:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 1DwpBb6rzpHh for <dhcwg@ietfa.amsl.com>; Wed, 15 Nov 2023 01:30:12 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 32D95C13AE23 for <dhcwg@ietf.org>; Wed, 15 Nov 2023 01:30:11 -0800 (PST)
Received: from dyas.sandelman.ca (dynamic-046-114-177-123.46.114.pool.telefonica.de [46.114.177.123]) by relay.sandelman.ca (Postfix) with ESMTPS id 7408B20B4B; Wed, 15 Nov 2023 09:30:10 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 8F990A1BC0; Wed, 15 Nov 2023 10:29:07 +0100 (CET)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 8CCC8A1BB0; Wed, 15 Nov 2023 10:29:07 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Jen Linkova <furry13@gmail.com>, dhcwg@ietf.org
In-reply-to: <CAFU7BARBbhxJtNtbTOTcCHBrpSdZSSjD=yX2-rn7h2eTrsX8XQ@mail.gmail.com>
References: <169972061526.44003.9261571368630357252@ietfa.amsl.com> <CAFU7BARBbhxJtNtbTOTcCHBrpSdZSSjD=yX2-rn7h2eTrsX8XQ@mail.gmail.com>
Comments: In-reply-to Jen Linkova <furry13@gmail.com> message dated "Sat, 11 Nov 2023 17:42:38 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 15 Nov 2023 10:29:07 +0100
Message-ID: <4055123.1700040547@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/xytnoGJ8AM4hyRkhIytXTxZQUbc>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-addr-notification-06.txt
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: Wed, 15 Nov 2023 09:30:16 -0000

Jen Linkova <furry13@gmail.com> wrote:
    > - "Signalling Address Registration Support" section is rewritten to
    > clarify that if the servers answers are inconsistent, the mechanism is
    > unreliable (as the client can pick up the first reply).

What is the impact of rogue DHCP messages on the network?
(Yes, DHCPguard, but even if it's enabled on the core switches, there might
be unmanaged switches closer to the edges... like on people's desks)

I guess I'd rather the client do address registration if it's seen at least
one server with it enabled.

But, I can live with your text as is.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email