Re: NomCom eligibility & IETF 107

Nico Williams <nico@cryptonector.com> Thu, 02 April 2020 21:45 UTC

Return-Path: <nico@cryptonector.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 9ADCE3A099A for <ietf@ietfa.amsl.com>; Thu, 2 Apr 2020 14:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 P-IRJY1j-ZWL for <ietf@ietfa.amsl.com>; Thu, 2 Apr 2020 14:45:33 -0700 (PDT)
Received: from blue.elm.relay.mailchannels.net (blue.elm.relay.mailchannels.net [23.83.212.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51ED03A088F for <ietf@ietf.org>; Thu, 2 Apr 2020 14:45:33 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 892F6480A76; Thu, 2 Apr 2020 21:45:32 +0000 (UTC)
Received: from pdx1-sub0-mail-a10.g.dreamhost.com (100-96-10-8.trex.outbound.svc.cluster.local [100.96.10.8]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 169EE4809A8; Thu, 2 Apr 2020 21:45:32 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a10.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.6); Thu, 02 Apr 2020 21:45:32 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Shade-Abaft: 70ec52933adb66fa_1585863932336_2194264581
X-MC-Loop-Signature: 1585863932336:2647177654
X-MC-Ingress-Time: 1585863932336
Received: from pdx1-sub0-mail-a10.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a10.g.dreamhost.com (Postfix) with ESMTP id AE153B1BAB; Thu, 2 Apr 2020 14:45:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=WWV/ZyEg34qOa0 UzQ5FYolS3t5Y=; b=LiEz7xGXZI4viEzrbUT5WgH0uSbzX7/IJirtPd7ZkvhN2E 0Xg55xgP/StAjIqO5QmQHCxQss5kttf+2bnKr83PPkGeELgiKK31KNKSTNQAVX8Z F8TV1j9V65yA38Ko9gB2qHrVH656zaX7W0H7iI6tdaJPMkniW3FZnPvyEI8KA=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a10.g.dreamhost.com (Postfix) with ESMTPSA id A372CB1B98; Thu, 2 Apr 2020 14:45:29 -0700 (PDT)
Date: Thu, 2 Apr 2020 16:45:26 -0500
X-DH-BACKEND: pdx1-sub0-mail-a10
From: Nico Williams <nico@cryptonector.com>
To: Pete Resnick <resnick@episteme.net>
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: NomCom eligibility & IETF 107
Message-ID: <20200402214525.GZ18021@localhost>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVBy7iVT4NVLw14+=a1ksWrg35q+dsKfs+9r2poiVo3wkg@mail.gmail.com> <0FC773BE-7B20-402C-AC7E-183A321741E0@gmail.com> <CAC4RtVBjTjOWLMTFvM50DR2piOLQ4jniXTWPunOoMfvdkOzvXw@mail.gmail.com> <r659rd$2vv1$1@gal.iecc.com> <9910E0CF-138A-40B0-B432-3E4BD692E6EE@episteme.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9910E0CF-138A-40B0-B432-3E4BD692E6EE@episteme.net>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrtdehgddtudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZN_F6Ey3tPGSLsvBEyScW6ypPeQ>
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: Thu, 02 Apr 2020 21:45:35 -0000

Regarding whether this updates or is part of BCP 10, the best reason to
do it is to make it possible to observe this via the various tools and
search engines.  Even long after this crisis is over, the fact that this
happened can prove useful a) to scholars, b) if a new crisis should come
up it will show how we handled it this time.  (b) is not the same as
setting precedent, though it could effectively set precedent in a way,
and not listing this as an update or part of BCP doesn't preclude
setting precedent.