Re: New document shepherd writeup
Barry Leiba <barryleiba@computer.org> Wed, 04 May 2022 14:11 UTC
Return-Path: <barryleiba@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 E0A28C159498 for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 07:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level:
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 B8f54MENqzjD for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 07:11:21 -0700 (PDT)
Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) (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 0AE32C159490 for <wgchairs@ietf.org>; Wed, 4 May 2022 07:10:35 -0700 (PDT)
Received: by mail-ed1-f49.google.com with SMTP id a21so1859498edb.1 for <wgchairs@ietf.org>; Wed, 04 May 2022 07:10:34 -0700 (PDT)
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:content-transfer-encoding; bh=GudvAGTNctBqs0sqSKIOlaI4eCQHqfSlOxJG72IldbA=; b=3P0oBvenoZt0rEN9TeaobJB+nSzp9iZoRrGZmuPC+vZjpZeB1HNbF289hcaavztEFS qzg/WjPLG29wZv80f5Qfj+pwhIbvsXpdCJyJpnRhsEMBDhHNOijxa9CUNcmuh5CS/k7i CrNmOyPV2dKD3pjnDrTMztQjc+rPMHiRUYE7lMaMX+ISLprTA+hV8Wr+0pqXEz6iKNtz 92uLfFW6MEzjGKyQ3z3R8mWbse1lVvZGj16Vw8uR0TMhcf69MYI1OQhowPWvQKCGHCwL 01y+zcR3E/4lXSO+YAvh0on7DfN5PasG8eLUM35AIM85Vsqr4TNCvv6jZxm/4T1spStZ pKpQ==
X-Gm-Message-State: AOAM532HOO7v81rXexbPQVq6ZKXygCnU4gc7e4jsqmnYNfZvA47swrhb 5LfMjcI8H3KxWsS2fh36Rv5w1P8iXyaU6N7m4EA=
X-Google-Smtp-Source: ABdhPJzejEFidOLbxS6FYdKatQzB5XIGqTYNwmMgD/CZQf3Qcori/dSBCV4gGvWPK7H/rJmbEh/q8Oue5uRi/A0CJ4c=
X-Received: by 2002:a05:6402:2793:b0:428:1303:1b43 with SMTP id b19-20020a056402279300b0042813031b43mr2898556ede.226.1651673433321; Wed, 04 May 2022 07:10:33 -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> <69281967-83db-9ec3-26e1-67028a0cfa92@joelhalpern.com> <FAC35BA0-0955-4CCF-A278-D9BFF233C603@eggert.org> <E66933CF-1272-48D2-A8E7-BE1CE0859D3B@macmic.franken.de>
In-Reply-To: <E66933CF-1272-48D2-A8E7-BE1CE0859D3B@macmic.franken.de>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 04 May 2022 10:10:20 -0400
Message-ID: <CALaySJJrvyeej_jkzByVZbcMp6Q=Yj=ZcA63kck1J2FT0_3k0g@mail.gmail.com>
Subject: Re: New document shepherd writeup
To: Michael Tuexen <michael.tuexen@macmic.franken.de>
Cc: Lars Eggert <lars@eggert.org>, IETF WG Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/JTfOntCowkuQADkFXGk9moWQBbM>
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:11:23 -0000
> When is a person a contributor? Whoever is listed in the Ack section? Why are > these persons required to answer such a question? Well, truly, BCP 79 requires *anyone* who influenced the outcome in any way to be aware of their obligations and to make a disclosure if they have anything to disclose. So this is, really, a fair question. Honestly, I think this is just a question of sending a reminder to the WG mailing list and asking if there are any disclosures that should be made but have not yet been. It may seem unnecessary, as everyone has seen the Note Well, but reminders during WGLC don't hurt anything. Barry On Wed, May 4, 2022 at 9:39 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