Re: New document shepherd writeup

Sean Turner <sean@sn3rd.com> Wed, 04 May 2022 14:42 UTC

Return-Path: <sean@sn3rd.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 268AFC15E6F3 for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 07:42:02 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 v7rOlLFmyvOX for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 07:41:58 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 25B54C14F739 for <wgchairs@ietf.org>; Wed, 4 May 2022 07:41:43 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id hh4so967374qtb.10 for <wgchairs@ietf.org>; Wed, 04 May 2022 07:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mLZYCjxir8Tl76YbTROltGuBHmLzqHZ7FOYGiAz9l7s=; b=PFtRYhqJw4hViisBGRb0QrkYF49MLS+z2+O9EJboTz7KlMoN6v+8kzjvK6QFym8DKF fPJKyU70/cZJ2cX43YVEHGHN7weJrRsE9ayfH/pa2ulPkzOTjr4dI0h+hvJ3oGcnpGuF IJqauuIzhUoq4Ru/tNbIZiBNqvFipaas7vy74=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mLZYCjxir8Tl76YbTROltGuBHmLzqHZ7FOYGiAz9l7s=; b=b3OH9o9REN8G/5MmEfYPjRIMNycVvPsv2nC7qR1Wl53S0mluyOEvvMiTuI3qmlTZRa 9m8SqBJPUDo4XW3aIO2d/V3Awvh7Siey/CMhIIt6XqQjQKNrZqPjsgjHhMHfBODpHMnK WCeKdz42exbhfB4S8HK4e5GS72OUjIedHCZNTBW+SdxDKoH5FxJSOEc+2DG8G0bGaBUT GSP108r2T3rX6IYxUjWLUoEH4vpKbgq77C73DeYNqpqvCmo6czzaITkwJdxmaWwBu3G/ 4Jv15OmUeIsTC4PnKhc1RY8yXO++zujx2IGUn55qoKEs2U94iFO0H2qzsFBTISzriw1i l9XA==
X-Gm-Message-State: AOAM533vASyq4ypDKyW1rCNKmzijBC+e8vEmVQTBzDIr2MEvJQ0Q0m11 bPeyIQ8LlyQJEc0vJcAWZXlv1w==
X-Google-Smtp-Source: ABdhPJw4sRNWOHfWjjrO8v5AjDJWChWp1HSFDV9lP3HGp3S7u5osGqh6uNUiQAxWLgzPFGx1AgqTBw==
X-Received: by 2002:a05:622a:c2:b0:2f3:a5f4:15a9 with SMTP id p2-20020a05622a00c200b002f3a5f415a9mr13645838qtw.522.1651675301396; Wed, 04 May 2022 07:41:41 -0700 (PDT)
Received: from smtpclient.apple (pool-72-83-85-4.washdc.east.verizon.net. [72.83.85.4]) by smtp.gmail.com with ESMTPSA id k4-20020a378804000000b0069c72b41b59sm7778642qkd.2.2022.05.04.07.41.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 May 2022 07:41:40 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Re: New document shepherd writeup
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <201782E3-9712-4685-94E0-FF59D49D4096@brianrosen.net>
Date: Wed, 04 May 2022 10:41:39 -0400
Cc: IETF WG Chairs <wgchairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF00EC50-740B-43FB-9CD2-26CAA9C36514@sn3rd.com>
References: <F4A44FCE-D31B-4FE8-9950-6C60CDD9DD36@eggert.org> <CAOW+2dsiHimBnUr1++Y+nq6r6oxA5jDa8sXM4g3k-vjXfDbPfQ@mail.gmail.com> <3EE82F27-F170-4E89-8491-B021C94E7B28@eggert.org> <69281967-83db-9ec3-26e1-67028a0cfa92@joelhalpern.com> <FAC35BA0-0955-4CCF-A278-D9BFF233C603@eggert.org> <E66933CF-1272-48D2-A8E7-BE1CE0859D3B@macmic.franken.de> <201782E3-9712-4685-94E0-FF59D49D4096@brianrosen.net>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/vM8bjaFzsyq7Ooy3EM6OJ_yVblY>
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 14:42:02 -0000

I was just about to ask a question related to Brian’s comment.

Previously when shepherd, I would send an email to the authors to confirm they had made the appropriate declarations. If I didn’t get a response, I stopped progressing the I-D. This resulted in some delays, but I got an answer.

Now, I am supposed to send an email to the WG and wait to get confirmations from all WG members subscribed to the list? ~1200 in the case of TLS!?!

Maybe I am just not thinking straight about this, but could the IESG provide an example of an email that I could send to the WG that will address the case where there are no IPR declarations and the other case where is some IPR declarations?

spt

> On May 4, 2022, at 10:13, Brian Rosen <br@brianrosen.net> wrote:
> 
> This is unworkable, please change.
> 
> You can get a “confirmed” from an author.  You can’t reasonably from any other larger group. 
> Acknowledgements nearly always include useful reviewers, who don’t get IPR disclosure requests (for their reviewing services anyway), so using that list isn’t useful.  We don’t track who contributes, so there is no way to get a list of contributors.
> 
> You can remind them, but you can’t expect to get confirmation.
> 
> I personally think a requirement to broadcast a reminder for every document has no value, but it’s not harmful.
> 
> But the proposed text, with any group other than authors is unworkable.
> 
> Brian
> 
> 
>> On May 4, 2022, at 9:38 AM, Michael Tuexen <michael.tuexen@macmic.franken.de> wrote:
>> 
>>> On 4. May 2022, at 15:12, Lars Eggert <lars@eggert.org> wrote:
>>> 
>>> Hi,
>>> 
>>> On 2022-5-4, at 15:46, Joel Halpern <jmh@joelhalpern.com> wrote:
>>>> As written, this seems to conflate two different concepts.
>>>> 
>>>> One of which seems to be a new requirement, although sometimes practiced.
>>>> 
>>>> The important existing requirement was that the authors (and by some interpretations the named contributors) confirmed explicitly that all known IPR believed to be relevant has been disclosed. That requires explicit responses from those people.
>>>> 
>>>> This text instead seems to ask if the WG has been reminded that they need ot disclose relevant known IPR. While a reasonable ask, it is not the same as the preceding and can not be answered the same way.
>>> 
>>> first, the term "interested community" was already used in several places in the previous shepherd writeup template; see https://github.com/ietf-tools/datatracker/blob/5a31658b7f87054237430ee5fab8a23a8b32a7e8/ietf/templates/doc/shepherd_writeup.txt
>>> 
>>> You're correct that a change was made to this original question:
>>> 
>>> 	(7) Has each author confirmed that any and all appropriate
>>> 	IPR disclosures required for full conformance with the provisions
>>> 	of BCP 78 and BCP 79 have already been filed. If not, explain why?
>>> 
>>> The text was broadened to "the interested community", because the shepherd need not only check that the authors have done so, but also that all contributors have done so. We probably should have phrased it as such and not reused the "interested community" term which was already used elsewhere.
>> When is a person a contributor? Whoever is listed in the Ack section? Why are
>> these persons required to answer such a question?
>> 
>> Best regards
>> Michael
>>> 
>>> Thanks,
>>> Lars
>