Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by September 13, 2023
Lorenzo Colitti <lorenzo@google.com> Thu, 14 September 2023 14:39 UTC
Return-Path: <lorenzo@google.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 366D3C15106E for <dhcwg@ietfa.amsl.com>; Thu, 14 Sep 2023 07:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.609
X-Spam-Level:
X-Spam-Status: No, score=-17.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 ll6pjMUxCA5s for <dhcwg@ietfa.amsl.com>; Thu, 14 Sep 2023 07:39:35 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 B9288C151066 for <dhcwg@ietf.org>; Thu, 14 Sep 2023 07:39:35 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-6c09d760cb9so574274a34.2 for <dhcwg@ietf.org>; Thu, 14 Sep 2023 07:39:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1694702374; x=1695307174; 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=PBBe+yZGqH3UwVws3rufUkjExk/8vh033Dv8v32DsZU=; b=grgsK8nX7Vhv0M1rZ1+wWlhnls+HpUgKtHygwIGIcyj6cAUD7R6QBZUyuVYeCxgIIW Jnrz0+FxlF84JpetOBkxWiGqybMMZ6Sn/PMLegVpJnNmqFDmQa7JLlMwy77xJH7Pe+mt On8VpU0upahYLvEID/I98ROfUOViWoDoswiaVCBsucE/d2qAnfl3wI7sTVqeoBGa3B2t LyaUuoJuMVkHRT0aUlcWnee9SNn+U1EmGetq5PPmZJQlbD2Wl6VPF7Ow4CxkP06qRS7z 6toWEo40rgcARDyJAITLbgH12YvoDlE3yFl4w60yIwuPIjam3LieEcuPKZfjzRUE+NmO IDPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694702374; x=1695307174; 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=PBBe+yZGqH3UwVws3rufUkjExk/8vh033Dv8v32DsZU=; b=N30qqB7/plXfHgmwiugdF1RwYrdAv/lw75UumOLih9wDu3otfUtXQ/O8jmXcQyeGk+ d14bsbHLfJ6j2iroYCWgL2RoPhorO1O+8IkNelu4basRqT536icfzaylsWQPG0W7sm4b wH2PdRiV1Rivo/YtVAcJ9+O3X5qS2AZ+Bs034wOFzcfjX5I0H+RrIYjGFMgcNyI2l9VX hRzqezBXaZkuiuhZEOXCymynmy8DgUB/f+5ZzsA3Hh6jiH/gL8bUALr2MkuRFVIOFQQG bSyNrgFLCYI9CIeQ7sGp9CIK1q/TyRK+G3zcthb8mdsoeEdqsDsEMz48EEHrKnqe8sOh sH6w==
X-Gm-Message-State: AOJu0YwLJHLzEmejKiPoi1PUuCFAbgL3QscFYi+9MBK5YGEoTqmtWE8x juoERwdvAgcXJzaLZ9COnStrUdjrBllD2WKPUC5p1mZKE8jMvCvjQrIvX8Wh
X-Google-Smtp-Source: AGHT+IEox6awittSZc/fOdgT1gm7YIYYQVtAR4+qlE5pksXfV/9RsdEJEA3eJLXVPf1rxDx2sUr33XbKchw66McY6Kc=
X-Received: by 2002:a9d:6aca:0:b0:6be:e1d6:821b with SMTP id m10-20020a9d6aca000000b006bee1d6821bmr6210351otq.31.1694702374366; Thu, 14 Sep 2023 07:39:34 -0700 (PDT)
MIME-Version: 1.0
References: <CAKD1Yr3AEOa_7dKM15g+z6ZPDApZz08vgCS4kn9Uvi=+B9Dthg@mail.gmail.com> <3F659608-5298-42B3-9403-2C2A170DFCB3@employees.org> <CAKD1Yr3no4WQ6-dsTYVNswfdT85zmg4fHXvLJPMa--ZT9=h6Og@mail.gmail.com> <A675F57A-7FDA-4011-A100-AA3CDA52A323@employees.org> <A87EAA8A-0A80-4FCF-BEB9-6C19022751E2@employees.org> <CAKD1Yr1qs_+Y+Eb+oSjYQ6-033anRkn3d_fcWXcZ6s5mCA-_aA@mail.gmail.com> <4705B18E-E96E-4EED-8CDC-70431600F59F@employees.org> <CAKD1Yr0BGoZNKgaO5wRVg9V2Cs6swj+POnVj+7hoPixkdByxug@mail.gmail.com> <98972EEB-EB29-4DDD-AF07-B4848D406C96@employees.org> <CAFU7BATFx-yW9p88BLOMCarps92ejj4zYkvJB=BBtPqOy9QD3A@mail.gmail.com> <DA08259F-B3AF-43CD-858C-5EBC399D20A7@employees.org> <CAFU7BASuLfBB0TswJdza2xtwhXqiZ=HHt-EvsofAK9zSp5G9TA@mail.gmail.com> <16472FC6-4253-4117-986A-2FE24B1ACDE8@employees.org> <CAKD1Yr0-NiA=U7vMtBhdUfF2nd5QVaTjOYd7k90be9whua9-3Q@mail.gmail.com> <CAPt1N1=7yzMhhQBKaZJhQ8KtyfpgaphugZ--FztCZcMNGbeTDg@mail.gmail.com>
In-Reply-To: <CAPt1N1=7yzMhhQBKaZJhQ8KtyfpgaphugZ--FztCZcMNGbeTDg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 14 Sep 2023 23:39:17 +0900
Message-ID: <CAKD1Yr1WAT46vdLG+v6t-MQZqTZ8yvyLbQcm+fOUt8po2UPhig@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Ole Troan <otroan@employees.org>, dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000006aa9b060552a5e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/yO1rXGeD-LztHucSg3PAPYJyfg0>
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 14:39:36 -0000
On Thu, Sep 14, 2023 at 10:34 PM Ted Lemon <mellon@fugue.com> wrote: > The approach would be to send an Information Request option that included > the address registration information. If the server supports this > functionality, it would reply with new behavior, whereas old servers would > ignore the information and in so doing, signal to the client that address > registration is not supported. This is still extra traffic we don't need, > but less of it. My only concern is that the source address requirements for > address registration are different than for information request, and it's > possible that some relay agents might drop messages with non-link-local > source addresses, or that DHCP servers might ignore them. So this would be > worth investigating. > Information-request isn't a great match for a few reasons: 1. As you say, equipment in the field would likely be quite surprised to see inforrmation-request options come from global addresses (although I think this is not technically prohibited by RFC 8415). This is less of a concern with the existing proposal because it's a new message type. 2. The retransmit logic is different - information-request has timers around when it needs to be refreshed (e.g., at most one message every 10 minutes, IRT set by the server, etc.), whereas the refresh logic you need for address registration is tied to the lifetime of the address itself which can change in response to prefix lifetime changes. 3. The fate-sharing properties of address registration require one packet per address, which is technically a violation of the IRT_MINIMUM time. 4. The address registration mechanism says that the server should register or update a binding between the client ID and IPv6 address. This might have compatibility implications on clients that for whatever reason use a global address to transmit information-request messages. None of these are huge problems, but it still seems fairly hacky. We'd basically have to say that address registration reuses the information-request message format, but the semantics and retransmit timers are very different. This seems like it would be confusing both for network equipment and for humans.
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- [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… 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