Re: NomCom eligibility & IETF 107

Stewart Bryant <> Thu, 26 March 2020 20:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9D7963A08BE for <>; Thu, 26 Mar 2020 13:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.507
X-Spam-Status: No, score=-0.507 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bTKrGKRSNd7u for <>; Thu, 26 Mar 2020 13:11:41 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0A3913A0786 for <>; Thu, 26 Mar 2020 13:11:41 -0700 (PDT)
Received: by with SMTP id g62so8987205wme.1 for <>; Thu, 26 Mar 2020 13:11:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4dNnkV8QIz0WeTtj9aK5x6l1Zz/VnRvt1oMnS60lP9M=; b=bOVAXVkzLKtKHJBocUoOJD1n1OT9Ejvdqg+1LmjMMiX15zYevCfnrCZJhWZ0EqULt0 e5G5gDWkKDRS9IQczsxfhgiy+S3Yr3IRzggZxr/BszzJMx0rXxyRlmEjLsGitu+rbJQs BlYBnlnmhRzaf1Ib26A08ACWAYVuyZw2/s4hkU9CsEuoZYvRpaB5VDwf13+ugM92zi7f 5mG+P/pxhrXH3XJqBgsBK0HdQHg5d4aSNFRJWyVqLJlhSYNXQ4gKc6rcAd/xad2hPB78 tWEb+W9FHG9bajg7H0+9deneq7uhtAgYmMhQutpIetpJ5jYbwzH0sFdglRoWF3WD4XmS mi9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4dNnkV8QIz0WeTtj9aK5x6l1Zz/VnRvt1oMnS60lP9M=; b=O4Sg8upsDLNP35SdCKIFkbZDpMahhVh02aNyCi2jC4BBaAfx8NfBBL4tCad1ZJMUBq RLxzcSccshSdojYukBm6YQJV7ulVgqtR8TJifuHE0KtFNvN8IV+pIdxyFoUEeXDDAuaa 6RghU1n6GBlOyGSVGSCq68XpX/yz22QUUmnJVQkjImqSGk9aiNIMLSm1/7a0aezWosR3 JC0zizACPeHC9fyPtlRRZd36KoNEte9v5OUGt/gFKIrUDLsV3xU//Oug8QXL/FvLi3mV 2Pk2u6Jvr+rQ+ZnR8+iLRobySOSU09drSCXgvYOR2r126HuDPjQez+IKJmNHsIxyxs3t kEFg==
X-Gm-Message-State: ANhLgQ3KA7c9J2fbOk50CUARUuyQ9DskVwF7bwpBFPKv7zo1XF8193mo How57jnNKzXWD+Ow7uzatSc=
X-Google-Smtp-Source: ADFU+vtBD04u6YlWgzdBfUfPj6EG3v0woF6l498Gj/W1NcII76zKKRKA3A13eF456b7p0/2BYksylA==
X-Received: by 2002:adf:9465:: with SMTP id 92mr11170352wrq.122.1585253499472; Thu, 26 Mar 2020 13:11:39 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id 9sm4744000wmm.6.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Mar 2020 13:11:38 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
Subject: Re: NomCom eligibility & IETF 107
From: Stewart Bryant <>
In-Reply-To: <>
Date: Thu, 26 Mar 2020 15:01:22 +0000
Cc: Stewart Bryant <>, IETF discussion list <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Barry Leiba <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Mar 2020 20:11:43 -0000

What worries me is how someone that has not been to a IETF a few times can be I a position to understand how it works and the nuances of the information that are presented. Also in person presence shows a level of commitment to the organisation which is essential to fulfil the Nomcom duties.

The criteria were set for a reason and we should abide by that rationale. For that reason I would prefer that the criteria be remained at three recent physical meetings as it currently is.

If, as is likely, we end up with a virtual meeting in Summer we can think again, but for now we should stick with the original criteria of 3/5 in person meetings.

- Stewart