IETF Logo Mail Archive

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

Lorenzo Colitti <lorenzo@google.com> Mon, 18 December 2023 03:22 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 C5AC6C14F600 for <dhcwg@ietfa.amsl.com>; Sun, 17 Dec 2023 19:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.609
X-Spam-Level:
X-Spam-Status: No, score=-22.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_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, 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 40Safw8Mampp for <dhcwg@ietfa.amsl.com>; Sun, 17 Dec 2023 19:22:24 -0800 (PST)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 A43AAC14F5FD for <dhcwg@ietf.org>; Sun, 17 Dec 2023 19:22:24 -0800 (PST)
Received: by mail-qv1-xf2f.google.com with SMTP id 6a1803df08f44-67f47b15fa3so3627656d6.1 for <dhcwg@ietf.org>; Sun, 17 Dec 2023 19:22:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1702869743; x=1703474543; 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=nNSnivz/YETB1v6xkVO7sfNJcaz7G6hmQXhaXh4OCnE=; b=KqZvaBYnumWJrgFC52JAsIH0eFtoAKlSIh0zo0+3g4P9qm0MipQ537dNcnhEmArhb8 HVdBRH6UZp2XGpPcHEQb0LHauBLuGdjd4boRN8+Zy5L7Qnv7bxWjJ3x7zyPIZRR5ym3U YHuRTpul3+OLKtBWot0gD2n2IhpiaodGkL4LjzKEf5EnZOxC3iWUvmWwoSJcMsUlQsmc 6W6A27eI1qOMixsy+5YxcH4Oc6RmtN+JQfs1co72dchF5gTm5v66llT8ExjsRgLb8NZG eMu67ijUqAMkopWUYBcSa9KejFQtcxUEpDMiNJAQEWnopvuGoV4DcM4O7zzCBp1NeiGO gxag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702869743; x=1703474543; 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=nNSnivz/YETB1v6xkVO7sfNJcaz7G6hmQXhaXh4OCnE=; b=V7QTOgLHSn85T/mdL9ul9r+1YH1pSi4apneHDJ+FTBAudUXXse69m9CbiWEzbCfexT sxSEEErohjKB1WcvPHJ8dBen92AArOcRfPK6z0ji93vBV8w/yd1EKsKs4uWWAIPo5FWR goT4f2r3CBPjv6QsZ/7d/3sF969DypHsU7LaBUDd2kmTIaxdsdE1A2FlSgTv0O8HPhtO SwsH3leRLARk2BO1fkjBOguj9RSy0Jdmcn7mu8aTpV6ZoE4kSaCOTARjX+/PQ1oZdSdM v0+D+mMdv/oK9xgM0vkO/qvmq3cwH3hz5mRL/dameFWh8CVcFp/bn/o9GMoSjQa55xOG unEA==
X-Gm-Message-State: AOJu0YyJcNVG64wx9hP20kPRNV1U3WLhXOo0awKwi0lZHt0PPLMG+oqd B1TADAhVjSU++frnGAbZX7dYwRn0F9HMctIK5wZdgA==
X-Google-Smtp-Source: AGHT+IHl6het8fLKDTE1XvM8uZ2nUpjwUPXO8VTDYLNDspMotypIz5lN4tQaw9LMcAOeBGA0OpR28r0YWbdjzyY0HeU=
X-Received: by 2002:a05:6214:2603:b0:67f:276d:a110 with SMTP id gu3-20020a056214260300b0067f276da110mr8994797qvb.110.1702869743196; Sun, 17 Dec 2023 19:22:23 -0800 (PST)
MIME-Version: 1.0
References: <CAPt1N1n1LxYRO39GEtoLa_z99Ti+ZPgHVtzZXrr1kba230Gg6w@mail.gmail.com> <7CF975FC-5450-4FAD-8D7B-1CF40A796728@gmail.com>
In-Reply-To: <7CF975FC-5450-4FAD-8D7B-1CF40A796728@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 18 Dec 2023 12:22:10 +0900
Message-ID: <CAKD1Yr2w_pm3YG7LzG4+EBT83WTnVOnxuVo6TrMUkHCfAgBDug@mail.gmail.com>
To: Bernie Volz <bevolz@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002498a1060cc04285"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/U4f1K8-0J8IWl7rrX1uYFVMXWss>
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, 18 Dec 2023 03:22:26 -0000

On Tue, Dec 5, 2023 at 10:00 AM Bernie Volz <bevolz@gmail.com> wrote:

> Keeping it simple is far better. Perhaps we should even consider that once
> a client receives confirmation that the link supports address registration,
> it sends them regardless of what future Reply’s (or Advertises) say. Only
> when the client believes the link has changed, does it clear the flag and
> send something (Information-Request) with the registration option in the
> ORO list when it lands at a (possibly) new location.
>

FWIW, I agree that this is the simplest and best approach. It simplifies
implementations, because they no longer need to track which servers
returned which option. Making this more complex is probably not worth it:
there are no functional benefits, and the only benefit is reduced multicast
traffic while the option is being rolled out or while the network is
reconfigured.

Michael, can you live with just saying that the client will enable
registration as soon as it gets confirmation that the network supports it,
and only asks again if it believes that the link has changed?

v2.23.0 | Report a Bug | By Email