RE: New document shepherd writeup

Adrian Farrel <adrian@olddog.co.uk> Sun, 08 May 2022 10:28 UTC

Return-Path: <adrian@olddog.co.uk>
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 E996FC14F72D for <wgchairs@ietfa.amsl.com>; Sun, 8 May 2022 03:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.896
X-Spam-Level:
X-Spam-Status: No, score=-5.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 PrbgkDpvui-o for <wgchairs@ietfa.amsl.com>; Sun, 8 May 2022 03:28:08 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA338C14F612 for <wgchairs@ietf.org>; Sun, 8 May 2022 03:28:05 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 248AS3GX007846; Sun, 8 May 2022 11:28:03 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F39FC4604B; Sun, 8 May 2022 11:28:02 +0100 (BST)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E78C946048; Sun, 8 May 2022 11:28:02 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs2.iomartmail.com (Postfix) with ESMTPS; Sun, 8 May 2022 11:28:02 +0100 (BST)
Received: from LAPTOPK7AS653V (229.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.229] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 248AS2tZ023190 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 8 May 2022 11:28:02 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, 'IETF WG Chairs' <wgchairs@ietf.org>
Subject: RE: New document shepherd writeup
Date: Sun, 08 May 2022 11:28:02 +0100
Organization: Old Dog Consulting
Message-ID: <019901d862c6$4caccf70$e6066e50$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AdhixS45eKMG+2seR6Gy6GtuVCNeYQ==
X-Originating-IP: 81.174.197.229
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-26880.007
X-TM-AS-Result: No--11.186-10.0-31-10
X-imss-scan-details: No--11.186-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-26880.007
X-TMASE-Result: 10--11.185800-10.000000
X-TMASE-MatchedRID: xcONGPdDH5rxIbpQ8BhdbAPZZctd3P4BAp6lsfTM3hlSgqkaj4elxz88 nyn5HOwBBha/rZwVYuLlZK+3BWyIveMWqRkh2K5Ls/Hes76OTZBgg7HO8z2tNvn6214PlHOFrLa ELwoCkYsNUccATRyd1HF7+UHLZ5g9sdJb8mpdccTEOJqSsn5KmYGzTdEevOMzBs4BftuMujW+M3 06Ro3W2j0ofMt7UVhvKnA1SFKwwMmBTpnHfbEkYrIWaFTQBCxT3SkTY86NiDgsnVYl/hHtSXDKw DFz97J9l2GUABdhPsz3c6sm1T2zt8uLyiFWZU1rzG0LtXz4gg/F11Guem055247M5sxfdoIzv0+ UmYCZcN+J/o+y9+xUi6AiJWEY7cFHQQxGXS62WMp1j2WdPxkF97kIcn/7F/gXhmWufKBF2R4ove la7vbSufOVcxjDhcw5i/lXtZ4Z+wLbigRnpKlKSBuGJWwgxAra7leoU/OMhNYsCaawSIuKR9JE3 lBq5VjS+WwebxAXqPsyP3BiXARSVwnII/bATgRftwZ3X11IV0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/BgD3qk5zmosuXeztE_UNpOF37sE>
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: Sun, 08 May 2022 10:28:10 -0000

Historically, it was enough that the I-d contains text saying...

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

How could an author or contributor not know what that means and the requirement to disclose IPR? Well, obviously, there is a bit too much indirection there for many people to realise their obligations. Further, there are some people who don't even know they are co-authors or contributors on some document.

In the past we have been "surprised" by late IPR disclosures on RFCs where one of the inventors had a key role in authoring the document. While the courts may have an opinion on this (IANAL) and the fact of the boilerplate text may be considered a key fact, it doesn't help the WG to develop solutions with the level of IPR coverage that the WG is comfortable with.

So, with that in mind, some WGs that were particularly concerned by the existence of IPR or had been bitten by late disclosures decided that an explicit poll for IPR disclosures would be helpful. The most obvious times to ask are at WG adoption and WG last call.

However, as far as I know, these polls are not a formal part of the IETF procedures. They are just something individual WGs have decided to run: if the participants in the WG decided that they didn't want to go down that path, they could "persuade" the WG chairs to do different.

Now, the new shepherd write-up asks questions, but it doesn't force action. It says...
   Has the interested community confirmed that any and all
   appropriate IPR disclosures required by BCP 78 and BCP 79
   have been filed? If not, explain why. If yes, summarize any
   discussion and conclusion regarding the intellectual property
   rights (IPR) disclosures, including links to relevant emails.
A write-up might report on the IPR polls conducted by the WG. But it could just respond, "The I-D contains the regular boilerplate text that confirms that all authors and contributors are adhering to BCP 78 and 79," or even, "No such confirmation has been received because the Working Group does not consider it necessary to extract one."

Of course, the IESG could propose a new piece of process mandating confirmation in all cases.

Cheers,
Adrian

-----Original Message-----
From: WGChairs <wgchairs-bounces@ietf.org> On Behalf Of Michael Richardson
Sent: 08 May 2022 00:05
To: Michael Tuexen <michael.tuexen@macmic.franken.de>; IETF WG Chairs <wgchairs@ietf.org>
Subject: Re: [irsg] New document shepherd writeup


Michael Tuexen <michael.tuexen@macmic.franken.de> wrote:
    >> We seem to be asking now:
    >> a) At workgroup adoption time
    >> b) At WGLC call time
    >> c) At Shepherd write-up time (sometimes the same as (b))
    >> I feel like I've been asked at AUTH48 time, but I'm not really sure of
    >that.

    > I (as an author and as a WG chair) am only aware of c). Where is a) and b)
    > formalized?

It's not.  It just happens in some WGs, possibly in error/mis-understanding.
Some WGs would like to know at adoption time if there is any IPR.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide