IETF Logo Mail Archive

Re: New document shepherd writeup

David Noveck <davenoveck@gmail.com> Wed, 04 May 2022 07:07 UTC

Return-Path: <davenoveck@gmail.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4B8C157B3F for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 00:07:18 -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, HTML_MESSAGE=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 I_zjx-28bKWO for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 00:07:17 -0700 (PDT)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (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 9BB46C14F735 for <wgchairs@ietf.org>; Wed, 4 May 2022 00:07:17 -0700 (PDT)
Received: by mail-ej1-x62b.google.com with SMTP id j6so1084388ejc.13 for <wgchairs@ietf.org>; Wed, 04 May 2022 00:07:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eJH30NYCWw6SyL3j0lhR1ktg4mDPPpR88KAQxIe7Y/g=; b=aGU7LI+nKVLM8YEkNKuhCnZXaHKrlbITtD7GbE9xsJnLXZu2geKWgvJUbcxYAwVQuJ KUr13i3dnMxEevMU9pH6ClBEWrkHskFOIFgHXI5h5IYzkLzsV8Q/Hd/e7IMnHVCNLOTA GjjS7+MJm3sZzj3LeNfajsNo9szDXHfbTg4YDcCX+XIjec6wIEqrqcz95NFE6bQ23wyv oRSUthvutICXnBBb5k2tPufrT3BEZJ+SVQUSwdKQaunE3hfnG3TjUqcurO8xxUe0U1Lg y0a3rAy1v3/q7tSeS9nw8r+vqSnJJtHficRthjpEwU/Q0m2HbL7hNsnxwgUQ9HzbaHQc TwAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eJH30NYCWw6SyL3j0lhR1ktg4mDPPpR88KAQxIe7Y/g=; b=Y4C0JU17injWCptk0cSRwB5a94YDdQZnsEOi3fdadxBjtoM0+9uJG2hmYJ8gYUU/FD w2CFR3tDkMB5L7XRdINc496bIxOzDvNMRpuHy2qxxk45vO6Wh8IHqVsOvBAiWtXs84Jo S97Rwb6EfTaDlTmF7M+ezEyJUJRL+oBt+ZZIQCWV/ik+O+RFL+Fc/BmAX0O+9d3KC0Po 4g9Xp3eScI57yi3DAdspFFgm42lAOlHr4aUPSbVjsHKPlpkg0zJmuTdb2iAxeeWqcRoA jjkcAN44GchFb0j2pPNtWPJgphYC0Bv5DT60LhYewoCBmgxUww4DZsAH7CF4cCeWneZQ xBTA==
X-Gm-Message-State: AOAM533mSDFQQ6IxY56FI41t8p61h0QHskQYEQjQA4rGviNCmoJoQIMI QAgtqHaqGrvSWNa/0hA5RUeR6Emc6k0tQnULb752SLTQ
X-Google-Smtp-Source: ABdhPJxkM/oQnNOtM8Mjmy46jWVq5b2gD6goqKVdbl27rQd13sRYc7kR/lQO0IzKpIeJAsLMz3KbDnXLfi0nFEi0bw4=
X-Received: by 2002:a17:907:1b10:b0:6e4:bac5:f080 with SMTP id mp16-20020a1709071b1000b006e4bac5f080mr19072599ejc.24.1651648035451; Wed, 04 May 2022 00:07:15 -0700 (PDT)
MIME-Version: 1.0
References: <F4A44FCE-D31B-4FE8-9950-6C60CDD9DD36@eggert.org> <CAOW+2dsiHimBnUr1++Y+nq6r6oxA5jDa8sXM4g3k-vjXfDbPfQ@mail.gmail.com> <3EE82F27-F170-4E89-8491-B021C94E7B28@eggert.org>
In-Reply-To: <3EE82F27-F170-4E89-8491-B021C94E7B28@eggert.org>
From: David Noveck <davenoveck@gmail.com>
Date: Wed, 04 May 2022 03:07:03 -0400
Message-ID: <CADaq8jctB78HZMQD+K5WYv=1+6+790=ib=HSijE37n-Wfi5CYA@mail.gmail.com>
Subject: Re: New document shepherd writeup
To: Lars Eggert <lars@eggert.org>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, IETF WG Chairs <wgchairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000072779605de2a46f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/cPR9xJ4ZsVsauc-fSQv6Sl3f4_Q>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 May 2022 07:07:18 -0000

On Wed, May 4, 2022, 2:02 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> On 2022-5-4, at 1:39, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> >
> > "Has the interested community confirmed that any and all appropriate IPR
> disclosures required by BCP 78 and BCP 79 have been filed? "
> >
> > [BA] What is the "interested community" with respect to IPR
> declarations?


This leads to two questions:

A.  What is the set of (natural) persons included?

B. In what sense, do these persons form a "community"?

The use of the term "community" adds unneeded complication since there are
no communal actions referred to; only individual ones.


This used to be the authors of the document. Has it changed?
>
> it used to be just the authors, but then got broadened out to ask about
> the entire WG.


That sounds like a mistake to me.  How could the person doing the write-up
be aware of every member of the working group?  Maybe you want authors plus
working group chairs and not the whole working group.

With the current text an honest person would say "Many members of the
working group have not concerned themselves with IPR declarations for this
document. This is unlikely to change."

The wording "interested community" was chosen to also capture the
> non-WG-document case.


Understood.  I think the focus should be on the authors and we should avoid
reference to hypothetical communities.

Could this be made clearer?
>

I think it has to be.


> Thanks,
> Lars.


Thanks for dealing with this.

>
>

v2.23.0 | Report a Bug | By Email