Re: NomCom eligibility & IETF 107

"Salz, Rich" <rsalz@akamai.com> Thu, 26 March 2020 15:45 UTC

Return-Path: <rsalz@akamai.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 709A93A0CBE for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 08:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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 (2048-bit key) header.d=akamai.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 XcMH32OfuiYY for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 08:45:55 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [67.231.149.131]) (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 2470D3A0D6B for <ietf@ietf.org>; Thu, 26 Mar 2020 08:45:55 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 02QFil3u024869; Thu, 26 Mar 2020 15:44:52 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=zSAX1yz3AmpnAXOsCvF54Y3mcfMqTsHdr6yBroU2Fvc=; b=RGcqDLGyvedxYkrB5MW5408Hyp4OXxGyCj7q29Z6h4DxlOJVyrXqzn9Q5llUi0hKgzds sYk9ze1MBN5JaE6ZbLNUz3CEVzhqCXOpRe8PEcF08b/X4U4c2c6p9nEXluA7w1SkFAGc UU8uK839K9dn8iTTTdtUGBFXNEaqAM3XZU/au2xCvhbmDvF6A8h0cehpigEeaHt6jnOv p//ZCKQ1P8f47yVRlXP45LgLKSXsW1tPKCagNsZwrFgczJzKkamdGPHIz/0DUHh17Jxo /gv5b6RrjduYE//G4jKSn7YZqyV6bqsFNzGkD0pCKrnwyQyDDisRepHOXNkg0vwx3z4v OA==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2yytab0b7e-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 26 Mar 2020 15:44:51 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 02QFWFJD011619; Thu, 26 Mar 2020 11:44:50 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint2.akamai.com with ESMTP id 2ywe8uj0ef-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 26 Mar 2020 11:44:50 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 26 Mar 2020 11:44:49 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1497.006; Thu, 26 Mar 2020 11:44:49 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: John C Klensin <john-ietf@jck.com>, tom petch <daedulus@btconnect.com>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: NomCom eligibility & IETF 107
Thread-Topic: NomCom eligibility & IETF 107
Thread-Index: AQHV+T17YIte9GVOtUSJhAMBWIG3LKhaRrUAgAC7yYCAAFgoAP//vdWA
Date: Thu, 26 Mar 2020 15:44:49 +0000
Message-ID: <5AB65F13-CE41-47B9-9B81-365621858F14@akamai.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <1UW64HHr2j.1YlDGqDnLsi@pc8xp> <9CED509420B008E8494332F1@PSB>
In-Reply-To: <9CED509420B008E8494332F1@PSB>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.118.63]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F61D337067F9C247ACFAC9E92C7821D7@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.645 definitions=2020-03-26_06:2020-03-26, 2020-03-26 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=869 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2003260120
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.645 definitions=2020-03-26_07:2020-03-26, 2020-03-26 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 adultscore=0 clxscore=1011 phishscore=0 impostorscore=0 mlxscore=0 bulkscore=0 spamscore=0 priorityscore=1501 suspectscore=0 malwarescore=0 mlxlogscore=853 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003260121
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5AMP2mV5E3yv_kVOcO3LjXh9nxU>
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, 26 Mar 2020 15:45:59 -0000

> I
    continue to worry that we can't say "107 was not a meeting" for
    Nomcom selection purposes and then turn around and say "107 was
    the First Meeting of the year" for Nomcom selection purposes and
    the rest of the timeline.  
  
I agree.  And it may be that that particular ship has sailed, since the new IAB and IESG were introduced via webex last night.