AW: NomCom eligibility & IETF 107
N.Leymann@telekom.de Sun, 15 March 2020 09:53 UTC
Return-Path: <N.Leymann@telekom.de>
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 D30503A1353 for <ietf@ietfa.amsl.com>; Sun, 15 Mar 2020 02:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_NONE=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=telekom.de
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 1Cg88KK04eEr for <ietf@ietfa.amsl.com>; Sun, 15 Mar 2020 02:53:01 -0700 (PDT)
Received: from mailout11.telekom.de (mailout11.telekom.de [194.25.225.207]) (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 8F4C53A1351 for <ietf@ietf.org>; Sun, 15 Mar 2020 02:52:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1584265980; x=1615801980; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=jAh4AuEs76dpTChryD4yxmfjnsGGBrucFoHvuJdkH+g=; b=bfcTy+shi9+B+L1KeH5TYBkeZAQ3ZMlqO19S5fb3/P1wmtHcPvFyF5oM DASNU9OjClItmx9Bf4Voh6wtgqf6NePX3Pz7kUpvNaj+rfx1WBsFXIOlA vttlGF3iTlAwBRIpZpW6fIoRkxf+rrF4AI/Hn2eFVecxmPMr5Kn9rR7lI LH6w1+46F5WPceTjQ0ryQJlL6lmbGxPQtpR6Ts8xbYyThB9SF8ICxsQ7r k9dq1yvxn/vuzh3XI3GY8MZNb0XfZkVcK5X8V0+LUEU0DYaZQD26L5pJn pK+LBELCKpgbFNnP3dTZPkemicpykOkvm5+UDl0+sRkcMS8W0gIE6f8ls A==;
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT11.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Mar 2020 10:52:57 +0100
IronPort-SDR: ldVjBC9nwPaKx5oXH3q/IkFiT/iIy8urxbbTRSYNFXhz93aI8CW88VM2K2eQixrOL+kaigzBow 6xt8ocrWaVhKjxdQMtBzrNy8KxMQwlAp8=
X-IronPort-AV: E=Sophos;i="5.70,556,1574118000"; d="scan'208";a="72467446"
X-MGA-submission: MDGUV898DW+hq/nOjx4NK2Mg/Of/emGX1erkZ9mSUY6rQ7xiW5/tRWYtuxNyjJi4ns9R+Y/BJQJVJ/bDOlU8DPiI4fYRlb8HU0Jhk0NhEqn5nPKREB+H6VgzvOTwx5hm6FpQRKopBbDiZd5M2BmoXvF+bBy64L/jNTiuA5cRsgdulw==
Received: from he105864.emea1.cds.t-internal.com ([10.169.119.41]) by qde0ps.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 15 Mar 2020 10:52:58 +0100
Received: from HE199743.EMEA1.cds.t-internal.com (10.169.119.51) by HE105864.emea1.cds.t-internal.com (10.169.119.41) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 15 Mar 2020 10:52:57 +0100
Received: from HE104163.emea1.cds.t-internal.com (10.171.40.38) by HE199743.EMEA1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Sun, 15 Mar 2020 10:52:57 +0100
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.18) by O365mail05.telekom.de (172.30.0.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 15 Mar 2020 10:52:35 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AfhQ5gVTQBwtHBYjBi/XO1TVNj20wmPBEwsQqjq2f70Fq42O9Z3N0BrzxuoegK1Hqe6eolKfU24g1ODop8Yf5Cji6DzIKxvH85W8U4ztjslSAwzacj6Ibew/eyuB2Zn8qrYZpY2KeaK3i+4vnsi48ZmEWCrH6kLWrZ4F7ryEocG7TlruwPnH55yRwT4rnLF8QC3Wastny9NMIUm4M7HQ3ZOPKG66d4FnLfZJe9btdl3yEJBSdOba89uAlV05+GH/0sYzrOs7JWPrm/2Hj029RABfWXoE3QauVwp46gNvbWJJHqDIW3p42RIPF+vFe0wIdIOht0LwtJcLetL1HCQ0sw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=jAh4AuEs76dpTChryD4yxmfjnsGGBrucFoHvuJdkH+g=; b=NsZVjw2kaSs4TmvOgIcIhuWhiw+u2z+O62FHieVKSKKBgaIbrLJejwlkZaq54M3UEjudftHzwmlnjCDThwrEzMyPG401Sm9WzxLriLfM7uR3i+rIMPmDh8FjtJh9e6SL3FuBLXGOb09pdG7ALs5/p3Yd2aJdwr8CqDVEs5YmxlhaNpSCmW/QuQ05R06/BVocoN4dizeBmRMdCyOKhD+jOi0wKyU8H31H3eZbHujAfBV0rwnF583Ba/3EVtfOjIzOepKIPc2Cy0o9wTbA07OWd6ZF/chUrn/E25JQOwJ/eJ7zkUE1lJ63VI5NB406xxJthE/gCQw15+ZAC4iMvmc8Lg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from FRAPR01MB0642.DEUPRD01.PROD.OUTLOOK.DE (10.158.134.19) by FRAPR01MB0002.DEUPRD01.PROD.OUTLOOK.DE (10.158.130.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2814.21; Sun, 15 Mar 2020 09:52:35 +0000
Received: from FRAPR01MB0642.DEUPRD01.PROD.OUTLOOK.DE ([fe80::b541:9649:491b:2ed6]) by FRAPR01MB0642.DEUPRD01.PROD.OUTLOOK.DE ([fe80::b541:9649:491b:2ed6%3]) with mapi id 15.20.2814.021; Sun, 15 Mar 2020 09:52:35 +0000
From: N.Leymann@telekom.de
To: barryleiba@computer.org, ietf@ietf.org
Subject: AW: NomCom eligibility & IETF 107
Thread-Topic: NomCom eligibility & IETF 107
Thread-Index: AQHV+T2V82p5ZPCMDUaNbbTfyj4cVahJa/2A
Date: Sun, 15 Mar 2020 09:52:34 +0000
Message-ID: <FRAPR01MB06425EB4B000DE17B79C56A398F80@FRAPR01MB0642.DEUPRD01.PROD.OUTLOOK.DE>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com>
In-Reply-To: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=N.Leymann@telekom.de;
x-originating-ip: [164.19.3.55]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bd2f016b-627a-44cd-9df6-08d7c8c69692
x-ms-traffictypediagnostic: FRAPR01MB0002:
x-microsoft-antispam-prvs: <FRAPR01MB00026D478B8C018950612B1198F80@FRAPR01MB0002.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0343AC1D30
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(366004)(376002)(396003)(136003)(199004)(110136005)(5660300002)(26005)(316002)(186003)(8676002)(71200400001)(7696005)(81156014)(81166006)(9686003)(55016002)(8936002)(478600001)(66946007)(2906002)(33656002)(66446008)(86362001)(66476007)(66556008)(64756008)(76116006)(66574012); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0002; H:FRAPR01MB0642.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: u9MOj7mUZCFek7NxqotRK71MO6GOKYvgKDIm+0i/rzTsjX0SDUyL74Kd6/xm1SIgQkZ+8uroI/v1Ep6hMUEaeITZBko0LfYNW+tXy0lG5zt3JwAkUIPjH3IsRW25LfuCQowcNuAflLbPqIfgBL9oIfvjnatjuLVlOz0wELAIxsdN8tduKBZ0zLP8Z64sjuj6o1SeCjxe8m4aBN60bSlNwLJ34HpWx1E2H5Wpyl/hMpsDKhBea/mYdbF2jekLIgcpXBxyg6rxX/y0vESMs8x0v+XJdV/N8XtoOlH2TIG4xXDfiwDrGmMNhkJXulnQyFWHR4o85YqH2Ot7Rl3IyZbff/C7DnCXa//ixt/Y8bN319bvtC2wiR61Sxht/4AT/+9qcAvnkLzvCzrSyxRc2QjsRuF2QQTCffCR8ZAzj7z1qH1WcVXeZfCDHOB9PrZReZsX
x-ms-exchange-antispam-messagedata: zke+j5wdB2i3UGy1fwsZcXw3wL48YGrsAMF2fc9N0iqpgatRgY5UPXlBI3I6dLKRjP6YnmUVFTo9hq+GDaev9BR+NkEpDvHdBvbTDjqSFz3YetnrVFIq4kpFlnNTpM7HP3YvZQrJbVuyxTHLyw92NQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bd2f016b-627a-44cd-9df6-08d7c8c69692
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Mar 2020 09:52:35.0835 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4r6FDoTYi+seuyvSqlPjsl0ZKdcHRwJYnN0BBAtmIcEDzATvUOQR4QKLcqIIwxJw3wEAMwayrzQkH2Y0ydYP/A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0002
X-TM-SNTS-SMTP: AECD6C44AFC074203D4615CABC69E1081FDC8AB410BE7C50BA3B153E2245A0632000:8
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SVgbN50rLTosrbPUymDlcQH9E8A>
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: Sun, 15 Mar 2020 09:53:03 -0000
Hi, Entirely ignore IETF107 and count the last five meetings before. regards Nic -----Ursprüngliche Nachricht----- Von: ietf <ietf-bounces@ietf.org> Im Auftrag von Barry Leiba Gesendet: Freitag, 13. März 2020 14:44 An: IETF discussion list <ietf@ietf.org> Betreff: NomCom eligibility & IETF 107 The cancellation of the in-person IETF 107 meeting raises the issue of how that meeting affects NomCom (Nominating Committee) eligibility. This is especially important because a new NomCom will be formed between now and IETF 108, giving us all a fairly short time to figure out what to do. For convenient reference, the current rules for an IETF participant to be eligible to be a voting member of a NomCom (Section 4.14 of RFC 8713) require attendance in person at three of the last five meetings. Normally, for the upcoming NomCom, that would mean three of the following five meetings: 107 (Vancouver), 106 (Singapore), 105 (Montréal), 104 (Prague), 103 (Bangkok). A new participant who had been to 105 and 106 would become eligible by attending 107. An occasional participant who had been to 103 and 105 would also become eligible by attending 107. On the other side, someone who had attended 102, 104, and 105 would lose eligibility by NOT attending 107. The IESG would like the community’s input: How do *you* think 107 should be treated in regards to NomCom eligibility? While we have time to come up with a longer-term answer for this as a general matter, we need to make a one-time decision about how to handle 107 now, before this year’s NomCom is formed. One choice is to entirely ignore 107 for the purposes of NomCom eligibility. The last five meetings would then be 106, 105, 104, 103, and 102, and one would have had to attend three of those to be eligible this year. Another choice is to consider 107 to be a meeting that everyone has attended, for the purpose of NomCom eligibility. There, the last five would still be 107 to 103, but 107 would be an automatic “yes” for anyone who volunteers for the NomCom. Perhaps there are other workable options. Please let us know what you think by responding to this message thread. And to be absolutely clear: whatever we, as a community, decide now, with fairly short lead time, is for the 2020-2021 NomCom cycle only. Any longer-term decisions might be different and will need to be done through a more formal, consensus-based process, which we also hope to initiate in the near future. Thanks in advance for the discussion we’re sure to have on this. Barry, for the IESG
- NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Lars Eggert
- RE: NomCom eligibility & IETF 107 Daniele Ceccarelli
- Re: NomCom eligibility & IETF 107 Mary B
- Re: NomCom eligibility & IETF 107 Russ Housley
- Re: NomCom eligibility & IETF 107 Carsten Bormann
- Re: NomCom eligibility & IETF 107 Russ Housley
- Re: NomCom eligibility & IETF 107 Paul Wouters
- Re: NomCom eligibility & IETF 107 Lars Eggert
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Eric Rescorla
- Re: NomCom eligibility & IETF 107 Stephen Farrell
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Alexandre Petrescu
- Re: NomCom eligibility & IETF 107 Carsten Bormann
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Forced virtual IETF 109 as well as 107 (was: Re: … John C Klensin
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Bob Hinden
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Lars Eggert
- Re: NomCom eligibility & IETF 107 Paul Hoffman
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Toerless Eckert
- Re: NomCom eligibility & IETF 107 Vittorio Bertola
- Re: NomCom eligibility & IETF 107 Michael StJohns
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Randy Bush
- Re: Forced virtual IETF 109 as well as 107 (was: … tom petch
- Re: Forced virtual IETF 109 as well as 107 Alexandre Petrescu
- Re: Forced virtual IETF 109 as well as 107 Brian E Carpenter
- RE: NomCom eligibility & IETF 107 Eric Gray
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: Forced virtual IETF 109 as well as 107 Phillip Hallam-Baker
- Re: NomCom eligibility & IETF 107 Job Snijders
- Re: NomCom eligibility & IETF 107 Randy Bush
- Re: NomCom eligibility & IETF 107 Andrew G. Malis
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Victor Kuarsingh
- Re: NomCom eligibility & IETF 107 S Moonesamy
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Stewart Bryant
- Re: NomCom eligibility & IETF 107 Stewart Bryant
- Re: NomCom eligibility & IETF 107 Phillip Hallam-Baker
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: Forced virtual IETF 109 as well as 107 S Moonesamy
- Re: NomCom eligibility & IETF 107 Cullen Jennings
- AW: NomCom eligibility & IETF 107 N.Leymann
- Re: NomCom eligibility & IETF 107 Jay Daley
- Re: NomCom eligibility & IETF 107 Jim Fenton
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: Forced virtual IETF 109 as well as 107 Alexandre Petrescu
- Re: Forced virtual IETF 109 as well as 107 S Moonesamy
- Venue for post-IETF 107 Nomcom eligibility discus… Spencer Dawkins at IETF
- Re: Venue for post-IETF 107 Nomcom eligibility di… Samuel Weiler
- Re: Venue for post-IETF 107 Nomcom eligibility di… Alissa Cooper
- Re: Venue for post-IETF 107 Nomcom eligibility di… Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 tom petch
- Re: NomCom eligibility & IETF 107 Lou Berger
- Re: NomCom eligibility & IETF 107 Loa Andersson
- Re: NomCom eligibility & IETF 107 Christian Hopps
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Bob Hinden
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 John C Klensin
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Michael StJohns
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Donald Eastlake
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Jared Mauch
- Re: NomCom eligibility & IETF 107 Stewart Bryant
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Lars Eggert
- RE: NomCom eligibility & IETF 107 Scott Mansfield
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Abdussalam Baryun
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Behcet Sarikaya
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Alissa Cooper
- Re: NomCom eligibility & IETF 107 Yoav Nir
- Re: NomCom eligibility & IETF 107 Michael StJohns
- Re: NomCom eligibility & IETF 107 Richard Barnes
- Re: NomCom eligibility & IETF 107 Victor Kuarsingh
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Robert Elz
- Re: NomCom eligibility & IETF 107 Victor Kuarsingh
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 Spencer Dawkins at IETF
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Michael Richardson
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Joel Halpern
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Salz, Rich
- Re: NomCom eligibility & IETF 107 Behcet Sarikaya
- Re: NomCom eligibility & IETF 107 Keith Moore
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 Bob Hinden
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Barry Leiba
- Re: NomCom eligibility & IETF 107 John Levine
- Re: NomCom eligibility & IETF 107 Pete Resnick
- Re: NomCom eligibility & IETF 107 Brian E Carpenter
- Re: NomCom eligibility & IETF 107 Nico Williams
- Re: NomCom eligibility & IETF 107 Abdussalam Baryun
- Re: NomCom eligibility & IETF 107 John C Klensin