Re: New document shepherd writeup
Brian Rosen <br@brianrosen.net> Wed, 04 May 2022 14:13 UTC
Return-Path: <br@brianrosen.net>
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 0F468C157B5E for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 07:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20210112.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 anRLy1pcunpn for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 07:13:44 -0700 (PDT)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 07399C157B4D for <wgchairs@ietf.org>; Wed, 4 May 2022 07:13:44 -0700 (PDT)
Received: by mail-il1-x134.google.com with SMTP id b5so952429ile.0 for <wgchairs@ietf.org>; Wed, 04 May 2022 07:13:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Icr/5l1PHF5TRiKMpUHVMW1/ciYOLSAI13pPkymHokA=; b=VlWLe3P4iEaPrS2Y9u39WI2Ii7fc6hJ5rBFywj5yGpnrHtAT77OJfyzoeaJK9xlpqw AGkewcps5QrMic3yoOZJrIVuxNsAlKaPgGZTqHKJ3lD6lnQrGdjypC1BOX6Ebpb+MzrJ EOt+A6Q62lFQAPRSqdg6yjjeAVeCEQhhiRxNrH+yyl2M9nV7E/vnlmGXdOmwZeh4FfZU hJD3oKPEd32iXmVOo4J7249ZBDNWAM0okBUIXPBnMtSVv6VvPXZqQCzZGaKIj0ZlmvKK VGt4j1ncZ7+nJMZ09u3SA8dielsLExrVN/csmAkeFZNXtm4xtOvYhUtL4sXW2SocCMQ+ ncNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Icr/5l1PHF5TRiKMpUHVMW1/ciYOLSAI13pPkymHokA=; b=sMId9Ta2dJQYKtaTa3JwVXxl9SRJuOkE6h6juy5rKyT7qaGxna0oPrxgfUGVGXi2/T XuunnEQWlOzLznKVvLyKGQPNa7XPSwOcbvezh9nsBYelayPsQoauOSQygS21/FJ9pL/d fpSo+kBt9LjE9jCkZQiEjA2VCpQwQCZSfASYivllOdCpskw7mkr/xbVqEDweNo9/yNVm ZKEB6PwcioTa0sVd9EkvV8Zyd/0TIBSevAoaYwo8YI+GIft3mmeSgC/PO2vUXBp8IVUK dWJ/S5Xu9juacm1o6MZmlgmqGW28V6WIU8TUF8SxPco2BA+avOfBCJniZN4hYse2OBfW rT8w==
X-Gm-Message-State: AOAM530D3pvwk9UrpgGPCaeIuo88z7or1vzfF5HRszy2rOcONbC95J79 u+gzBQ/5oUgrD0SadqhvIZdjSQ==
X-Google-Smtp-Source: ABdhPJwfN1m12Udz8plJz09jI/ezm5wQu/H0UF5YkdY5wneqICvfGiGJvpMi11loWDym4hs5Zy0ofA==
X-Received: by 2002:a05:6e02:1987:b0:2cd:a2e1:c0a9 with SMTP id g7-20020a056e02198700b002cda2e1c0a9mr8641257ilf.104.1651673622650; Wed, 04 May 2022 07:13:42 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id y17-20020a056e02129100b002cde6e352cdsm4207088ilq.23.2022.05.04.07.13.41 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 May 2022 07:13:42 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <201782E3-9712-4685-94E0-FF59D49D4096@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5C17E541-5DE5-48A2-82F4-A563F3E3753C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: New document shepherd writeup
Date: Wed, 04 May 2022 10:13:37 -0400
In-Reply-To: <E66933CF-1272-48D2-A8E7-BE1CE0859D3B@macmic.franken.de>
Cc: IETF WG Chairs <wgchairs@ietf.org>, Michael Tuexen <michael.tuexen@macmic.franken.de>
To: Lars Eggert <lars@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> <FAC35BA0-0955-4CCF-A278-D9BFF233C603@eggert.org> <E66933CF-1272-48D2-A8E7-BE1CE0859D3B@macmic.franken.de>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/_i3OuNV82jmSvsBj9jK_EiNVQgQ>
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:13:45 -0000
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
- 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