Re: [Gendispatch] Updated draft: Policy experts are IETF stakeholders

John Levine <johnl@taugh.com> Tue, 20 June 2023 16:34 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF0D7C1575B0 for <gendispatch@ietfa.amsl.com>; Tue, 20 Jun 2023 09:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.148
X-Spam-Level:
X-Spam-Status: No, score=-4.148 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="VJPL09pA"; dkim=pass (2048-bit key) header.d=taugh.com header.b="W784BmMw"
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 opuh2AbVd8n3 for <gendispatch@ietfa.amsl.com>; Tue, 20 Jun 2023 09:34:07 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2BD3EC151554 for <gendispatch@ietf.org>; Tue, 20 Jun 2023 09:33:04 -0700 (PDT)
Received: (qmail 21631 invoked from network); 20 Jun 2023 16:33:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=547c.6491d4bf.k2306; bh=b9tj80tAFqggrNqQQ9bMdE9bUD0/b+GhisszN8Hu/Ns=; b=VJPL09pA5KKn0EmE+HmhgtLFzreUWmSxYaniOP4nidgLeSPglMVqFdMcdGl/EqHuH/JPpw8QSuRGNu5T9duhY0XTxmym1eWYKrUc4HFHTUKwrzrVHUNhjR/aBLNmW2VPvIYaa3g+9rphi362ln5Kp95eNNVBOojVDG0uhvfBjDc/KO0l7PFAnfPnfUx3YMC8SK73KZwlhi8POXAgRvXWqrqPmTzxi8joY59K1bAfuzjBuXqPKlqghO4jP4WAPKoF+vcvrtffK/JIoeEpenmq4SY1i4tGqNq34eU+upqqBKFKhYVk4y1v4WNR+qW4ZFshKqbTXq6i5wW95xNs9yVtZg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=547c.6491d4bf.k2306; bh=b9tj80tAFqggrNqQQ9bMdE9bUD0/b+GhisszN8Hu/Ns=; b=W784BmMwO8C9bz6mBskI1fOUF1YzJmjncKhkuHjkeMLOD3SgErQOKpyoPTaWRQqQMMzhm0iX9Q+LavXxyHAKioUxYbHaQ3kGoUcVAlNCiC0m8JygHQCZ2Y1txhIVVBy4qlCX+sNaMKBK4wJjsYq4GgPtCES/73rzc1s5ycVVvCNJbw+mogCWDyC53oh8DieR25g2WS7QidsD4glUAeZzS0Hx/V3O/bpjmz9zMOc3HaQ2IXnKOof9+Alqx28My4I+rLd2encYr8Q0XxvL7v9/A2g10IyRWPm3AtKORJ7aBMQzP65+ayQFPw0YHtWIkE2e/HBDJqRuX1RCYc4j7Q5bLg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 20 Jun 2023 16:33:03 -0000
Received: by ary.qy (Postfix, from userid 501) id ACBA8F6FA18F; Tue, 20 Jun 2023 12:33:02 -0400 (EDT)
Date: Tue, 20 Jun 2023 12:33:02 -0400
Message-Id: <20230620163302.ACBA8F6FA18F@ary.qy>
From: John Levine <johnl@taugh.com>
To: gendispatch@ietf.org
Cc: huitema@huitema.net
In-Reply-To: <6b349547-a26b-4028-14a7-6be3f3e44321@huitema.net>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/LDM04bPOHaDwzWvf3bUo0xR8I8k>
Subject: Re: [Gendispatch] Updated draft: Policy experts are IETF stakeholders
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2023 16:34:12 -0000

It appears that Christian Huitema  <huitema@huitema.net> said:
>I could see the point of an external reviewer sending a message to "the 
>IETF" explaining that if not fixed, some draft will have a damaging 
>impact on some affected parties. In theory, our processes allow for that 
>to happen during IETF last call. I could see the "policy experts" 
>mentioned in draft-hoffmann-gendispatch-policy-stakeholders subscribing 
>to the last call list and doing just that.

Wow, I hope not.  I can think of several cases where policy people from
the HRPC parachuted into a working group and insisted that we change
or drop a draft because it would do something bad.  Except it was
painfully clear that they did not understand the draft, did not
understand what it did, and the purported danger did not exist.

While policy advice on technical documents can certainly be helpful,
it is simply not possible to provide useful policy advice without a
clear understanding of the technology. That's how you end up with
cryptographers repeatedly explaining why we can't put back doors in
cryptosystems and policy people telling us we have to, just nerd
harder.

I don't have any great advice to offer beyond the obvious observation
that we need ways both to help policy people learn about the
technology, and help technical people learn about the policy issues,
preferably both long before a contentious document goes to last call.

R's,
John