Re: [Gendispatch] Updated draft: Policy experts are IETF stakeholders
Eric Rescorla <ekr@rtfm.com> Fri, 23 June 2023 00:06 UTC
Return-Path: <ekr@rtfm.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 D1E64C151079 for <gendispatch@ietfa.amsl.com>; Thu, 22 Jun 2023 17:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20221208.gappssmtp.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 KwZLuQy8hjP9 for <gendispatch@ietfa.amsl.com>; Thu, 22 Jun 2023 17:06:27 -0700 (PDT)
Received: from mail-yw1-x112d.google.com (mail-yw1-x112d.google.com [IPv6:2607:f8b0:4864:20::112d]) (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 E9DACC14F73E for <gendispatch@ietf.org>; Thu, 22 Jun 2023 17:06:26 -0700 (PDT)
Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-5701eaf0d04so79030547b3.2 for <gendispatch@ietf.org>; Thu, 22 Jun 2023 17:06:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20221208.gappssmtp.com; s=20221208; t=1687478785; x=1690070785; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=EUMDQmKAXYzElgrCYVlmpmYpGwwCGTFwBqXuN8xoWHM=; b=yBWRbPgiJ++6hOU/ec/X+EJ41AtDK4SY2QzRHL+pFPacRA5ja5UzeqanoGfxBOWdwz rZ6sNwVm7PAyyKi3XWFM+uAgsDLrOzqaC4PHENkVsW/LVQ2QTGP7RG4Ew6Fx2s7JE7H3 ZqL99ygDIjt5JnZWfcUZxFCpayKSX4k7pTsofWtoV8IVieUmSKAv/olMBQxeNA3HTeTh nGA67qkiiU3tMdlLnn199jpB70PZXY2hujXSS1Xu6oZacEBDK39hMHRrP2lsmqJk9ahI lDP+oR/aq/EuhISXDvki0gP3nnAMuWH4kcFDKSFY3Dec6eRjaNrAAV3IVqihKQDgbGDR 52WA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687478785; x=1690070785; 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=EUMDQmKAXYzElgrCYVlmpmYpGwwCGTFwBqXuN8xoWHM=; b=D7Vl6KKKQvhQSiJ9xjsk6bsJAa+sheq6vEQRKT8kqnBRml0SiFyAx5m2THVFFhLQuj LLWGYFRwbE+DI3iNIoy0WIvckNSO+hqXPa8cU73iFTuovnaqwfRd4GZwrSzMkpa5ywSf doltb3dDBoyS3WqEjc2I7vBQesrJYqVcak0f83DlmD02cSWm4gq1KI4nnwu2ixPCX5CW Q7nkquGcEF3RI/WFu1yaM/OEaX7xzbpGFKo+VYJPGMCGtoxDTDaMeUqQ4sn0nOte9uek QKP1t4ZE5pyFXTukMMxHY3Zqwmiy4SsshVuGcy/0uiODBhVNoHiYHHILiIUC5utOOwNq Psxg==
X-Gm-Message-State: AC+VfDy4P3Aem9kx9h8OgRKtFC/RRiXC0In5NFxt7F7T1xN9wSdlBp5N sxmqe2XzpuYo+9aZvUYbsFxqQxCKwQ1/6lnG9gHkgCH2fLi2z6daAgA=
X-Google-Smtp-Source: ACHHUZ7OzydpTmJBlvHUiWj4dzaiKjDQnXXkcqL/jU728GxcoRWxj71JmEtgvF93e/lLIVhY3uHMvvCNjein7YKksvQ=
X-Received: by 2002:a81:4846:0:b0:569:5f4f:b316 with SMTP id v67-20020a814846000000b005695f4fb316mr19771947ywa.13.1687478785529; Thu, 22 Jun 2023 17:06:25 -0700 (PDT)
MIME-Version: 1.0
References: <168664933013.34090.4997665230118680759@ietfa.amsl.com> <CAFWDOZAtWL2q9Ev8=iwuzeZici9ujGiheW2tdYg_OMoC2Pk57w@mail.gmail.com> <e5361cb7-c898-9664-872d-74a21a782d0c@cs.tcd.ie> <c3cb95b2-5fae-3483-2f90-3d84664548e7@joelhalpern.com> <9397cd6b-6ff4-9a7c-e8cf-75f3dad9e8d7@cs.tcd.ie>
In-Reply-To: <9397cd6b-6ff4-9a7c-e8cf-75f3dad9e8d7@cs.tcd.ie>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 22 Jun 2023 17:05:46 -0700
Message-ID: <CABcZeBO0sKGFR=9ekjPdKu0JB82dG3KTW-Eyg3HozfCJM06qqQ@mail.gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: Joel Halpern <jmh@joelhalpern.com>, Stacie Hoffmann <stacie.hoffmann=40dcms.gov.uk@dmarc.ietf.org>, gendispatch@ietf.org, Marek Blachut <marek.blachut@dcms.gov.uk>
Content-Type: multipart/alternative; boundary="00000000000093efe105fec0c5c4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/ik7n3huqi8O5cQQp8fVaBjS8dNI>
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: Fri, 23 Jun 2023 00:06:30 -0000
I largely agree with Stephen's comments here. It seems to me that the argument made by this document goes something like this: 1. There are policy equities which deserve consideration in the development of IETF specifications. 2. Engagement by people engaged in policy issues (PEPIs) [0] would promote consideration of those equities. 3. In some cases, PEPIs feel that they are not being heard at the IETF or that their views are not being taken as seriously as they would like. 4. Therefore we need new structures to facilitate engagement by PEPIs. I mostly agree with the first three of these points. As argued in this draft, it's important to the multistakeholder model that people of all backgrounds have an opportunity to express their views and be heard (this is not to say that I necessarily agree with all of those views or that I think those views should be dispositive). However, I don't agree with the conclusion in point (4), at least if it's read as we need a new "home for people with policy expertise". A situation in which there is some "policy experts" community which coordinates largely with itself and then somehow liases with the IETF as a unit has a number of obvious problems: - PEPIs have a huge range of views, in many cases with governments on one extreme and people from civil society on the other. Those differences should be aired and resolved in some other body. - It privileges "policy" over other communities of interest that also might want to have input at IETF (e.g., accessibility, environmental concerns, etc.) - It makes it very difficult to evaluate consensus, etc. when input comes in in this way. Rather, what is appropriate here is for those with expertise to engage more fully with the regular IETF process, which means being WG members, reviewing documents, etc. To the extent to which PEPIs find it difficult to be involved in that way, then I think the IETF can help facilitate that engagement via the same kinds of mechanisms that we ordinarily think of as helping newcomers participate. -Ekr [0] I don't think "experts" is helpful phrasing here. On Tue, Jun 13, 2023 at 4:43 PM Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: > > Hiya, > > On 14/06/2023 00:04, Joel Halpern wrote: > > Looking at the draft, I was struck that it goes to some trouble to make > > clear that if policy folks are to participate effectively, they need to > > also understand the technology. > > Interesting. I didn't quite take the same message from the > draft. But in any case, I don't think understanding is in > itself enough to effectively participate in a piece of IETF > work, I'd say one really needs to be involved in the work and > not parachute in late on, at least in many cases. (Yes, I'm > ignoring things like directorate reviews/IETF-LC there but I > hope you get what I mean.) > > > The point I take away from that is that > > the obligation is on both sides, both the policy-oriented participant > > and the community, to help make that education happen. > > Yep, I agree with that. > > > Having said taht, I have trouble figuring out what to do with the > > draft. Not clear how or where it can usefully progress, for all that I > > found it interesting and informative in pulling together disparate > aspects. > > Ditto. > > Cheers, > S. > > > > > Yours, > > > > Joel > > > > On 6/13/2023 6:46 PM, Stephen Farrell wrote: > >> > >> Hiya, > >> > >> I just read the draft and recalling the discussion at > >> IETF-116 I fear that a message that I heard being sent from > >> the mic line perhaps hasn't landed. > >> > >> In particular, I think a number of people said that the best > >> way to ensure your favourite policy topics are considered in > >> IETF work is to have someone who is playing a full and > >> constructive part in that IETF work be familiar with your > >> favourite policy issues. Liaising, co-ordinating and setting > >> up new bodies will be nowhere near as effective. > >> > >> Yes, that's expensive (in time), but so is being involved in > >> IETF work, so that seems fair to me fwiw. > >> > >> Cheers, > >> S. > >> > >> On 13/06/2023 16:31, Stacie Hoffmann wrote: > >>> Hello everyone, > >>> > >>> Many thanks to those of you who provided feedback to us on the Policy > >>> Experts are IETF Stakeholders draft at the 116 Gen Dispatch meeting. > >>> > >>> We have uploaded a new version (see below), which we are preparing > >>> for the > >>> 117 meeting and welcome further input or ideas on how to refine our > >>> problem > >>> statement or scope potential solutions. In particular, we would welcome > >>> specific examples of how and where policy input is working well, and > >>> thoughts on a ‘landing space’ or next steps for this work. > >>> > >>> Please reach out to the authors directly with comments or suggestions. > >>> > >>> Also, if anyone is interested in reviewing or contributing to this > >>> document > >>> please let us know. It would be great to work with others on this. > >>> > >>> Best, > >>> > >>> Stacie > >>> > >>> > >>> > >>> > >>> ---------- Forwarded message --------- > >>> From: <internet-drafts@ietf.org> > >>> Date: Tue, 13 Jun 2023 at 10:42 > >>> Subject: New Version Notification for > >>> draft-hoffmann-gendispatch-policy-stakeholders-01.txt > >>> To: Marek Blachut <marek.blachut@dcms.gov.uk>, Stacie Hoffmann < > >>> stacie.hoffmann@dcms.gov.uk> > >>> > >>> > >>> > >>> A new version of I-D, > >>> draft-hoffmann-gendispatch-policy-stakeholders-01.txt > >>> has been successfully submitted by Marek Blachut and posted to the > >>> IETF repository. > >>> > >>> Name: draft-hoffmann-gendispatch-policy-stakeholders > >>> Revision: 01 > >>> Title: Policy experts are IETF stakeholders > >>> Document date: 2023-06-13 > >>> Group: Individual Submission > >>> Pages: 11 > >>> URL: > >>> > https://www.ietf.org/archive/id/draft-hoffmann-gendispatch-policy-stakeholders-01.txt > >>> Status: > >>> > https://datatracker.ietf.org/doc/draft-hoffmann-gendispatch-policy-stakeholders/ > >>> Html: > >>> > https://www.ietf.org/archive/id/draft-hoffmann-gendispatch-policy-stakeholders-01.html > >>> Htmlized: > >>> > https://datatracker.ietf.org/doc/html/draft-hoffmann-gendispatch-policy-stakeholders > >>> Diff: > >>> > https://author-tools.ietf.org/iddiff?url2=draft-hoffmann-gendispatch-policy-stakeholders-01 > >>> > >>> Abstract: > >>> The IETF’s work has significance for wider societal, economic, and > >>> political communities, though gaps and barriers to engagement with > >>> the IETF exist for policy experts. This informational draft > >>> introduces a problem statement and gap analysis of existing > >>> initiatives related to policy expert engagement in the IETF. It > >>> also > >>> poses questions we hope to work through with others in the IETF > >>> community regarding how to better enable policy expert engagement > in > >>> IETF standardisation, and on how we can build a culture which > better > >>> supports technical and policy experts working together to develop > >>> more robust standards. > >>> > >>> > >>> > >>> > >>> The IETF Secretariat > >>> > >>> > >>> > >>> > >>> > >> > -- > Gendispatch mailing list > Gendispatch@ietf.org > https://www.ietf.org/mailman/listinfo/gendispatch >
- [Gendispatch] Updated draft: Policy experts are I… Stacie Hoffmann
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… Joel Halpern
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… Brian E Carpenter
- Re: [Gendispatch] Updated draft: Policy experts a… Christian Huitema
- Re: [Gendispatch] Updated draft: Policy experts a… Stacie Hoffmann
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… John Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… Livingood, Jason
- Re: [Gendispatch] Updated draft: Policy experts a… Bob Hinden
- Re: [Gendispatch] Updated draft: Policy experts a… Adrian Farrel
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… John R Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… Martin Thomson
- Re: [Gendispatch] Updated draft: Policy experts a… Eric Rescorla
- Re: [Gendispatch] Updated draft: Policy experts a… Eric Rescorla
- Re: [Gendispatch] Updated draft: Policy experts a… Eliot Lear
- Re: [Gendispatch] Updated draft: Policy experts a… Christian Huitema
- Re: [Gendispatch] Updated draft: Policy experts a… Eliot Lear
- Re: [Gendispatch] Updated draft: Policy experts a… Colin Perkins
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… Jay Daley
- Re: [Gendispatch] Updated draft: Policy experts a… Eric Rescorla
- [Gendispatch] savage beasts at IETF meetings Jim Reid
- Re: [Gendispatch] Updated draft: Policy experts a… Mallory Knodel
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… Brian E Carpenter
- Re: [Gendispatch] Updated draft: Policy experts a… John Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Stacie Hoffmann
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… John Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Rob Sayre
- Re: [Gendispatch] Updated draft: Policy experts a… Andrew Alston
- Re: [Gendispatch] Updated draft: Policy experts a… Andrew Alston
- Re: [Gendispatch] Updated draft: Policy experts a… Tony Rutkowski
- Re: [Gendispatch] Updated draft: Policy experts a… Salz, Rich
- Re: [Gendispatch] Updated draft: Policy experts a… Andrew Alston
- [Gendispatch] Diversity and the IETF Andrew Campling
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… Rob Sayre
- Re: [Gendispatch] Updated draft: Policy experts a… Tony Rutkowski
- Re: [Gendispatch] Updated draft: Policy experts a… Rob Sayre
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… Mallory Knodel
- Re: [Gendispatch] Diversity and the IETF Brian E Carpenter
- Re: [Gendispatch] Updated draft: Policy experts a… Eliot Lear
- Re: [Gendispatch] Updated draft: Policy experts a… Stacie Hoffmann