Re: [irsg] New document shepherd writeup

Barry Leiba <barryleiba@computer.org> Fri, 06 May 2022 13: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 8012FC159A1E for <wgchairs@ietfa.amsl.com>; Fri, 6 May 2022 06:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.404
X-Spam-Level:
X-Spam-Status: No, score=-1.404 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, 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 LRUyt408h4W1 for <wgchairs@ietfa.amsl.com>; Fri, 6 May 2022 06:11:11 -0700 (PDT)
Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.43]) (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 27FB4C159A1D for <wgchairs@ietf.org>; Fri, 6 May 2022 06:11:11 -0700 (PDT)
Received: by mail-ed1-f43.google.com with SMTP id p4so8685552edx.0 for <wgchairs@ietf.org>; Fri, 06 May 2022 06:11:11 -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; bh=uTq5eIbV1+iHW1ijN6VeUn9/gz6Z00rbPRIpdZVA9HM=; b=X4OzXj/k337YyHHXKfRRXJG8CtqQVJNvAlGfhZ1QhdE8KEzxqur989cS+JK411Qixh gSB91U0JFRrBtDn5ReTqJqlm/XSAIA8gKrpKYWDX/aGQ4SBj+YKOrdnXLkVs/Pc6VePO edZ09LZ6zzWCoeetsgQqvgsolDkkIgbVcu+x9MAv8lwISSgrahxC0HzHRDqyQIdCYp/9 KFg6J7XunRkrNx2+OL4o/zk7VBVIKZEgDtHvIO8iga8JgcQWNK2NF7hFXy118ICzN6Z0 ndkoftYcdu3iDlq7AGYC25cjJVy5pviVwcV8ccF+WqPpvsxvdMMd6wM3vqCBUJJ/3sTk /iVA==
X-Gm-Message-State: AOAM531EhWPMGAN+yEdJXPQSslIVVUkRFaeKCFrWgjXM/+ULbyuqyaNx 62fCykLo4m9w0W3lFUhWVAhmUTJBnyMYNGhBOn1ZJj6fvbU=
X-Google-Smtp-Source: ABdhPJz7HLuMxroO3z8+aLLoqgeZIGBpSLE65P+aklfaXLuFF4fq4wer2LczMSHx4SkVJEy7KmY3cgKdvEcSJkieYWw=
X-Received: by 2002:a05:6402:128b:b0:425:d1d7:b321 with SMTP id w11-20020a056402128b00b00425d1d7b321mr3346171edv.179.1651842667772; Fri, 06 May 2022 06:11:07 -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> <CALaySJJrvyeej_jkzByVZbcMp6Q=Yj=ZcA63kck1J2FT0_3k0g@mail.gmail.com> <015C8742-F6C4-4C78-89A5-D2F912231D7E@tzi.org> <15584.1651794856@localhost>
In-Reply-To: <15584.1651794856@localhost>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 06 May 2022 09:10:54 -0400
Message-ID: <CALaySJK4ZCFNPvH4s9Ae9xaWgsZ1bXD4kFN0FTWmiUNdyjsmFg@mail.gmail.com>
Subject: Re: [irsg] New document shepherd writeup
To: IETF WG Chairs <wgchairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/oWypnHvleLXvZSMp2dIDlLPFvxQ>
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: Fri, 06 May 2022 13:11:11 -0000

Carsten says...
> Polling, yes, stalling until their confirmation, no.

Michael R says...
> Isn't the reason to subject everyone to repeated instances of NoteWell
> specifically so that they will know they have to declare IPR?
> (I'm not even sure I understand why we ask authors again, given that)

And, indeed, some tales from my time as an AD:
It might surprise many of you that we have some crusty people in the
IETF, those who are prone to get grumpy about things they think are
stupid.  I know that's far fetched, but bear with me here.

It, of course, won't surprise any of you that one of those "things
they think are stupid" is a requirement from the chairs to get a
direct answer to the "Are you in compliance with BCP 79?" question
before their document can proceed.  "I've read the Note Well 17,000
times," they will say.  "I've read the boilerplate in ever draft I've
posted," they will say.  "I've asserted that compliance more times
than I can count, and it's insulting to continue asking me... and to
make it a condition of progress," they will say.  Um.  Wrong tense:
not "they will say," but they did say."

At that time -- and I can't speak for the current IESG -- we reached
an understanding that it's the chairs' judgment whether the question
needs an explicit answer or whether the chairs know the authors well
enough to confidently answer the question from the chairs' own
knowledge.  As a chair, I've used that mechanism often... as with the
two quoted above: I will never ask Carsten or Michael that question
explicitly -- not because they're grumpy about it (they are not;
they're quite polite in this regard), but because I just know they
know the rules and are people of integrity.

If my AD tells me to handle it differently, I will consider that (and
will have the conversation with the AD), but there you go.

Barry