Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by September 13, 2023
Bernie Volz <bevolz@gmail.com> Thu, 14 September 2023 19:16 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 16674C14E513 for <dhcwg@ietfa.amsl.com>; Thu, 14 Sep 2023 12:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.215
X-Spam-Level:
X-Spam-Status: No, score=-1.215 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 yL3L8tYXjMEs for <dhcwg@ietfa.amsl.com>; Thu, 14 Sep 2023 12:16:40 -0700 (PDT)
Received: from mail-oa1-x2b.google.com (mail-oa1-x2b.google.com [IPv6:2001:4860:4864:20::2b]) (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 CC836C14F726 for <dhcwg@ietf.org>; Thu, 14 Sep 2023 12:16:40 -0700 (PDT)
Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-1d5c54160a8so698420fac.0 for <dhcwg@ietf.org>; Thu, 14 Sep 2023 12:16:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694718999; x=1695323799; 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=mGXJskLMZ/DAOScDJBFE376OQNA1RrViUEwIw2+IkT4=; b=FhbqzVUvSk+NeSYS9sN4OP8vGlR6LH4brJRQQfG9TdQY3KDkZvu2G9mQl6kVjgdrXC XOP+Tl5hPCpaqY9ONKsNspPgAolmDgPRtKENlsgOyR92Gt9sgI1INXteIwmL+DxJVlp9 nquUl3Ob9zIbwkdv5mEUor0U4C8m9TNQphKRpkztEgw4NzOBMSx120FZE18xSe+fB3wz 7hzK7rQSHKwn4grI1ew/fPnGRFweJKE706EU8LghvgNfNkLOpJb/a5lt0XHOoZRw4bER g8iZdyyDowQkcu5h67BIRXXsJlyEMejyL9F3DWNyEH8MZ+M720U0WYY4A2LNGwkSxy1q SzWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694718999; x=1695323799; 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=mGXJskLMZ/DAOScDJBFE376OQNA1RrViUEwIw2+IkT4=; b=Pey+hxGyZejIdobQehMzRATd3N8NWC2AF9v0gMH7lYXfrQNWmHwaPUCetd42aWPND0 fo9DruA2djWm5r9uIGQLSL3nKELW5huBVp/Z6QyKZa1RXmupvmdloy/paEFGiAfmK8Jp sHFkkL4n1AIb5O0EBYavjjRX4P5hwmTp24tIcxIM2KH/ZGvalAj3RkQpnqO/TWE2AaSY Mpsm6docVrAAtrB8RZQaVvd49aY0fIrH3gmbmw3NCBFjQEB7lQsikCzhaoLMZQDNOyZ3 GOyaxhU4RodR2jn99eD5xNaEjq+yY512bv9WFqemglgvt7MK9PirEe+4V4eyAwl67lO8 JRwA==
X-Gm-Message-State: AOJu0YyrkEuCUgaXCCgIQVipQncxLx0nOKCNy4xLx6JYg8U3+WdZ4tEn ckzfszpaWvItJ/zwZ1/SHKsK9H+jjw==
X-Google-Smtp-Source: AGHT+IE7FxgQ1GRhzlZDCg0sOWnBl6u1R4YTMFaa5cxGJtDEdoeYvPssJVpHbJtXbCpXpWw8/XWvJA==
X-Received: by 2002:a05:6870:ea90:b0:1bb:51e4:9483 with SMTP id s16-20020a056870ea9000b001bb51e49483mr7100143oap.45.1694718999422; Thu, 14 Sep 2023 12:16:39 -0700 (PDT)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id g27-20020a05620a13db00b0076cdc3b5beasm675217qkl.86.2023.09.14.12.16.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 14 Sep 2023 12:16:38 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-AD677C43-55BB-4641-A0A9-9E1BB27FED8E"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 14 Sep 2023 15:16:27 -0400
Message-Id: <D55BE526-8E02-416B-9EE0-DF86994E470B@gmail.com>
References: <825A32E7-3AFA-409F-B870-002D092BA3F9@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, dhcwg <dhcwg@ietf.org>
In-Reply-To: <825A32E7-3AFA-409F-B870-002D092BA3F9@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: iPad Mail (20G81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/U9wGdNBP9HaD5907siYN11Dh97s>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by September 13, 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: Thu, 14 Sep 2023 19:16:45 -0000
On Sep 14, 2023, at 2:32 PM, Bernie Volz <bevolz@gmail.com> wrote:
Hi:(Just catching up and responding to this as was asked specifically…there could have been more I haven’t yet read.)8415bis only prohibits IA options in Information-Request16.12. Information-request Message Clients MUST discard any received Information-request messages. Servers MUST discard any received Information-request message that meets any of the following conditions: * the message includes a Server Identifier option (see Section 21.3), and the DUID in the option does not match the server's DUID. * the message includes an IA option.I wonder however if having an Address Registration option specifically would be better (the Information-Request and new registration request could use this instead of IA_Addr option). This might avoid an overly aggressive server or relay that checks the Information-Request or its Reply for options from doing odd things if it sees the IAAddr. If we’re trying to make things safe, this may be best. Note also that it may help other devices in the path that may want to snoop for this data. (But it could have downside if any “options” are developed as then those specifications would need to determine if they are also allowed in this new address option).On a separate note, one issue the current draft may need to document and is a consideration is that when O-bit (RA) and A-bit (PIO) is set, a registration only server should really support Information-Request as it will also get lots of those from clients that support DHCPv6 - it may just send back a pretty empty Reply.By using Ted’s suggestion of using Information-Request, it would be natural for registration only to be implemented at least sufficiently to send a well formed Reply even when not address registration request.It seems like a clever idea to use Information-Request at least for initial determination of support.- it avoids extra packets.- client could honor server’s INF_MAX_RT to reduce frequency of probing (likely periodic probing is not a bad idea).- Bernie (from iPad)On Sep 14, 2023, at 11:29 AM, Lorenzo Colitti <lorenzo@google.com> wrote:What I think would be most expedient (if we must use DHCP to probe for support of address registration) would be to do the first address registration as an information request with the additional information in the information request, using the source address being registered. If the reply that comes back confirms the address registration, then all subsequent address registrations on this link would be sent as address registrations.Well, but if we can come up with a reasonable way to represent an address registration using an information-request packet, then why not make all registrations be information-request packets?+Bernie Volz any thoughts on using information-request and reply messages, instead of the new addr-reg-inform and addr-reg-reply messages currently defined in the draft?
- [dhcwg] WGLC for draft-ietf-dhc-addr-notification… Timothy Winters
- 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… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Erik Kline
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- 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… Sheng Jiang
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- 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… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- 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… Bernie Volz
- 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… Bernie Volz
- 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… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… David Farmer
- 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… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- 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… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- 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… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- 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… David Farmer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Nick Buraglio
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Timothy Winters
- [dhcwg] Fwd: WGLC for draft-ietf-dhc-addr-notific… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Timothy Winters
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Mark Smith
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… David Farmer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Alan DeKok
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… rob@deepdivenetworklng.com
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Nick Buraglio