Re: New document shepherd writeup
Fred Baker <fredbaker.ietf@gmail.com> Wed, 04 May 2022 15:40 UTC
Return-Path: <fredbaker.ietf@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 E35AFC157B37 for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 08:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 yrnhx5PCP8nU for <wgchairs@ietfa.amsl.com>; Wed, 4 May 2022 08:40:10 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 6ACD5C147921 for <wgchairs@ietf.org>; Wed, 4 May 2022 08:40:10 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id t11-20020a17090ad50b00b001d95bf21996so5532257pju.2 for <wgchairs@ietf.org>; Wed, 04 May 2022 08:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pFYyNMWCG5lzgq/LWHFQYehjyogxrdbI//OtVGiiC5I=; b=F0MAj6IkTVtiwO0PXIyFxuUp/SBCQz+daod3d0WC3INFHSPn5VdxSwQhSUKWXvBv1b hbnun0JuYdQ5POnIZ2/MjMbvV2Af03mZV4cC3m0Dr4SDUP4ZD+QyYwEWYe88ld9iH2WM J/r9ewaTqhaa6yu+p2laXn9Wg9pos8BrjgYhqMXqyobXiBtcfX5vu2SDccyVKBDFoVo8 a5VRt6GBrWHqPk1fK9LsnyEqr6EcR60U+zGb1UBrrgKDH0Nx6F0QT2GMidfQfxV3gFN+ aJVTz8o/mh/oV0Uc3mhvWX9RdpS+9iM65wRsq63PS56SiNIybq4rO1jhySVS5QvEl4RG hUQA==
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=pFYyNMWCG5lzgq/LWHFQYehjyogxrdbI//OtVGiiC5I=; b=FCCRSbNo0l2fUzlAbpiYC/88JN0GMTiOXp50v/f8S2O/C87AbooUcZp8M74Ok8c2WA nlanVlZhd4Vnjzqy7x7qqGBsbEHVxyytp0B+2WpUBJ9WS/Z8zzCeAoL8XSukc4yLKVXg BuLxDY9dkCMFdbwYIO3ggX1uWqPmE7DwHtffNAV0ZItdCaQ/PqEmRPe0F5PcIA50J4ZC 15zyXvFMV9ul95q3xaBz89vkutAtRlBRleWbpfxPsDrXHcJJUS+h76ysi8McV+4znihJ 3Pe3bUYjqzX+B91Utzi8Z/aYgNT9rPRDDEL8IpGzgm1QrIwMOIWjm9upMB8h6mtZtYth 8M9g==
X-Gm-Message-State: AOAM533BMGDIXvF/tVFOnxht5lh/WG2WToEWdeObMNE/SxNJ+4cUZfGP c5udZmJqNtBCaWwIRNPE3xvoJ6LxCOs=
X-Google-Smtp-Source: ABdhPJyDi+XHPFtz/Wd/ukQizIkcxO5+T7q7F8hzF7bMtUaM8kQtj96w4YxHl0eTg1VjTsFZFAxHew==
X-Received: by 2002:a17:90b:1251:b0:1d7:f7ae:9f1 with SMTP id gx17-20020a17090b125100b001d7f7ae09f1mr57425pjb.65.1651678809530; Wed, 04 May 2022 08:40:09 -0700 (PDT)
Received: from smtpclient.apple ([2600:8801:d00b:e800:c989:703c:88f0:3b30]) by smtp.gmail.com with ESMTPSA id k22-20020a17090aef1600b001cd4989feb7sm3502225pjz.3.2022.05.04.08.40.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 May 2022 08:40:09 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.21\))
Subject: Re: New document shepherd writeup
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <FAC35BA0-0955-4CCF-A278-D9BFF233C603@eggert.org>
Date: Wed, 04 May 2022 08:40:07 -0700
Cc: Joel Halpern <jmh@joelhalpern.com>, IETF WG Chairs <wgchairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E6E4134-3271-4E6E-987D-663AA90B2522@gmail.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>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3696.100.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/PcPYmFCH1SrjwMl8tahsbjyr0wk>
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 15:40:11 -0000
> On May 4, 2022, at 6:12 AM, 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. From my perspective, if that is intended, then it should be said. Right now, we poll the authors and contributors. > 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