[6tisch] Fwd: Nomcom 2020-2021 Second Call For Volunteers

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 11 June 2020 07:01 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E8E3A0888; Thu, 11 Jun 2020 00:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=NhRk/H8Z; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=LGoILqF3
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 2UQSi_CF0sNn; Thu, 11 Jun 2020 00:01:12 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34CC83A1753; Thu, 11 Jun 2020 00:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26541; q=dns/txt; s=iport; t=1591858872; x=1593068472; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=eYLcs/Gc8Xx/zdGDiSTBArsIbH6dZJmx8eCYcgBNKoI=; b=NhRk/H8ZMiMeZVIrFW02TsC43nIRnJZWxbSMh1oY7CQ7lJ0RshA7JrLV frhmF2a8e2W0R0QtPLlSGfov59HnZNQ3C0XJ4t3uB8NPamarAXnbzCarr VshIQu3kHZ6eeYdq2RYThkJDDJhAPIpEvzPZ7ftpJq5VNTIkDbgeE4uyC 4=;
IronPort-PHdr: =?us-ascii?q?9a23=3AHh9r+hTP5iwKBc8ImA+WQ8xpqdpsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESQBN+J6v9YhazRqa+zEWAD4JPUtncEfdQMUh?= =?us-ascii?q?IekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsutZlDOrDu19zFBUh?= =?us-ascii?q?n6PBB+c+LyHIOahs+r1ue0rpvUZQgAhDe0bb5oahusqgCEvcgNiowkIaE0mR?= =?us-ascii?q?Y=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CEBwCa1eFe/5ldJa1VERwBAQEBAQE?= =?us-ascii?q?HAQESAQEEBAEBggqBUiMvB29YLyyEJINGA40UJYEBiH6Ja4RogUKBEANVCwE?= =?us-ascii?q?BAQwBARgBBwkEAgQBAYREAheCBwIkOBMCAwEBCwEBBQEBAQIBBgRthVsMhXI?= =?us-ascii?q?BAgEDAQEQCwYdAQEkAgYMDwIBGQMBAisCAgIfBgsbAggCBAESFA6DBAGBfk0?= =?us-ascii?q?DLgEOp38CgTmIYXaBMoMBAQEFRAJsAYEWgk4NC4EjawMGgTiCZIJIghOBZ4M?= =?us-ascii?q?lGoFBP4ERJwwQgU9JBy4+gQQBgRlJAQECGoEUARIBOAmCdDOCLYsBg3ELEoM?= =?us-ascii?q?OhjUlinqPUSRMCoJZiDuGHoRwZYIIgl0DHYJuiRaOMYQjkRKBYogmglGRSAI?= =?us-ascii?q?EAgQFAg4BAQWBaiJmcHAVOyoBgj5QFwINjh4MDAuDToUUhUJ0AgEBEyACBgE?= =?us-ascii?q?HAQEDCXyMRwSBYWABAQ?=
X-IronPort-AV: E=Sophos;i="5.73,498,1583193600"; d="scan'208,217";a="511332948"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 11 Jun 2020 07:01:08 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 05B718b2021564 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 11 Jun 2020 07:01:08 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 11 Jun 2020 02:01:07 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 11 Jun 2020 03:01:06 -0400
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 11 Jun 2020 02:01:06 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OwB4YSESPQ0E1TJQEG4mw4zeko1aVQjgf3uvkc5q4azjHZQpruR1Rn90GrFPjSqCxTcDHaKST1cwwGmf00im7vT/i7tep2ZOex1XNIVp6JWma0ZXNl05uGkieahINAaAltAp7kQOEL44wYAA/e5G7K21RUwfd0MI4iTUKy1RRRAD/J+VYcWL9+dh6b9TqTp15HFwBmTtp4AdTf/hDEABSVnKVAINyIq88nNuvlGSqxak22jpm/YKHe9bET6WH87CeDUxm6nKg2wrAkunoW3/GT7DKkmRzt1O+qbRQyy4acKIvy9NufMJeGQ+p3qmkzz5D7fhjmDXX9st1QtsfN9ueQ==
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=eYLcs/Gc8Xx/zdGDiSTBArsIbH6dZJmx8eCYcgBNKoI=; b=A1QyfJGPHo3ehn18Xc0aWmrggru8QJNfzEhSyLBri/KLkhLdnWttHV8zpxMTE2Y5mXwalCh4eaD7k79VYYFO0ijdXtyNTPQ77PSx00cR/xq9iuw1TSrvedQczOQOuqnQzw7J9nYfkQfgoFKa/GnUiwM7/JRnO6CiaXefFGbpIwr69YrupgOh3RAUGTxCgFv6+u54jrBlIO6SH22wliaoCdjGm8QP38FMxSb2ObbtUdz/z5Sh9qUbBMGk/ovbgxgQ4Q8AFuU72oZemFQxCYzYPC5tJZFquqOZ9oOQOzvmxumnctFOsaj+SN4QM8Ai6gvh4BGhRIFcV/OORCiIMZanwQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=eYLcs/Gc8Xx/zdGDiSTBArsIbH6dZJmx8eCYcgBNKoI=; b=LGoILqF3ljINxjzJEzvKjZ8sCZZyke1ntzHNp/hTRH7c/y931ZWjjWIeFSrudNZ9frIDT5RhY3GrKPvEgdQLCSBg4cxmoKTvRjDiP24sQtmh/65pgJCEztlRkgi31GJpxItALoIr5we2i9TB3yM5T3FOjckI7ESGhXCzGhXTmZ4=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (2603:10b6:208:ea::31) by MN2PR11MB3934.namprd11.prod.outlook.com (2603:10b6:208:152::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3088.18; Thu, 11 Jun 2020 07:01:01 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::55bb:b065:86c1:1108]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::55bb:b065:86c1:1108%6]) with mapi id 15.20.3088.019; Thu, 11 Jun 2020 07:01:01 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: lp-wan <lp-wan@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: Nomcom 2020-2021 Second Call For Volunteers
Thread-Index: AQHWP74QSY6xEvJOTUOdLF6G/Dg9fg==
Date: Thu, 11 Jun 2020 07:01:00 +0000
Message-ID: <0A630EF8-2185-423F-A3CB-27C52847F079@cisco.com>
References: <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com>, <2F36E15D-AE39-48BA-86AA-C33607B57035@gmail.com>
In-Reply-To: <2F36E15D-AE39-48BA-86AA-C33607B57035@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb1d:4ec:2200:f09d:fc2f:e57e:3fc8]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: da8165c2-239f-4671-51d8-08d80dd53341
x-ms-traffictypediagnostic: MN2PR11MB3934:
x-microsoft-antispam-prvs: <MN2PR11MB3934F17D58CBA9497F86A363D8800@MN2PR11MB3934.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5516;
x-forefront-prvs: 0431F981D8
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: sFYQ6ZuZKpffuH3o3BLRzF7V5gpQBQu4riD06b6fMSjW74PCeEqOicvBmChJfGp9Ys8PJM/lcQL8O5iTqWY7z7v+KsRFdXfEL8ksqEr8pQUa4i3LRwSi8xn6XlHTHmyxZXOnmvtqZhpSImlH1AvafnywSKnV4529XoLZL3v9WGmQXIv0UxKtx50jOKFqAUNDoL7VtSRuH7qtjZLbFsfbdJMMlZyW4bVs0ol/YcGF9tGS01m9312j5Xy0MluxG4RqpxDTokSemvjpwHeMgmTWAEBNG3heiAKVROUvS5/Cw9p+cMbr42cpsc412EGXyYh57+SU+rBWdZJ/9UhoHVIJjJBd4dy0ivln+kMWezg7c5y6e8/J1BS6fNrSh4zYaUvPr0rG/6jAegFZeOQSnskx439LUXIKNGkE7jBVrtIi/GNR5xbgc2Ctb7Iru/RfmMZP6wt/AtTtvZWJwzoFC4oGJg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB3565.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(396003)(366004)(136003)(346002)(39860400002)(376002)(2616005)(5660300002)(8936002)(478600001)(86362001)(53546011)(316002)(110136005)(186003)(66574014)(966005)(450100002)(33656002)(6512007)(66446008)(6486002)(83380400001)(66476007)(36756003)(2906002)(66556008)(64756008)(66946007)(6506007)(76116006)(91956017)(71200400001)(8676002)(244885003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: q8kgovGPDu3mBlz3X4thdos3MpnHyBk/YKKh5nxOy7UeV52UF2pQJuPFqRK+5pS2EH5gXaDruzuvYTc+P0cSWzqNU/Xli7Z4pLUmZDz1d9x9Qz4wZTtk3G1VZ+SlxzN41YgSU40gCAHXb27f4jcyLOiMUzxfP0IrY+09CbDVwYfFGXfeJogGqS0DKYmsHgzVINhOT7X3otCmZJImKyDqDWLb5+b4sgYkWlqAdORYF5NAXRcCqC6JzEn93aqCV+RZBJYy4+fFLJ1UgHq1tZR0N0VCor7tJmb4kMSR/Q0tNK8EagEl8uwycebH6zKaaovQ6a0Z1X1eZx82Y4uqDnnEOSc4gUxDv3gf9AeHFEklPoe1qcc3mtRNBSxWqvdsTJBoKKSzdHh+pZskPrqgHXSJeFtEPqpK5Iu5qaaeeYMMgzQVictikGYv5chcv7Ikm9d8iuTFT29k3K2BQ7tYQLnumAgFM9lHrOtOLz45BT0NxYDgo8pc6hgZiongTSN0kYasIKQPpDiYHRrUZZVK1EyLbfRl8ZUVW+KTrxcMOxFT/Oi8SzMtDw9L7BNXKQxy0xQT
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_0A630EF82185423FA3CB27C52847F079ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: da8165c2-239f-4671-51d8-08d80dd53341
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jun 2020 07:01:00.8451 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2mqSrICsuRIZ7mQ5dZudEgHddStw920NPF3SGhkdKZKSYQO6girIcYCoW9lZdRWST9eOAMG8AGSXvPFlUmYd3A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3934
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/ADoQAryCKD4xkJX7H3LaGAJiB14>
Subject: [6tisch] Fwd: Nomcom 2020-2021 Second Call For Volunteers
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jun 2020 07:01:15 -0000

As Fred says... non-com is a foundation of the IETF open and diverse activities.

Please volunteer if you can...

Pascal

Expéditeur: Fred Baker <fredbaker.ietf@gmail.com>
Date: 11 juin 2020 à 00:02:17 UTC+2
Destinataire: IPv6 Operations <v6ops@ietf.org>
Objet: [v6ops] Fwd: Nomcom 2020-2021 Second Call For Volunteers

 Folks: the nomcom chair asked that you volunteer to serve on the nomcom. I would ask that, and ask that you also be willing to serve in management roles in the IETF. If there’s something you wish were different, it would be your chance to change it.

Sent from my iPad

Begin forwarded message:

From: NomCom Chair 2020 <nomcom-chair-2020@ietf.org>
Date: June 10, 2020 at 1:55:21 PM CDT
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Nomcom 2020-2021 Second Call For Volunteers

This is the second sending of the call for volunteers for the 2020-2021 NomCom.

I wanted to mention a few updates from the previous email (sent 2 weeks ago):
- I've fixed the URL at the bottom of the email to point to https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_nomcom_2020_&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=ZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=NgIu-7Ij0nEdsFcbJOLcl2M56RxyREhLAtcaHLatD34&e=  instead of /2019/. This was a test to see if anyone was paying attention. Apparently, some people were. ;)
- The IETF 108 registration form includes a checkbox that will let you volunteer. You can use this instead of emailing me, when you register for IETF 108.
- I currently have 39 volunteers. Last year had 149. I need more volunteers!
---------------------------------------------------------------------------------
The IETF NomCom appoints people to fill the open slots on the LLC, IETF Trust, the IAB, and the IESG.

Ten voting members for the NomCom are selected in a verifiably random way from a pool of volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population.

The details of the operation of the NomCom can be found in BCP 10 (RFC 8713). RFC 3797 details the selection algorithm.

Special for this year (and only this year), we also have RFC 8788 (one-off update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer:

     Members of the IETF community must have attended at least three of
     the last five in-person IETF meetings in order to volunteer.

     The five meetings are the five most recent in-person meetings that
     ended prior to the date on which the solicitation for NomCom
     volunteers was submitted for distribution to the IETF community.
     Because no IETF 107 in-person meeting was held, for the 2020-2021
     Nominating Committee those five meetings are IETFs
       102 [Montreal, Canada; July 2018],
       103 [Bangkok, Thailand; November 2018],
       104 [Prague, Czech Republic; March 2019],
       105 [Montreal, Canada; July 2019], and
       106 [Singapore; November 2019].

Keep in mind that eligibility is based on in-person attendance at the five listed meetings. You can check your eligibility at: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_registration_nomcom.py&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=ZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=7_9x9PPoUIajJs2AnUFYg0KnEg8gkD3Jnwf1v079EQo&e= .

If you qualify, please volunteer. Before you decide to volunteer, please remember that anyone appointed to this NomCom will not be considered as a candidate for any of the positions that the 2020 - 2021 NomCom is responsible for filling.

People commonly volunteer by ticking the box on IETF registration forms. The IETF 106 form did not ask whether people were willing to volunteer. IETF 107 did ask, but all those registrations were canceled. I have asked the Secretariat if it is possible to get the list if volunteers from canceled IETF 107 registrations. If that list is available, I will contact all who are verified as eligible. But given the uncertainty of this process, I would encourage people to volunteer directly (see the bottom of this email for instructions). Thank you for volunteering!

The list of people and posts whose terms end with the March 2021 IETF meeting, and thus the positions for which this NomCom is responsible, are

IETF Trust:
   Joel Halpern

LLC:
   Maja Andjelkovic

IAB:
   Jari Arkko
   Jeff Tantsura
   Mark Nottingham
   Stephen Farrell
   Wes Hardaker
   Zhenbin Li

IESG:
   Alissa Cooper, IETF Chair/GEN AD
   Alvaro Retana, RTG AD
   Barry Leiba, ART AD
   Deborah Brungard, RTG AD
   Éric Vyncke, INT AD
   Magnus Westerlund, TSV AD
   Roman Danyliw, SEC AD
   Warren Kumari, OPS AD

All appointments are for 2 years. The Routing area has 3 ADs and the General area has 1; all other areas have 2 ADs. Thus, all areas (that have more than one AD) have at least one continuing AD.

The primary activity for this NomCom will begin in July 2020 and should be completed in January 2021.  The NomCom will have regularly scheduled conference calls to ensure progress. There will be activities to collect requirements from the community, review candidate questionnaires, review feedback from community members about candidates, and talk to candidates.

While being a NomCom member does require some time commitment it is also a very rewarding experience.

As a member of the NomCom it is very important that you be willing and able to attend either videoconference or in-person meetings (which may not happen) during 14-20 November (IETF 109 - Bangkok) to conduct interviews. Videoconference attendance will be supported whether or not there are in-person meetings. Orientation and setting of the NomCom schedule will be done by videoconference during the week 20-24 July (exact time and date to be determined after NomCom membership is finalized on July 12), the week prior to IETF 108.  Being at IETF 110 (Prague) is not essential.

Please volunteer by sending me an email before 23:59 UTC June 24, 2020, as follows:

To: nomcom-chair-2020@ietf.org
Subject: NomCom 2020-21 Volunteer

Please include the following information in the email body:

Your Full Name:
   // as you write it on the IETF registration form

Current Primary Affiliation:
   // Typically what goes in the Company field
   // in the IETF Registration Form

Emails:
  // All email addresses used to register for the past 5 IETF meetings
  // Preferred email address first

Telephone:
   // For confirmation if selected

You should expect an email response from me within 5 business days stating whether or not you are qualified.  If you don't receive this response, please re-send your email with the tag "RESEND"" added to the subject line.

If you are not yet sure if you would like to volunteer, please consider that NomCom members play a very important role in shaping the leadership of the IETF.  Questions by email or voice are welcome. Volunteering for the NomCom is a great way to contribute to the IETF!

You can find a detailed timeline on the NomCom web site at:
   https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_nomcom_2020_&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=LoGzhC-8sc8SY8Tq4vrfog&m=ZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=NgIu-7Ij0nEdsFcbJOLcl2M56RxyREhLAtcaHLatD34&e=

I will be publishing a more detailed target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next few weeks.

Thank you!

Barbara Stark
bs7652 at att dot com
nomcom-chair-2020 at ietf dot org

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops