Re: [dhcwg] dhc-addr-notification: input required on the client behaviour

Lorenzo Colitti <lorenzo@google.com> Wed, 10 January 2024 01:32 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 73959C14CF1D for <dhcwg@ietfa.amsl.com>; Tue, 9 Jan 2024 17:32:08 -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=unavailable 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 dig_s0o09vat for <dhcwg@ietfa.amsl.com>; Tue, 9 Jan 2024 17:32:06 -0800 (PST)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 53319C14CE30 for <dhcwg@ietf.org>; Tue, 9 Jan 2024 17:32:06 -0800 (PST)
Received: by mail-qv1-xf2a.google.com with SMTP id 6a1803df08f44-68015293aa3so14651756d6.1 for <dhcwg@ietf.org>; Tue, 09 Jan 2024 17:32:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1704850325; x=1705455125; 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=nizqP/ByUjoJ+NPBzUA3D8XeVBqEbobXvdJlykx5QxE=; b=TprRKZDUGUdrI/qQjKBmFzCFirAujzCWAkm3Ct89r0zdn5fgngHgfgB/UZqS5voZzN 6H1aQ/uQTqa9BujlIHfbl25q6YZYFG0gi0W18fni90ci7apRDd2MhMVabBs4hcB0Dc1Q IPqwKc0hZORSdhx/G3Ve6Ltvx7PEp5AQAFpezT2jeCzF09teXAp4rRjDjzf9DksMoZEH 7S0c4/K4fZlhz6HEltgsYAGr04vMms1HQtC+tpTDU4JqC3fchzr2uWWJ1qfy/7VEjQ13 wWoWJ5dLZikWre/6Ttve/cqU4H/jQ4I0f313Yemg/WCstK2nbiEuMzCROlWGqIehfUrf xjxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704850325; x=1705455125; 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=nizqP/ByUjoJ+NPBzUA3D8XeVBqEbobXvdJlykx5QxE=; b=YNRkm5FEK7zenWAj5QdMracBFQLJv/SR6lbL/PF3zIQ7ETEqCQ7yKocOHsMD8Ma4UD msSAsyTYC79QRy/6B4+jDMJVpwNYq1IPaG0nPD5K/Coh33HXLdwcg8Y1QcbdjLsvMmo2 f1HYtbkaaXZ9eS+5zt9mxZsE+zlMlet9AcyDm/o/sXvsGC0pFyUBYg1G8AVrr9jr7/Or coqDyWqI6TaXHij+WRP2jNSp/9uAzX2vC7PnG7HrlaeTrKbUYMgVZe+8b/5gZp5SRssl 9qJIDrwHlneU8P9DikhF2ip7/oOsP0EHmqVoIbd0I6RXRLPNHIDL6qsXKf5T04sQlBaY +B+w==
X-Gm-Message-State: AOJu0YxTT8+zPeFrutZfIVwpOI5EO5VgbMwxko/B8rfB1RFi2R2NrejZ iWS8nt7wT5LqsGsQMdCd8k+XdOlLwKVGqXoETQJbSOHiL2IS
X-Google-Smtp-Source: AGHT+IFtMwnt62PrDZP+e85kfDdpXRr7W+6TxZBOh0nEqYkAiTiBWCqyW+x/E95Abqjgqz0uVzyE1aRY4JaWTT8dYLM=
X-Received: by 2002:a05:6214:29e4:b0:681:af:b686 with SMTP id jv4-20020a05621429e400b0068100afb686mr417331qvb.80.1704850324724; Tue, 09 Jan 2024 17:32:04 -0800 (PST)
MIME-Version: 1.0
References: <CAFU7BASCOHV_HQriarduvEjs5hUMwt3Qad+31AVwTjb=GQdmmQ@mail.gmail.com> <CAPt1N1=mhYdCNg3r9qU+7oStpD34bHWqFMo0AzVA5BJo5v=iVw@mail.gmail.com> <CAHw9_iJErpjX3BizFRjCKLJOsTXVCHBcQdzZQeTGgEKTYAEd4w@mail.gmail.com>
In-Reply-To: <CAHw9_iJErpjX3BizFRjCKLJOsTXVCHBcQdzZQeTGgEKTYAEd4w@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 10 Jan 2024 10:31:53 +0900
Message-ID: <CAKD1Yr2O5nPRxSDK58Vg7GVKVOf9P+RisYcH2A-d_sf_Ob9M7g@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Cc: Ted Lemon <mellon@fugue.com>, Jen Linkova <furry13@gmail.com>, dhcwg <dhcwg@ietf.org>, draft-ietf-dhc-addr-notification@ietf.org
Content-Type: multipart/alternative; boundary="000000000000007ef0060e8d660e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/yCCrErHTRbKZqOshrZ2qYjCm_fY>
Subject: Re: [dhcwg] dhc-addr-notification: input required on the client behaviour
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: Wed, 10 Jan 2024 01:32:08 -0000

+1. Avoiding a small amount of extra multicast traffic in these unusual
situations (misconfiguration, rollback) doesn't seem worth complicating the
implementation and increasing the risk of implementation bugs.

If the network has really serious problems with these packets (e.g., DHCPv6
server catches fire when it receives them) then relying on implementations
not to send them doesn't seem like a good strategy anyway.

On Wed, Jan 10, 2024 at 1:42 AM Warren Kumari <warren@kumari.net> wrote:

>
>
>
>
> On Tue, Jan 09, 2024 at 10:07 AM, Ted Lemon <mellon@fugue.com> wrote:
>
>> On Tue, Jan 9, 2024 at 4:15 AM Jen Linkova <furry13@gmail.com> wrote:
>>
>>> Would the group be OK if -08 contains Bernie's proposal?
>>>
>>> Not speaking for the group, obviously, but I think this is the right
>> choice. Anything else is an unnecessarily complicated protocol fix to a
>> configuration mistake.
>>
>
>
> Yup / +1.
> If the "failure mode" was more harmful then I'd have a different view, but
> seeing as it is a trivial amount of traffic (and in a weird corner case), I
> think that it's the right solution….
>
> W
>
>