Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023
Bernie Volz <bevolz@gmail.com> Tue, 05 December 2023 01:00 UTC
Return-Path: <bevolz@gmail.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 571D2C14F603 for <dhcwg@ietfa.amsl.com>; Mon, 4 Dec 2023 17:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level:
X-Spam-Status: No, score=-6.212 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_HI=-5, 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=gmail.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 rhII_Om3e6hN for <dhcwg@ietfa.amsl.com>; Mon, 4 Dec 2023 17:00:09 -0800 (PST)
Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (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 90D30C14F5FB for <dhcwg@ietf.org>; Mon, 4 Dec 2023 17:00:09 -0800 (PST)
Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-67adea83ea6so328186d6.0 for <dhcwg@ietf.org>; Mon, 04 Dec 2023 17:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701738008; x=1702342808; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=e6gtKhZWNX72EG7otCr48rMqBMs6xWFIX0v02KVVyGc=; b=RKjeYjkdnQpoe3lxHvVU9z03TA9JX7rAZZSyYJHHAexyqc/ltTTOQ30eTHFkf6vUS0 VV2EcPHOZsT8kkbJ/HaNoNDpNoX5lHNKAQ5oroH7MHD9sZMZ3kSsclOYFEKMEwLgMoJ8 N3rg6Y8vK5+e/rOZtKO6kfF8ZyEO9Sogcz/DNCr/9rrp+6kdr+bIcyAaQwYQRFpFITwt xce+eDP6KREDGR9sZlc4Jm7q/KAohqVBZNdqq1NWq2qqcxCQwnZsoZ+RXWmS55IKrWsJ zbOTaDuEYMR2IsXKGiMYebdDFCU6Wzb5zp+3HNnbELI55cPnjqLb3JUuAKmY1WDBdhLf lhfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701738008; x=1702342808; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=e6gtKhZWNX72EG7otCr48rMqBMs6xWFIX0v02KVVyGc=; b=kf2mogYY/J/+gJWUQ+0rKppfYJqZmC8zG1OhkUqevLDvP9ewPj9SteeX08jK6y0Zha KBvNjFMAu52gyEjRb2b8iQ/9Ql9JN9i7a34pcKj/U1FmwKvjkPeGNcc5/vvxoh3cSAPP vykGaswSKCXXWSpDJulLy5ArQM8SRXzkZoU+EeWXJnZsXiq4fGBjbYLOEQo4yVnzodTL Tx9OiCvFezpUmdv52vyS0sWjQazJNhY9CEy1Q2UN3w/j/C9YnG/F9wlo3dFMjqypkX1z ycRfgetfDbGJ7LOFdq0dO6PysbyP/iQJyDjPmNf5SlWBZ0Mx1UWu+Un08mHlsKFArGEv NVtQ==
X-Gm-Message-State: AOJu0YzB/FxnzkZbBZdF/GK20SqDOd8XCUEOCa8kIVHMOYUjpy4Pv1ek RNLKer6Y7sZD54RXUCnFwJj6sn1l6Q==
X-Google-Smtp-Source: AGHT+IEmq0x2/x8EyjhFczVBlEjQWE92ewkY90fm3vo4xwTAijvJ+R70RigJx2yBhQATixC4bMRPUQ==
X-Received: by 2002:a0c:e784:0:b0:67a:cf28:39c3 with SMTP id x4-20020a0ce784000000b0067acf2839c3mr491447qvn.37.1701738008375; Mon, 04 Dec 2023 17:00:08 -0800 (PST)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id m15-20020a0562141bcf00b0067aa351b0a3sm3271363qvc.65.2023.12.04.17.00.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Dec 2023 17:00:07 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-8486A1C1-12C8-45C4-94A5-70CD0405A8A6"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 04 Dec 2023 19:59:57 -0500
Message-Id: <7CF975FC-5450-4FAD-8D7B-1CF40A796728@gmail.com>
References: <CAPt1N1n1LxYRO39GEtoLa_z99Ti+ZPgHVtzZXrr1kba230Gg6w@mail.gmail.com>
Cc: Jen Linkova <furry13@gmail.com>, dhcwg <dhcwg@ietf.org>
In-Reply-To: <CAPt1N1n1LxYRO39GEtoLa_z99Ti+ZPgHVtzZXrr1kba230Gg6w@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: iPad Mail (21B101)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/hmMzpJPo1GapAhbYAyIGpXFU37E>
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, 05 Dec 2023 01:00:13 -0000
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,
On Dec 4, 2023, at 5:45 PM, Ted Lemon <mellon@fugue.com> wrote:
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._______________________________________________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" rel="noreferrer nofollow" target="_blank">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" rel="noreferrer nofollow" target="_blank">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" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/dhcwg
--
Cheers, Jen Linkova
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/dhcwg
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… Ole Trøan
- 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… 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