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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 13 June 2023 23:48 UTC

Return-Path: <brian.e.carpenter@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 AB3C7C1516F8 for <gendispatch@ietfa.amsl.com>; Tue, 13 Jun 2023 16:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=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 lfmvnXlUKxs4 for <gendispatch@ietfa.amsl.com>; Tue, 13 Jun 2023 16:47:58 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 8CC6EC151701 for <gendispatch@ietf.org>; Tue, 13 Jun 2023 16:47:58 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id d2e1a72fcca58-652699e72f7so4721128b3a.3 for <gendispatch@ietf.org>; Tue, 13 Jun 2023 16:47:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686700078; x=1689292078; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=mm1W1SO50wfg4XHDb7E8OTFaZx1rXiMjPoKCg3SXjrw=; b=jbQLDXrMzjmP/JbOziQLzwmROOVUzO3XUQrFlFeZaQfs12JxN2bTqTv0fyDPqL1BBO W7SP8h8Ve/trBWO7arFf/0R6nBJGMmjVwx4a5ARNlurwfRIgWHCP4fHkzbtH6fvQtfX+ 060jms5r6JViTBYH87PWGzRyCSRxHDIIt6kFJwsBKeVGbqrXCbLMXvXf9WQ6eook4fQn /ni6TRs5drHT/81T0ubHc2hQ+9NvE/7c9L/4Dvc8Mm8bUtp9p8BeQ9KOLkySUYs2b1n+ KcIoZDrN90ewLd1e3fwJ9o8PKW2sAFdsR8VcyG6bWGd56Y+0gmS34BlZkP6dgyXjHRtA oczA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686700078; x=1689292078; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mm1W1SO50wfg4XHDb7E8OTFaZx1rXiMjPoKCg3SXjrw=; b=MPjo5hKo9+vlquLrA2/Ty2Dwbpo9z8br4blt6+d1jgVNJoKbwZWF65dDY5VAPlypep hsuq4rm6ap0oKvxrwv8+ZppEV//afRLYILK+l2A793GyDewgePWtpXhWHrcY65u0OK5j D3Dd6n5Te5+4w2X/zYvTG2W234Hk1CFzYGDqFt0ftRccqWvX3qx6lV95P6owHMA2R79m Nja5FmsMQ8Kx79xumbfIfgOant08fPCPtV8u3yC9qWIoRlEvWrFFpsGf32kjDMsZQvcU LMbT1ieYKvOuQzjrZgg8YZeW5mMOgpYS3iXR3vaGGH5QREvJi5ekN6XvRAqqtPVSmjop YkNQ==
X-Gm-Message-State: AC+VfDz4WXJUJXaPEw1IPtokqEu6Gy+f8o6RyuwbreCLx6qgX2UrRw+H upSGd8ALO61ekBAuS7u1wlo=
X-Google-Smtp-Source: ACHHUZ5w3+33gzUp4PBmxBy/YYuIX/fIkwG4c3zzzLuH8yGxWLj3Dwfn/KBMY5Juz/4smyrwkgys7A==
X-Received: by 2002:a05:6a00:1397:b0:65e:40d7:81fa with SMTP id t23-20020a056a00139700b0065e40d781famr307638pfg.11.1686700077540; Tue, 13 Jun 2023 16:47:57 -0700 (PDT)
Received: from ?IPV6:2406:e003:1184:f001:9991:d1ad:8c20:42bd? ([2406:e003:1184:f001:9991:d1ad:8c20:42bd]) by smtp.gmail.com with ESMTPSA id w1-20020aa78581000000b0064f46570bb7sm8645813pfn.167.2023.06.13.16.47.52 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 13 Jun 2023 16:47:55 -0700 (PDT)
Message-ID: <438e1d41-fcf4-2277-d384-9fd19395ce8c@gmail.com>
Date: Wed, 14 Jun 2023 11:47:47 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Joel Halpern <jmh@joelhalpern.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Stacie Hoffmann <stacie.hoffmann=40dcms.gov.uk@dmarc.ietf.org>, gendispatch@ietf.org
Cc: Marek Blachut <marek.blachut@dcms.gov.uk>
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <c3cb95b2-5fae-3483-2f90-3d84664548e7@joelhalpern.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/g4T0e0YCWYK2rtVMUr5CDM127CM>
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, 13 Jun 2023 23:48:02 -0000

I agree with both Joel and Stephen. IMHO there is nothing substantively
new in this area, compared with what I experienced as an IAB member
20+ years ago. (There are a few new talking shops.)

What is actionable that will help the IETF make the Internet work
better? For that matter, what is actionable that will help the
IETF make the IETF work better?

We could perhaps look at draft-farrell-tenyearsafter as a sort of case
study. Would some additional liaisons or committees have improved the
outcomes (i.e., produced more or better IETF specifications mitigating
the problem of pervasive surveillance)?

We do have a formal relationship between the IETF and the policy world
in Section 5 of RFC 8712:
https://www.rfc-editor.org/rfc/rfc8712.html#name-the-ietfs-role-in-isoc
so there is a pretty clear division of responsibilities.

Regards
    Brian Carpenter

On 14-Jun-23 11: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.  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.
> 
> 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.
> 
> 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
>>>
>>>
>>>
>>>
>>>
>>
>