[hackathon] Re: [irsg] reserved fields: must be zero

Carsten Bormann <cabo@tzi.org> Mon, 06 May 2024 20:14 UTC

Return-Path: <forwardingalgorithm@ietf.org>
X-Original-To: hackathon-owner@ietfa.amsl.com
Delivered-To: hackathon-owner@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F45FC15155F for <hackathon-owner@ietfa.amsl.com>; Mon, 6 May 2024 13:14:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1715026486; bh=FMO7RjBJVvlrcX5o3zAwaZPlvBH6W6um16Olda3wTlA=; h=Subject:From:In-Reply-To:Date:References:To:CC:List-Id: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe; b=iWYaA00U91n8TeuqTf02E4Z0ugNvtGxaaWgkOz5Uf7TSlCfPgyORKF3Fuyxngn40N Km4RHpFbSnJutJUOEnDNaD2c8zT5MNP1nS53wJq/4gsLrthdpQuacw7tCTw9SeH3eh u1YYpUoaEIk/CgYVfLWRZtETDIEV11PBz4kCLcoA=
X-Mailbox-Line: From wgchairs-bounces+hackathon-owner=ietfa.amsl.com@ietf.org Mon May 6 13:14:45 2024
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF94FC1516E9 for <hackathon-owner@ietfa.amsl.com>; Mon, 6 May 2024 13:14:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1715026485; bh=FMO7RjBJVvlrcX5o3zAwaZPlvBH6W6um16Olda3wTlA=; h=Subject:From:In-Reply-To:Date:References:To:CC:List-Id: List-Archive:List-Help:List-Owner:List-Post:List-Subscribe: List-Unsubscribe; b=EmJbZCGVDhf735K8+gY5SNG4uYSAaDVfhR8lTy8QkZSWT26bTT5qFiCJ4j3j8d2VB na1V8wXpvIHiyJMrMgTWU5na9WGVBb5MH7nRfgITfTkltCJyJQrVfePeeLbmHG9pFs ecgatuXnawqW7FciPM39+EVKISMesaunF5Dq6keA=
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67B0C14F6E4 for <wgchairs@ietfa.amsl.com>; Mon, 6 May 2024 13:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 zQpi7yxP-8eo for <wgchairs@ietfa.amsl.com>; Mon, 6 May 2024 13:14:34 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 D52ECC14F60E for <wgchairs@ietf.org>; Mon, 6 May 2024 13:14:33 -0700 (PDT)
Received: from smtpclient.apple (p5dc5d931.dip0.t-ipconnect.de [93.197.217.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4VYCLH0ybKzDCbq; Mon, 6 May 2024 22:14:31 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <B3FF960A-70E8-4EB4-8809-CD968673002E@pfrc.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5956294D-1487-4183-9A3B-016DC3A3E0A4@tzi.org>
References: <0D438514-8A5B-4B8F-937F-6458D771B073@pfrc.org> <CADaq8jd-bDXEW6YbaTHY8dXmPLCFcZfOb239022HY6FFdgRa_Q@mail.gmail.com> <1557157.1714989685@dyas> <0c3a01da9fd3$7f358260$7da08720$@gmail.com> <8845318F-92D2-4E24-8600-7EEF6F01DDAE@pfrc.org> <CALaySJKOANLMY8WvhhuAy+Sk6qveuXY=0vuCA6=Gar-uS9MVDQ@mail.gmail.com> <B3FF960A-70E8-4EB4-8809-CD968673002E@pfrc.org>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
X-MailFrom: forwardingalgorithm@ietf.org
X-Mailman-Rule-Hits: implicit-dest
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-hackathon.ietf.org-0; nonmember-moderation; administrivia; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
Message-ID-Hash: GU7CIHDUYIBAA2HZTSJNAJ7C45TJBPRU
X-Message-ID-Hash: GU7CIHDUYIBAA2HZTSJNAJ7C45TJBPRU
X-Mailman-Approved-At: Mon, 13 May 2024 06:09:16 -0700
CC: Barry Leiba <barryleiba@computer.org>, dthaler1968=40googlemail.com@dmarc.ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>, IETF WG Chairs <wgchairs@ietf.org>
Subject: [hackathon] Re: [irsg] reserved fields: must be zero
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/Qxi-Mbzf22Cs9smAIchfCAZDsDI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Owner: <mailto:hackathon-owner@ietf.org>
List-Post: <mailto:hackathon@ietf.org>
List-Subscribe: <mailto:hackathon-join@ietf.org>
List-Unsubscribe: <mailto:hackathon-leave@ietf.org>
Date: Mon, 06 May 2024 20:14:46 -0000
X-Original-Date: Mon, 6 May 2024 22:14:20 +0200

On 6. May 2024, at 21:36, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
>  you're just making someone non-conformant even if there's good reasons.

That is where we disagree.  
The second spec (the one that defines values ≠ 0, see my previous posting) updates the first (and needs to do so, otherwise you are right).  
If your product managers cannot be made to understand that concept, then indeed they have a problem (*).

Grüße, Carsten

(*) We could of course explain the concept somewhere and point to it each time we use it, like we always point to BCP26 when we select one of its behaviors.
Maybe that will be an outcome of this discussion and can further allay your concern.
I think such a document would be useful if only to avoid “MUST be zero” without specifying the receiver behavior.