Re: New Version Notification for draft-resnick-variance-00.txt

Barry Leiba <barryleiba@computer.org> Sat, 28 March 2020 14:20 UTC

Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93AC33A0E83 for <ietf@ietfa.amsl.com>; Sat, 28 Mar 2020 07:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level:
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7m1uD_OXjaO for <ietf@ietfa.amsl.com>; Sat, 28 Mar 2020 07:20:21 -0700 (PDT)
Received: from mail-ot1-f43.google.com (mail-ot1-f43.google.com [209.85.210.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51D2E3A0BD1 for <ietf@ietf.org>; Sat, 28 Mar 2020 07:20:21 -0700 (PDT)
Received: by mail-ot1-f43.google.com with SMTP id 111so12942603oth.13 for <ietf@ietf.org>; Sat, 28 Mar 2020 07:20:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=gKCb0g7grcsXIJVknSMrgYJ8fZPLMBXWSCT2R1Ip/IA=; b=LtrMI5YlC68kJFP2epFRhFTOy4M1LFMRAbFOeA4K9QFyy03WaoyLLRdGTpt7aLsFui Kt75zh2eNPnKe8tXdQW+Cq6hh98sCr1p3/NuNNudbt3/LEnWHg4JGrJOnaj0UIwWiwZa HxDHnhMOnowM50slqr0mp6WMHpnyp9dLqOKzXAT8m0K1wsFqFEv+VzEksilDeW25uAE8 j+DLT46/aYtQiW+an7V81bAX0lmDW4alYiaJWrq97uL/Gj1MeCJEEer/JzQ4DpK6NjlH Uv3DyXdNvIbxVmzlF35mn81QmH022chAjLXNr98/qv9NDoTvs13OVWdmFqjke3jVrrcR TN/w==
X-Gm-Message-State: ANhLgQ0TlkwiFzdbxqc+al5/3UrCoMXmckqRrqiZctVsBAoz3pJNgQ2i F5VIHiBRiM23v3+FWsbi+Exg3h8+naYJD/aVQQeX8w==
X-Google-Smtp-Source: ADFU+vtrereci6A1qcVFYtk8oW/QOo9jrTvulk/sTW8qdiouWux4v55j1j2bMlWTMfTwMplYxTPfjWbjMOcMv14UCcE=
X-Received: by 2002:a9d:1a3:: with SMTP id e32mr2967533ote.206.1585405220237; Sat, 28 Mar 2020 07:20:20 -0700 (PDT)
MIME-Version: 1.0
References: <158533925458.17797.13806166303625482245@ietfa.amsl.com> <AE66200A-E718-4BF6-BA87-EE427A0BF971@episteme.net> <0e9e0a5f-5022-9a06-b8be-46d922f31aa7@nostrum.com> <4f79a660-2268-dad0-e796-dc1fabfcf73d@network-heretics.com> <A2B6BC2A-5983-48D9-BF0E-F782BBA54004@episteme.net> <0b518909-d421-afe7-b473-3d7ea3b04648@network-heretics.com>
In-Reply-To: <0b518909-d421-afe7-b473-3d7ea3b04648@network-heretics.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Sat, 28 Mar 2020 10:20:08 -0400
Message-ID: <CAC4RtVA1j4vSCvgWstnajveAqgWYvu19UDSNKBagk3XjfDM=2A@mail.gmail.com>
Subject: Re: New Version Notification for draft-resnick-variance-00.txt
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RK3Pq_MtscUtBIuiPfpQ2Jjm7zQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Mar 2020 14:20:23 -0000

(Not picking Keith's comment, in particular: it was just convenient to
use for the reply here.)

For those of you who think the IESG should not (or is not allowed to)
exercise judgment here and make a one-time exception for this
exceptional situation:

Please advise how you think we can get the NomCom eligibility question
sorted out IN TIME to seat a 2020-21 NomCom, when we normally need to
ask for volunteers within the next 6 weeks.

Barry

On Fri, Mar 27, 2020 at 7:21 PM Keith Moore <moore@network-heretics.com> wrote:
>
> On 3/27/20 7:15 PM, Pete Resnick wrote:
>
> > For your reading pleasure, here is the Last Call discussion on that
> > statement, so there is precedent:
> >
> > https://mailarchive.ietf.org/arch/search/?qdr=a&email_list=ietf&q=subject%3A(Policy%20Statement%20on%20the%20Day%20Pass%20Experiment)&as=1&so=date
> >
>
> Sure, but there's not a written consensus-approved process to approve an
> IESG statement that's not reflected in an RFC.   And IESG doesn't get to
> dictate how nomcom operates.
>
> >> I am not sure that it's within the IESG's purview to make such policy
> >> statements, especially since nomcom is not an IESG function.
> >
> > The IESG is the consensus caller for BCPs, and the NomCom process is a
> > BCP process, so I can see the argument. Also, the IESG was defining
> > attendance at an IETF meeting, which could arguably be a reasonable
> > thing for the IESG to do.
>
> For other purposes, say whether someone gets a t-shirt, perhaps.   Not
> for nomcom purposes, IMO.
>
> Keith
>
>