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

Stacie Hoffmann <stacie.hoffmann@dcms.gov.uk> Tue, 27 June 2023 14:52 UTC

Return-Path: <stacie.hoffmann@dcms.gov.uk>
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 4A7F5C15108A for <gendispatch@ietfa.amsl.com>; Tue, 27 Jun 2023 07:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_GOV_DKIM_AU=-0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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=dcms.gov.uk
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 BjfqwDpIHX2N for <gendispatch@ietfa.amsl.com>; Tue, 27 Jun 2023 07:52:48 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 9E6ACC1575B3 for <gendispatch@ietf.org>; Tue, 27 Jun 2023 07:52:47 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2b63e5f94f1so40627731fa.1 for <gendispatch@ietf.org>; Tue, 27 Jun 2023 07:52:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcms.gov.uk; s=google; t=1687877566; x=1690469566; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yjeUficQK+WpOjXAkqdyklAKYcJy/jJHE3yBArojWNg=; b=hilhBTVqctkf739D9W+p5a+5stLjhMBZzQ6Lw/NIxwXONXISx2RuySv+w/x3Q1LVgS XScmS/BQ8s7UHYGpFedlq1dgoKinPWDvpo6y7ZNer1YBEd7Hiw+cAC5uyIhdDFl1bGN2 /ywU96xsjBCfxTLPOgcg7X8MsvR6CGZvlCMEjlx7AC5WcrVo6ON7mcetUclSfr1VDcyg cvCiDHhOjf3FxhqwGiNR5rl28detS8qtaMc7NGt3EwagMUBfiW9O2jvzULG8xDsXYiQ+ 85HfhWcbrwVTNgS+SQWWNV5m6UrGMRHhdcDbQa+Uyt0e62TRyaWEqjU8QnFP1s5nI0Xa l5nQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687877566; x=1690469566; 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=yjeUficQK+WpOjXAkqdyklAKYcJy/jJHE3yBArojWNg=; b=HONzU4L8spZKhNgoHXjAuPj+tRhpUzNJmJEwLbjMqE1PzgPlnqpWjLBsHEEmjjBcKU ZHMEfrsizJaXKdySL6oI8mgavarSb/fWSeJUZ6UXxrUEQIEXtneMzmzv/iC+RJTPHH4G XSMc+x4JrKpL1QhYYkzmBhrMaQXwvGK0rMMBgIJuxCgRZ3DDH6Gee/KYwFJHwNCd/rCo hhN26KtKy245RZTSZassmG0UUMRXa3KCWaaMjwyuUyzrAWEvsDzlnq96N25BDRMQi5/p sDNh2hnG5SfjjB6LZQadyr/7GQUfphX9NykaysxJVSabajrc8wqfMqVezXXT/S3QlFRy oLTw==
X-Gm-Message-State: AC+VfDx8gEsfde88ShZQBWdTRoLTbB2z4XZKEcMCY0B+Om8jBjYcdegF FGFFIs2/awrwx966DDOTEemA3caEVcN+POU3yK4IhCtVLnfBEKJ/zhg=
X-Google-Smtp-Source: ACHHUZ5O7hTXeGE5pXLSDUbaucR/xjuNwnwyIl6vZCwJPV0bQBcUHmadiNjSRM/jjNHMwOvcofCLxW+V7nQeV2mW17w=
X-Received: by 2002:a2e:a4a8:0:b0:2b6:9dcf:bcb6 with SMTP id g8-20020a2ea4a8000000b002b69dcfbcb6mr2498236ljm.19.1687877565780; Tue, 27 Jun 2023 07:52:45 -0700 (PDT)
MIME-Version: 1.0
References: <15c65bec-0a31-918b-ff1c-828361b68ab2@lear.ch> <20230624024249.DF9BCFA78580@ary.qy>
In-Reply-To: <20230624024249.DF9BCFA78580@ary.qy>
From: Stacie Hoffmann <stacie.hoffmann@dcms.gov.uk>
Date: Tue, 27 Jun 2023 15:52:29 +0100
Message-ID: <CAFWDOZB7b38jak4eg-uqyVc-2J=Y9eV2zrkoTD5TAbr2AstHrg@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: gendispatch@ietf.org, lear@lear.ch
Content-Type: multipart/alternative; boundary="000000000000bc0b4505ff1d9ed0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/mtx4LhHpd5MjM0WZGdNGAyrpFok>
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, 27 Jun 2023 14:52:54 -0000

Hi all,

Thank you for the constructive feedback across the different aspects of the
problem statement, and on ways forward.

It’s good to see the recurring recognition that people with policy
backgrounds engaging in the IETF bring value, as well as the discussion
around enablers of participation -- such as the obligation of all to better
understand the technology and partnerships between stakeholders. This is
the ‘bridge building’ that we discussed at IETF 115 and 116. In particular
Bob’s point that “many (perhaps most) technology decisions are also policy
decisions” articulates why we shouldn’t think of these as completely
separate domains.

We recognise the comments and suggestions on keeping existing ways of
working and strengthening them, as opposed to creating something new. At
this stage we see value in a dedicated venue to refine this problem
statement and discuss potential solutions in a coordinated manner, and are
not seeking to jump to any conclusions about what the shape or form of
solutions might be.



We will also be looking at making clearer the ‘non goals’ in the draft. For
example, this draft is not about giving any one stakeholder group special
treatment - it is about how we work together within the IETF, and the
potential to work better together. It is not about setting up a new
structure - but about discussing potential solutions to the problem. Nor is
this draft about any one specific policy issue, technology or standard.

Another discussion point that was brought up is the terminology ‘policy
expert’. We have seen this chain use “non-technical”, “people engaged in
policy issues” (PEPI) and “policy specialist”. This is an important
consideration we will take away, as well as making sure the definition is
clear. We’re focusing on addressing these challenges for a wider group of
policy experts not limited to those from governments, including the likes
of civil society, academia, industry etc.

We will continue to update this draft as a means of documenting this
problem space, and we welcome any further thoughts, or inputs. We look
forward to discussing more with you in San Francisco.


Best

Stacie


On Sat, 24 Jun 2023 at 03:43, John Levine <johnl@taugh.com> wrote:

> It appears that Eliot Lear  <lear@lear.ch> said:
> >I do agree with the sentiment that it is important *not* to divorce our
> >decision process from its policy implications, whatever they may be.
> >But that doesn't imply some sort of policy veto.
>
> That's a key point. I want it to be crystal clear that anyone is
> welcome to join in, and we're happy to help people improve their
> skills and understanding about what we do, but policy people get
> exactly the same role in our rough consensus as anyone else.
>
> R's,
> John
>
> --
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch
>


-- 


[image: Text Description automatically generated]

Stacie Hoffmann
Digital Standards Strategy Lead

Department for Science, Innovation & Technology

Tel: 07766598283
stacie.hoffmann@dcms.gov.uk
www.gov.uk/dsit
<https://www.gov.uk/government/organisations/department-for-science-innovation-and-technology>
 | https://twitter.com/SciTechgovuk