[Gendispatch] Re: I-D Action: draft-carpenter-gendispatch-org-proc-docs-00.txt

Eric Rescorla <ekr@rtfm.com> Tue, 24 September 2024 13:24 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 36C51C14F685 for <gendispatch@ietfa.amsl.com>; Tue, 24 Sep 2024 06:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=rtfm-com.20230601.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 Xxb0o9vE2apG for <gendispatch@ietfa.amsl.com>; Tue, 24 Sep 2024 06:24:02 -0700 (PDT)
Received: from mail-yw1-x112a.google.com (mail-yw1-x112a.google.com [IPv6:2607:f8b0:4864:20::112a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43730C14F61A for <gendispatch@ietf.org>; Tue, 24 Sep 2024 06:24:02 -0700 (PDT)
Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-6ddfdeed0c9so44515807b3.2 for <gendispatch@ietf.org>; Tue, 24 Sep 2024 06:24:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20230601.gappssmtp.com; s=20230601; t=1727184241; x=1727789041; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kYPcwHfQejX9q47KrVgLRhOHO/AJkcCsPQlxT1WZk1k=; b=W9V6BuAmaL43JLulX7UbJe7aeLs2G/Qh9Yuvwji67M5G8We2fiAQzZBH4Cdc3DiFRk kD8UeimA6phYjP7q7jZAGPskd6/8l3fpApp2LAJRMZz/ICY8PBoMfhdV8b+w6W5XK0yr I6H4MCtP40JeQynZ3k+qoFEfaBIjP13eW4AQfzUE+IOQbBbReTukkfDv92VCT/nWfHln D5xx3MRrU0pZjF5EVX3QZSqcDPH5Zwti6SP04300sOxxXQIhpW4DJ0U0sIvi3GKFJgAo IZFaZ+ZUmnFeet3KjSI71UlbPsvDGTz+oGwLqX9FELcnx4FopJBQeVa4Qt66tO8nDYYH zRZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727184241; x=1727789041; 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=kYPcwHfQejX9q47KrVgLRhOHO/AJkcCsPQlxT1WZk1k=; b=eFHji4iwgTVptjfKl616Z55uix8caWZrOsNtJKpCYKdomHuOGnEX+stuQF5fG5xt5E r4xtq9tz2D+ibMzu167s9Wc2ICAfmrOqrBZJXY2PuIWuJGpfkY9R5raVMeVlXdwwf2zj z961rHltXpjcJXgbNafo3d4kxpgJ8uhCt0CEoowxXd5Dkw/uTeHVS5onzmmebHx/8ddJ CYhtC26yf93WODot/WN+8fhAM1aG5OeXVJwMyHS6UW654/YphN3FeNmJv+mHuwNq5lIE aVmLXcpD9xGOsofqKn5ku17IeKr3pRTrjZEcZJJO71NXw7se9zA7HO3XWx5nXifjdcXS egWQ==
X-Forwarded-Encrypted: i=1; AJvYcCVCcvzRbK1FI+LIDE/bHYjJjYV2HKiOoetKxQ1JyTCVFUHv7lz8kinYiJCPELJKhVAmfGhf/WBJCFcufA==@ietf.org
X-Gm-Message-State: AOJu0YxiGy93qOpPAlt3+IxVMAzl0K/XVF4alHRpfr2edlls5gPUlP8A 1QwhuWziES88y0C9SSyWqApuA4+Sdyw+StwVf5/+d2bRDJNSkNT8E2LqU1Ks2o3mzt9jDC9qwy5 zl9CITJW7BGWaBqjhcFr3UEUz5xYJvHTe7RLPBw==
X-Google-Smtp-Source: AGHT+IGvcJ+OMPETVKYwVd0WA5MUAo8FSLqHbhsPzO1RY1gc3X0nxrQuWaJdERA+zu8/FDBZnXd8KJu+1fkrY0+kqKY=
X-Received: by 2002:a05:690c:7305:b0:6db:e280:a3ae with SMTP id 00721157ae682-6dfeed59ab9mr129477487b3.23.1727184241373; Tue, 24 Sep 2024 06:24:01 -0700 (PDT)
MIME-Version: 1.0
References: <172714913950.1303095.258693123434634616@dt-datatracker-65695bf5bc-rgg8z> <a6729ae9-3dc9-4ea9-a89e-effd62f07c89@gmail.com> <1630744c-0be2-4e16-a863-65ac5c968952@lear.ch> <CA+9kkMCXtjcWkM+0Wer3BWL85MiZAxXg2pUzYGYLJug0gfFCJw@mail.gmail.com> <0FDB6E9E-BCDE-46D8-9E12-F324A4278745@ietf.org> <89da642b-175f-4d1c-be41-3d6a3faaa490@lear.ch>
In-Reply-To: <89da642b-175f-4d1c-be41-3d6a3faaa490@lear.ch>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 24 Sep 2024 06:23:24 -0700
Message-ID: <CABcZeBMw6DMqgCxpZsEx7b2Z7BbEGRkDO5tM-OyrxC_a7htPPw@mail.gmail.com>
To: Eliot Lear <lear@lear.ch>
Content-Type: multipart/alternative; boundary="0000000000002b56540622dd6b88"
Message-ID-Hash: KG4FPVCCHBX3ADGBOVCTI4KT5SGC6AXR
X-Message-ID-Hash: KG4FPVCCHBX3ADGBOVCTI4KT5SGC6AXR
X-MailFrom: ekr@rtfm.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Jay Daley <exec-director@ietf.org>, Ted Hardie <ted.ietf@gmail.com>, gendispatch@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Gendispatch] Re: I-D Action: draft-carpenter-gendispatch-org-proc-docs-00.txt
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/7NaSMbIijptFGyczpayL4DnxaT4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

It would not address mine. I think we should keep a bright line here and
that means not have the staff involved in writing the documents at all.

-Ekr

On Tue, Sep 24, 2024 at 6:18 AM Eliot Lear <lear@lear.ch> wrote:

> Between online and offline commentary, what I'm getting is that people are
> very concerned about the staff stepping into a policy making roll.  I
> suggest the middle ground here is as follows:
>
> It would be good if we could ask for help on an editorial level to collect
> and collate all the existing processes in a NON-NORMATIVE fashion.  That
> is- help us understand what we have in a way that seems coherent.  Then we
> the IETF community can do what we want with that.
>
> Ted, would that address your concerns?
>
> Eliot
> On 24.09.2024 14:49, Jay Daley wrote:
>
> Hi Ted
>
>
> On 24 Sep 2024, at 13:36, Ted Hardie <ted.ietf@gmail.com> <ted.ietf@gmail.com> wrote:
>
> Hi. Eliot,
>
> On Tue, Sep 24, 2024 at 2:31 AM Eliot Lear <lear@lear.ch> <lear@lear.ch> wrote:
> <snip>
>     • We dispatch this to the LLC (assuming they are okay with that) to perform the consolidation, with the understanding that the goal is not to create or change any policy but to simply document it all in a way agreed.
>
>
> If you review https://www.ietf.org/administration/overview/ you will see that work like this is explicitly out of scope:
>
> The IETF LLC has no role in the oversight or steering of the standards process as currently conducted by the IESG and IAB, the appeal chain, the confirming bodies for existing IETF and IAB appointments, the IRTF, or ISOC's memberships in other organizations.
>
> At least as I recall it, that separation was a core part of developing the community consensus around the IETF LLC approach.  Dispatching documents that describe the standards process to them seems to me to be a non-starter as a result.  If you want to hire an editor, I think you have to do it outside the LLC itself.
>
> LLC staff regularly act as professional authors, writing primarily website content relating to all aspects of the IETF, including the standards process.  Most of the time this is simply taking existing content and rewriting it in a more consistent, accessible and integrated (i.e. reducing several overlapping pages to one) form.  Whenever we do so, the content is checked by IESG members and other community members before publication.
>
> For examples, see my regular updates to the now closed tao-discuss list about reuse of Tao content https://mailarchive.ietf.org/arch/browse/tao-discuss/ and the authors site authors.ietf.org.
>
> Provided that is what would be asked of us, then I see no inconsistency with RFC 8711, which is where the role of the LLC is set.
>
> cheers
> Jay
>
>
> regards,
>
> Ted
>
>
>   --
> Gendispatch mailing list -- gendispatch@ietf.org
> To unsubscribe send an email to gendispatch-leave@ietf.org
>
> --
> Gendispatch mailing list -- gendispatch@ietf.org
> To unsubscribe send an email to gendispatch-leave@ietf.org
>