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

Bob Hinden <bob.hinden@gmail.com> Thu, 22 June 2023 14:57 UTC

Return-Path: <bob.hinden@gmail.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 13887C15198E for <gendispatch@ietfa.amsl.com>; Thu, 22 Jun 2023 07:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iEgV9gYrIAql for <gendispatch@ietfa.amsl.com>; Thu, 22 Jun 2023 07:57:33 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 391D2C1524A3 for <gendispatch@ietf.org>; Thu, 22 Jun 2023 07:57:33 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id af79cd13be357-76300f4d7eeso419383485a.1 for <gendispatch@ietf.org>; Thu, 22 Jun 2023 07:57:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687445852; x=1690037852; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=rk89AifDvb10GMdkMuIlJYT5w+UqOx3yV/PntAztJ9M=; b=MTkhG+ODxGWj2ML5emWTVFM6OJLUFqhnbgVk7SuLSkrHA/6YuQ7ZmaSHN3p2K5/YJf LeTANDfxV+5svu864akFmnxvX9G0NwKwheyDBaWYh1+2EQBvdBKXQTgiaAkNGpIhD85e Y/huADmwALWML1frNx7Ru5nL404FOZwkAOlsuTPOGk8HlWhHqmb85tiGFAigLLZoQXYc wPeBfTTeFKO5r3J+a5+unjnTmkwZWXp2gGJ4WV0UjKgvBvwpfut0c6XsIW7z0idy7v4/ ug4dV/+MrC/b7rvbJs6Sq6VBbb9iC7TXECP7qHUkEiBI/iwDPdh128DSqB61EEdl7cwN knrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687445852; x=1690037852; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=rk89AifDvb10GMdkMuIlJYT5w+UqOx3yV/PntAztJ9M=; b=CWdBy+ZivrpW8Ir31unqOpjKQFaX9NKv3CuVuhS9T9S8XlpxjEwFC+d24QAx87a4Hz KyIqyhaW2YbAlt7xWbWq59ihgdRB3oQxgLaMC99ZGnD+KQoksxIWoWJt48x0e+bLW2TO xkzAfn1h0oXYYfaMCeQNghZyTdpzTKn8o/03iShLVnGNerxUpOo6Vy/pV/ltt0DGvepC w2nOdclJ6fZSNJbXiRm6s4nHJoH5GFR4maWHZTtOjNcRgD8OY6ci4lVOlTnceuu5mw69 ycb3xHKS5GS0XeSjc6fgYVlseg/um3qSvQ8GIR6kro5JG6hsyYG/ZLupVHwGAirj6mMX WiYA==
X-Gm-Message-State: AC+VfDxWD2A/yi4KyRJ97wv/kTA2tfhzcqvp3Om2TaGpUpV1L5mXjmbB q7Bz0vTjRMXtZjSJor394YQ=
X-Google-Smtp-Source: ACHHUZ4OzSC4aJm0+oBZqU2J4O8ireQRP/H23a2a1cYihKqK+jXU9masgHVsJDxId3VSXOtes8Yj8w==
X-Received: by 2002:a05:6214:401a:b0:62f:f2fb:6915 with SMTP id kd26-20020a056214401a00b0062ff2fb6915mr19953866qvb.0.1687445852172; Thu, 22 Jun 2023 07:57:32 -0700 (PDT)
Received: from smtpclient.apple (99-31-208-116.lightspeed.sntcca.sbcglobal.net. [99.31.208.116]) by smtp.gmail.com with ESMTPSA id z13-20020a0cf00d000000b00626161ea7a3sm3898918qvk.2.2023.06.22.07.57.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Jun 2023 07:57:31 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Bob Hinden <bob.hinden@gmail.com>
X-Priority: 3
In-Reply-To: <231861687.27760.1687420035913@appsuite-gw1.open-xchange.com>
Date: Thu, 22 Jun 2023 07:57:19 -0700
Cc: Bob Hinden <bob.hinden@gmail.com>, John Levine <johnl@taugh.com>, gendispatch@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA947AC2-D22E-417A-BDF0-96E9F473FF55@gmail.com>
References: <6b349547-a26b-4028-14a7-6be3f3e44321@huitema.net> <20230620163302.ACBA8F6FA18F@ary.qy> <231861687.27760.1687420035913@appsuite-gw1.open-xchange.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/7yWndSWR2eqOPs0Dhkj3Dzfpr64>
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: Thu, 22 Jun 2023 14:57:35 -0000

Vittorio,

> On Jun 22, 2023, at 12:47 AM, Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org> wrote:
> 
> 
> 
>> Il 20/06/2023 19:33 EEST John Levine <johnl@taugh.com> ha scritto:
>> 
>> 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.
> 
> Don't misunderstand me, I do think that backdoors in crypto are a bad idea, but: is the cryptographers' explanation of why we can't have them a technical or a policy argument? I always understood it as "if we do, there is no way to eliminate the risk that they will fall into the wrong hands", but whether that risk is acceptable or not and under which conditions is a policy decision, not a technical one.

I think this shows that there is not a separation between “policy” and “technology”.   Many (perhaps most) technology decisions are also policy decisions.   It doesn’t work to think that they are separate domains.   

Bob