IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 29 December 2023 17:36 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 5E168C14F5F2 for <dhcwg@ietfa.amsl.com>; Fri, 29 Dec 2023 09:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_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 SIiys7jpKPOK for <dhcwg@ietfa.amsl.com>; Fri, 29 Dec 2023 09:36:08 -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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40903C14F5E6 for <dhcwg@ietf.org>; Fri, 29 Dec 2023 09:36:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C87F21800F; Fri, 29 Dec 2023 12:36:01 -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 invQlbeGFWvV; Fri, 29 Dec 2023 12:36:00 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CDB911800C; Fri, 29 Dec 2023 12:36:00 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1703871360; bh=69q/Y+BK2gCOePdjNNfs6WOjtetM5cQ3XbWAZkBwLTw=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=tUGb2362rLzHQZd32JHLgnWE2ZJ2mE8UcON7ZaNdFoTIuEjbZgFXxlSKTF2qaUSYM 4m9y0iFAHeZuOs9jUf8HcdFLZa4Iy4LhC/xe2haTRZrl2o7CixHhTiQbls141fvZjX jegA1ZwbgRdNrEZ9mlGRx7joMRf9V44ZSY0SnVDWPDySEZGm+afjKGtkCgJ+vvgiXo Rgnz7jO2dUNNrRSVC5ukILMs8BikpK71VyAIHa0LTk4M2U7sofPQDdFoVAvnxldkVA GdQ4enHQ0C4Sn1rbQLDxninfkCtfHVbhxR5z5jzvUk0mnvJtT++VHdsZOvZZpm6xsy NDZbU6bLhmNtw==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C47691BF; Fri, 29 Dec 2023 12:36:00 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>
cc: dhcwg@ietf.org
In-Reply-To: <CAPt1N1kHOqvqkBmCVG+=53Fp7htAtNfgCch_VU4i2sRnaSSDQw@mail.gmail.com>
References: <CACyFTPE0+aV35JgVCL62T3NKL_tFkxuvM=Wfq0xpcw5_Ra-u_A@mail.gmail.com> <15477.1703435979@localhost> <CAFU7BATNwBjbY7k_i7ft8nf2b_HhRqV2yyd4LKc=ou1kLmjwXQ@mail.gmail.com> <CAPt1N1=h10kWEQkynMF4qDQBBrMLGOxDOE_tAc4AYnob1jw8qg@mail.gmail.com> <23223.1703869513@localhost> <CAPt1N1kHOqvqkBmCVG+=53Fp7htAtNfgCch_VU4i2sRnaSSDQw@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:36:00 -0500
Message-ID: <30634.1703871360@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/JAWLXFb-iGfOd5yoWQANFe2_O_Y>
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:36:12 -0000

Ted Lemon <mellon@fugue.com> wrote:
    > How would it receive that?  It’s not going to do an information request,
    > currently. The only dhcp behavior currently specified is that it will
    > attempt an IA_PD.

I'm assuming that it arrived on the stub network from an IoT device there.

That it was being used in the stub network for reasons similar to why we want
it on the enterprise network: to know which device is which.

Would you want to relay it, or process it locally?

--
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