Re: New document shepherd writeup
Lars Eggert <lars@eggert.org> Wed, 04 May 2022 13:12 UTC
Return-Path: <lars@eggert.org>
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 04F2CC159493 for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 06:12:54 -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=eggert.org
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 d1dbviNh_66L for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 06:12:49 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F609C157B4A for <wgchairs@ietf.org>; Wed, 4 May 2022 06:12:49 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:69a2:4d85:86c:ea75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 448D51DAA66; Wed, 4 May 2022 16:12:31 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1651669952; bh=ZJuWoD45Fux/NGZi1ixOCRO2XZmatBoxFThel2/v5k8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=LLdQ6s+cO2fuX4F8OtfYojlX7xl0qBRlfTbdUw/TkoLfDkFrziQoGbaw+t+v9qO9h hehHoB+Vh2nUuzfMXWyHNvqQ4cdEA3TzKaxya6yKryaE/f6Tep3gxFrHXjXgV5Gjf7 hOaE6nPnmig0bi1pMZvZKBTryQEFUHKvQA+2q1CE=
Content-Type: multipart/signed; boundary="Apple-Mail=_17E1FF99-A40F-4761-AE64-CC7D761F3B56"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: New document shepherd writeup
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <69281967-83db-9ec3-26e1-67028a0cfa92@joelhalpern.com>
Date: Wed, 04 May 2022 16:12:20 +0300
Cc: IETF WG Chairs <wgchairs@ietf.org>
Message-Id: <FAC35BA0-0955-4CCF-A278-D9BFF233C603@eggert.org>
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>
To: Joel Halpern <jmh@joelhalpern.com>
X-MailScanner-ID: 448D51DAA66.A3A19
X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/cGa287y41dBLOnbeqPzWU1kwQQA>
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 13:12:54 -0000
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. Thanks, Lars
- New document shepherd writeup Lars Eggert
- Re: New document shepherd writeup Mark Nottingham
- Re: New document shepherd writeup Bernard Aboba
- Re: New document shepherd writeup Mark Nottingham
- Re: New document shepherd writeup Lars Eggert
- Re: New document shepherd writeup Lars Eggert
- Re: New document shepherd writeup David Noveck
- Re: [irsg] New document shepherd writeup Carsten Bormann
- Re: New document shepherd writeup Salz, Rich
- Re: New document shepherd writeup Joel Halpern
- Re: New document shepherd writeup Lars Eggert
- Re: New document shepherd writeup Michael Tuexen
- Re: New document shepherd writeup Barry Leiba
- Re: New document shepherd writeup Brian Rosen
- Re: New document shepherd writeup Michael Tuexen
- Re: New document shepherd writeup Sean Turner
- Re: New document shepherd writeup John Scudder
- Re: New document shepherd writeup Fred Baker
- Re: [irsg] New document shepherd writeup Carsten Bormann
- Re: New document shepherd writeup Bob Hinden
- Re: New document shepherd writeup Thomas Nadeau
- Re: New document shepherd writeup Salz, Rich
- Re: New document shepherd writeup Sean Turner
- Re: New document shepherd writeup John Scudder
- Re: New document shepherd writeup Alvaro Retana
- Re: New document shepherd writeup Salz, Rich
- Re: New document shepherd writeup Paul Wouters
- Re: New document shepherd writeup Salz, Rich
- Re: New document shepherd writeup John Scudder
- Re: New document shepherd writeup Salz, Rich
- Re: [irsg] New document shepherd writeup Carsten Bormann
- Re: [irsg] New document shepherd writeup John Scudder
- Re: [irsg] New document shepherd writeup Carsten Bormann
- Re: New document shepherd writeup Mark Nottingham
- Re: [irsg] New document shepherd writeup Michael Richardson
- Re: [irsg] New document shepherd writeup Carsten Bormann
- Re: [irsg] New document shepherd writeup Fred Baker
- RE: [irsg] New document shepherd writeup Pascal Thubert (pthubert)
- Re: [irsg] New document shepherd writeup Michael Tuexen
- Re: [irsg] New document shepherd writeup Salz, Rich
- Re: [irsg] New document shepherd writeup Barry Leiba
- Re: [irsg] New document shepherd writeup Michael Richardson
- Re: [irsg] New document shepherd writeup Michael Tuexen
- Re: [irsg] New document shepherd writeup Michael Richardson
- RE: New document shepherd writeup Adrian Farrel
- Re: [irsg] New document shepherd writeup Michael Tuexen
- Re: New document shepherd writeup Sean Turner
- Re: New document shepherd writeup David Noveck
- Re: New document shepherd writeup Lars Eggert
- Re: New document shepherd writeup Salz, Rich
- Re: New document shepherd writeup David Noveck
- Re: [irsg] New document shepherd writeup Carsten Bormann
- Re: New document shepherd writeup Lars Eggert