Re: NomCom eligibility & IETF 107

"Salz, Rich" <rsalz@akamai.com> Thu, 26 March 2020 13:50 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 2119F3A0984 for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 06:50:21 -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 9ZMyMg5MUSAr for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 06:50:20 -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 E95A63A0C4F for <ietf@ietf.org>; Thu, 26 Mar 2020 06:50:19 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 02QDmPWZ013028; Thu, 26 Mar 2020 13:49:18 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=hT3/lSqya0mjSHhV6h0oHbiID4926pJpFKtAIvRqCRM=; b=fm2NsRG2wbRRqd+69KBrM39AR2snY4ljIc0ok6jxKj21UUuXgzQuXfUCwqGh0+8148Ej 86jXKXud8p5SSEH8gEd93Ug8gaQaS9DYGMaNNYYZnQZZzNopu1gKdYXKP1QXOjz8SLxb 3U1j1a+D2WwsfYTG8vUCXcPafWe2qK7iQNWgj5QQb0uKFx0XtAcmdDSWc3kEM8S4DGWA gJNxXdM21cKD9KMwpE4Oee2lMvgFTDHwyjaqeGZhX9ve4J3qAMeSGhlShR3b41tQxebD tru3jKraBbsr/4rQq/M/J0LNI9ADqioFUrrqnrJCR1LKbqLvcnVLh99j4etMbqv2FxsR Jg==
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 300b9xv1sa-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 26 Mar 2020 13:49:18 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 02QDliJd024428; Thu, 26 Mar 2020 09:49:17 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint3.akamai.com with ESMTP id 2ywe8xp6k2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 26 Mar 2020 09:49:16 -0400
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 26 Mar 2020 09:49:11 -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 09:49:11 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
CC: Barry Leiba <barryleiba@computer.org>
Subject: Re: NomCom eligibility & IETF 107
Thread-Topic: NomCom eligibility & IETF 107
Thread-Index: AQHV+T17YIte9GVOtUSJhAMBWIG3LKhaRrUA///IIwCAAHnogIAAb22A
Date: Thu, 26 Mar 2020 13:49:11 +0000
Message-ID: <AB36354C-7EA1-4160-937E-94998E928276@akamai.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com> <55D8F3C6-7F2A-4382-AFFD-B8A1D7C14992@akamai.com> <f67d1729-6406-a348-eb2f-a459ddb7cca1@gmail.com>
In-Reply-To: <f67d1729-6406-a348-eb2f-a459ddb7cca1@gmail.com>
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: <25D047F3E3C297439760C4DCE6D313F0@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_04: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=523 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2003260107
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.645 definitions=2020-03-26_04:2020-03-26, 2020-03-26 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 spamscore=0 priorityscore=1501 bulkscore=0 mlxscore=0 malwarescore=0 adultscore=0 lowpriorityscore=0 clxscore=1015 suspectscore=0 mlxlogscore=491 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003260106
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m5ex4BMdFov1dbKTRQ3v1VboNBU>
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 13:50:28 -0000

>    I certainly consider this worth discussing, although I don't see why you say "bluesheets on more than one day" rather than "more than one bluesheet." With such a reduced agenda, it could easily happen that a person only considered one day of interest.
  
Yes, it could happen that there's only one day interesting to someone.  I suggested multiple days because I thought it showed a high level of interest or involvement in the IETF and that's what we want for nomcom.  It was an engineering trade-off.
  
As for the details of what needs to be done, should we decide to do this, I leave that to the process-wonks. I was answering the question asked.