Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023
Ted Lemon <mellon@fugue.com> Mon, 04 December 2023 22:45 UTC
Return-Path: <mellon@fugue.com>
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 2C3A0C14F5E9 for <dhcwg@ietfa.amsl.com>; Mon, 4 Dec 2023 14:45:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=fugue-com.20230601.gappssmtp.com
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 Bo-FD4OQh44E for <dhcwg@ietfa.amsl.com>; Mon, 4 Dec 2023 14:45:23 -0800 (PST)
Received: from mail-yw1-x112b.google.com (mail-yw1-x112b.google.com [IPv6:2607:f8b0:4864:20::112b]) (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 C0700C14F5E3 for <dhcwg@ietf.org>; Mon, 4 Dec 2023 14:45:23 -0800 (PST)
Received: by mail-yw1-x112b.google.com with SMTP id 00721157ae682-5d7346442d4so23580227b3.2 for <dhcwg@ietf.org>; Mon, 04 Dec 2023 14:45:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20230601.gappssmtp.com; s=20230601; t=1701729922; x=1702334722; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=R5q4ceNC4Afd3xIKVDMDQm11tfltlTPta2qmzmOwDtk=; b=JivdIe0lwwgsRXunTBJk7ONPQvIJjrlCVxlsa2eppbV7n2ijMDH1yCxo/C/kba5QWl Mh7J5iCRcqCCR9CLRwNO47u85/MznBUqihOMGV6mdtAcMzeXQ9WrlnhMhVMMfiICyiYz 5ZQ5Nr9gF4hLkpUHU7F+xMbLuusZL2MNY5+Y4zoBVL+3DLxyndJm4TvjL3bU+P9hRhr3 IOAOe4gEkQpDxsU4hV3FFqcLHnAUMtL2wlSRHqKDvan7ccu1QyGXsO391SU1X0bMB237 hrgGczi08cgPtJJCnVBxZU9lI1Y/2LxIOjY5fIGYReGoSsST9um6kEAzN7OTXrUsDHMH gBaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701729922; x=1702334722; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=R5q4ceNC4Afd3xIKVDMDQm11tfltlTPta2qmzmOwDtk=; b=tVRQ960o1OSONvqBnkNirxIQKLhZ+l0LV/dVYkUGdJ/QjYuic0G5MqUj2zcZmqtMfX Bmg2ohqKmNHdqgzJ7FSDAzzLnaqARgR6MfglDuL+tPoehB3CXIuMycnkk5OJgY74l/WB lWM3jKDHJu9Tn/P0UqO9PZ5eiubhskB+HEEEJjUs4ALS6JkfOBdFRewZ7tw34tIxHGGZ WTQK7RenQCC8suL2n9DXLt3zt/VCTcGziysWm+bH6XIFqVVrvGv0lU4zSgvIlMocHKcf ukz4rPAuu9IQmKJzvZuMpcpZ15bPfXTTUFogvNHeKqX1KmyCscwQ3pQFZ/3bKNI5NjGv Ephw==
X-Gm-Message-State: AOJu0YzN2wLn8j8mP37cr+1SIFmSAQPUKy1d2d7frO0T26LqZm7/ACCQ ESJHQqTIztQlf+hOGVhIk2NhB4SBjsJsrTnMBQ9dGg5nBQxfMjHbdVQ=
X-Google-Smtp-Source: AGHT+IEPYsbgZlSUU9zvtkdGpt3LS9pDRcKZUQtrzOmAy6DSDX7nr2JV+FnYXP1vdL488QpmbBdiFrG/4BPCMrnMEkg=
X-Received: by 2002:a81:9848:0:b0:5d3:d6c3:dce with SMTP id p69-20020a819848000000b005d3d6c30dcemr7569936ywg.12.1701729922617; Mon, 04 Dec 2023 14:45:22 -0800 (PST)
MIME-Version: 1.0
References: <CAJgLMKuUkm1bxhT379QxrdOLzbA0zuGPQY4UbvzOYJD-ykWBwg@mail.gmail.com> <CAFU7BAQzwW4yFXH6vF2stZT5G7OmyZj248zGxeZbJ06JDJ_ieg@mail.gmail.com>
In-Reply-To: <CAFU7BAQzwW4yFXH6vF2stZT5G7OmyZj248zGxeZbJ06JDJ_ieg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 04 Dec 2023 17:44:46 -0500
Message-ID: <CAPt1N1n1LxYRO39GEtoLa_z99Ti+ZPgHVtzZXrr1kba230Gg6w@mail.gmail.com>
To: Jen Linkova <furry13@gmail.com>
Cc: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008aa6fa060bb6df6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/H8zBTp36OSedOZv-VhjgI_PMjFw>
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: Mon, 04 Dec 2023 22:45:25 -0000
My only worry about this is that the draft (correctly) acknowledges that there may be more than one DHCP server and that such servers may have different answers to the registration question, but doesn't talk about the specifics of when the client decides that things have or have not changed. The only message for which RFC8415 acknowledges that there can be multiple replies is a Solicit, but in fact an Information-Request could just as easily return multiple replies. I don't know if the WG is thinking about this, but this seems like a fairly serious gap. So I think that in fact what you're proposing here isn't quite right. Rather, the client in this case should wait as it does for Advertises. When it gets a reply that allows for registration, it registers with that server. If it gets no reply that allows for registration, then it stops registering. This behavior should be specified in 8415-bis, not in this document. Additionally, the client should pick a server, and include the server's DUID in a server identifier option as specified in section 14 of 8415. So this is the opposite of what's currently specified. The reason for this is that if you have some servers that support address registration, and some that do not, and you send an address registration message without specifying a server identifier, it's going to be processed by all servers, so you'll get errors back from servers that don't support it and possibly multiple acknowledgments from multiple servers (maybe that's okay though?). Anyway, I think this needs a bit more thinking. On Mon, Dec 4, 2023 at 5:24 PM Jen Linkova <furry13@gmail.com> wrote: > The WGLC has been uncomfortably quiet, so we've just submitted -07 > (https://www.ietf.org/archive/id/draft-ietf-dhc-addr-notification-07.html) > to address an oscillation problem: if some servers support the > registration and some don't, the client might turn the registration on > and off, depending on the order of arriving Replies. > While it's not the end of the world, I think it's rather undesirable. > The new text says that the client always register if at least one > server returns the OPTION_ADDR_REG_ENABLE option, and say the client > MUST stop > registering if that server stops returning the option. > Basically, as long as at least one server supports the registration, > the client will be sending messages, but it's still possible for the > administrator to turn the registration off. > > Comments? > > On Mon, Nov 27, 2023 at 9:32 PM Timothy Winters <tim@qacafe.com> wrote: > > > > Hi: > > > > The authors believe this document is ready for WGLC. Therefore, the > chairs > > are initiating a WGLC on this document. > > > > Please review this document and provide your comments and whether you > > support this document moving forward or not by the end of day on Monday, > > December 11th, 2023. > > > > Please see > > > https://datatracker.ietf.org/doc/html/draft-ietf-dhc-addr-notification-06. > > > > This is a Standards Track document. > > > > Thank you! > > ~ Tim and Bernie > > _______________________________________________ > > dhcwg mailing list > > dhcwg@ietf.org > > https://www.ietf.org/mailman/listinfo/dhcwg > > > > -- > Cheers, Jen Linkova > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg >
- [dhcwg] WGLC for draft-ietf-dhc-addr-notification… Timothy Winters
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ivan A Pena
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Daryll Swer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Daryll Swer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Daryll Swer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Daryll Swer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson