From nobody Thu Jun 4 05:34:01 2020 Return-Path: X-Original-To: pals@ietfa.amsl.com Delivered-To: pals@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A415F3A0A29; Thu, 4 Jun 2020 05:33:40 -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, 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_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecitele.com header.b=UZLtuWWw; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.com header.b=uEHe8EaW 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 wCEfTIWqRfdH; Thu, 4 Jun 2020 05:33:38 -0700 (PDT) Received: from mail1.bemta25.messagelabs.com (mail1.bemta25.messagelabs.com [195.245.230.68]) (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 3B30B3A0B29; Thu, 4 Jun 2020 05:33:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ecitele.com; s=eciselector10072019; t=1591274012; i=@ecitele.com; bh=G5hjMBic5l9EKLSGwZfIyqpWAXj/dDZVjQQLe+3V+ME=; h=From:To:CC:Subject:Date:Message-ID:Content-Type:MIME-Version; b=UZLtuWWwdRt3bHGQmoIWCaE8+7+2/XkJbHS/6ktVseYxeoTjAJgFxvef0ajYDxLuS zsXs/qvwguozQH9psDYMFArTlvzCJQuRIRKz2tLTC1HdsGFg+MJgs9Rg0Vxj5JMQAL yT4TmRHEH/X3jgOMBjbpydJ8g/M5BQ/7ztDUbzA0= Received: from [100.112.196.81] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-b.eu-west-1.aws.symcld.net id 83/A5-51957-B1AE8DE5; Thu, 04 Jun 2020 12:33:31 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA1WTfUxbVRjGOffetncLxUsp8PJVl8I0brbSofN iNJrMJSRO3QybGZGPVq60oS2kLbZozIgZIoXitoxsHRuw0jIsFXVuY8s+op3jyxEqmayjcWFS EMqHMP4A1wm2vWPOf05+z/O855z3vTmXxAX1vGSSMRkYnVauFnM3EoK5+u8lKQFvQWbbSgLd0 WvFacfxKxjtP+kl6OD9JoLu83dw6FHH1xx6oiWJdq12YfTSwwuIbnVN8GjPbBCnez1BRFevXC Te4OfY7X9ju1EeR6VVlJmKOMqa7/7klvtEJutXXrwKLaeY0UYSUQ4c6pd+4bCihwBnWz9ixQ8 I+nqP8MKCoL7BYW3+OjcsBFQzBtYjswQr7iKw9d8JiQ0kl3oNznb+HqkSUjM4dPp/DgmSxKk9 4DiqDdfEUZtgsOkyFmYhtRnMg9cIlqVw1zPCDTNBZUC793DE51P5UOu2RXxEJcDygCuyF6cSY dTfEmGgKLBfGcJZjofp8dVHA9UiGJ4N8sI9APU03PbFsDVpMNxSh1g7Hc5N5bP222CxzSGWt4 BvzYOxJRmw6q5kbTW0jQ7yWH4GukeGHpWkwrS3iLVF4LTcI1hOhTFvd+SDAGXHoeZcA4cNnAS c7GEOIcmJJ4ZhWQvHF1y8E5HhY6Hf6idY/3lovXyfy/JWaD89g6/zzR/HsSf9VsRzopcVOlWJ 0qCRq9QSWWamRCbbJpFl05KsTKn8E4lCylRIjIzeIJFJ5Ua9VF+p+VBdLNUyhrMo9BiLy3tEF 5FldkHqRkkkJo7nt/m9BYIYRVlxpVKuVxbqKtSM3o1SSVIM/GNToSxWx5Qwpo9U6tCTXo+BjB YL+dnToZivL5dr9KoSNhpA2eSh6VM2nFx02kPrcngVENoyLZOcyD8YPo8Kb1BWaB8ft/6TDKO 05Dg+ioqKEkSXMzqNyvD/PIASSSSOY7uKVmkNj28NhBrCQg293jASbsgg/y9KrsKMZ+bN4upb Mwbzpe2f2XzBA5i5s/+t/H2bg5N5WZ+u7f3puaDOpbsWH3x2dSGb7KJyfsvte5VUlH5rIWnE+ 2cokNMzt+mG9VZW4X5jYME8Xft+3JmRDUzGvX2NH39RsJh7dWv7hY4d9jdLySlZ6+iuo1e5dV UrhTG/visski86Drv/6Hphuy7zYOnO99YGdom6v/ygGc3n5vkSqYTGGtlfvMmlO9XbdC+meBu sNytFGteOAwl9L3WZPMpXHM1pE/HVptK8d+pOiS/tfFCakiR+uMfyYGWy3rk/tjE7PV0406kA mybgGhw7f+OpqAq0ODu+d2mx+vbEWLD1ulEf7Wk6/7mY0Cvlsi24Ti//F6vekRWfBAAA X-Env-Sender: Alexander.Vainshtein@ecitele.com X-Msg-Ref: server-7.tower-291.messagelabs.com!1591274008!623704!1 X-Originating-IP: [18.237.140.177] X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass X-StarScan-Received: X-StarScan-Version: 9.50.1; banners=ecitele.com,-,- X-VirusChecked: Checked Received: (qmail 8198 invoked from network); 4 Jun 2020 12:33:30 -0000 Received: from p01b.mail.dlp.protect.symantec.com (HELO mail.ds.dlp.protect.symantec.com) (18.237.140.177) by server-7.tower-291.messagelabs.com with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 4 Jun 2020 12:33:30 -0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z4FuJa4I01rO9Ufiwzp5wQ6gTqBbMFAlRnnl7xBK2vp8qO+49Ub/R9nR89CQIr4hBJzNxPYgjazW8/1VySldQJaxGEVG3HAqdLAFXQ00rBPQ28iK1zlIZhI98Lyn/+mQJdhHc4ZzNG9sWbM98OmV+suAxCTcTLiqzRS8njWQT41KJ55D98559Gv7w9aVmfgpsnMXwC7ON5FVKvwGe53SE1WLuZqfT+BWdPvXG8cTQkMHwasbYF3aVfHP3ucuTnJkbIRVaK+2uILobckkcxkM0YmYqTFZDoAOViNELPBcMggGvqE3tDdcuLoPiJcE8gATMTftc5F4brcVYcg7jB9nWA== 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=fI1VASLXZz4Ox0ssXgNY86/9Q5c/pofN9fXJcIrJxdE=; b=XoDrWvoD0+ouKUAPbaBG/GCQ+/Dw/67RX0+kIrJkbSNwGiYP5hHnLhjhmLV4H/UCmZlx8HjNXbnAuk0JWIjQiiapdFTVpHvpxH0ZWDMGj7/ivC7kZlUzAVZFVBGZ5a86SnND3Olfi4kXmM6vXko79aN//y+IEf8RHvEKMAODgHQRFKA9JY4NK1XWa/d4zhlWu4oJu9edUX454bqOvTVeWQSmWgboxYZvZ0laoXiy97UOnAZeN2HC8VJMwu7GZt4Zai4/UXh3pTV145xXq4+ES9pmxwyK6cZMOSY/RLoa3HfD+vwC6ihuXNFrJQCsP1+WJo1Tcbfa0Jaa6SkdIMoKsw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ecitele.com; dmarc=pass action=none header.from=ecitele.com; dkim=pass header.d=ecitele.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector2-ECI365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fI1VASLXZz4Ox0ssXgNY86/9Q5c/pofN9fXJcIrJxdE=; b=uEHe8EaWLKYvBFl75cGbw6BanXM7s6D6DHBy0Nf54y9eaTtZJoylMZY/aa0CFfZGFZrtoTaMIm+V38aPGOlDcl7k0feTmcWkPK1c0l+z/tCkqRRgep2lNFCGd6I8FH+a2WNJ+GNEXZGBYoL6Rsr2/JqmcuyeYJS1Fxv+Gel8EG8= Received: from AM0PR03MB4499.eurprd03.prod.outlook.com (2603:10a6:208:c4::33) by AM0PR03MB3905.eurprd03.prod.outlook.com (2603:10a6:208:6c::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.19; Thu, 4 Jun 2020 12:33:26 +0000 Received: from AM0PR03MB4499.eurprd03.prod.outlook.com ([fe80::8c03:b832:8af9:7992]) by AM0PR03MB4499.eurprd03.prod.outlook.com ([fe80::8c03:b832:8af9:7992%7]) with mapi id 15.20.3066.019; Thu, 4 Jun 2020 12:33:26 +0000 From: Alexander Vainshtein To: "rtg-dir@ietf.org" , "spring@ietf.org" , "lsr@ietf.org" , "bess@ietf.org" , "rtgwg@ietf.org" , "rtg-bfd@ietf.org" , "CCAMP@ietf.org" , "teas@ietf.org" , "bier@ietf.org" , "lsr@ietf.org" , "pals@ietf.org" , "detnet@ietf.org" , "mpls@ietf.org" , "nvo3@ietf.org" CC: Ron Sdayoor , Rotem Cohen Thread-Topic: Change of email address Thread-Index: AdY6a+TLCHm6WE7zRQSbSvqx0WrAHA== Date: Thu, 4 Jun 2020 12:33:26 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [79.183.63.9] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 0462e468-617d-4428-fc4b-08d808837aaa x-ms-traffictypediagnostic: AM0PR03MB3905: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 04244E0DC5 x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: oqX1MOKb7TS+HaVmi3rcoRopuKRJJc0WRoEvfH7Iiu3CCgDefRgq+eHNhYYmgiHB8NSx9qR8JVzKnT7TOcDlmw2wlBCuLGzP0HrfTpe8fGtVcevpOGhb3IcmYroecXvtM24LYNjnwdGd9qBuHQ1EnR/+0zkkw0YacWy+XYGxp2LVclwQXFq0ijQ90ghoVXtS11urzvMDIeYW6da7QRmCFSDeLDDOOeCMSuwBQe6QnI2YceaUs1hYqyi70pQduTTKONO++SHVm9q7FEV2T/a5MRfjBzkx1zFP3fT4vkgfI7S4mB8wWNx6cR65CHaCq0bvC4NuLrC+iEZeBynSUT/wBNfnmOAiZ9GlSyb6IKeQl5xVM/JotJG9SIiQQGs04C5o x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR03MB4499.eurprd03.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(136003)(396003)(39860400002)(366004)(346002)(376002)(316002)(5660300002)(110136005)(450100002)(9686003)(55016002)(478600001)(54906003)(3480700007)(8676002)(107886003)(7416002)(8936002)(186003)(6506007)(66446008)(4326008)(2906002)(76116006)(71200400001)(52536014)(83380400001)(64756008)(66556008)(26005)(7696005)(33656002)(4744005)(86362001)(66946007)(66476007)(921003); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata: s8z6+Qk0NvQdpKY7y5MlnzBV0nfphQUZovVqM1fEMwixaAX2P0qlf6Yop7cmZbFgkZ6hGjRHXX3Ehogmml6b8Rm24wqCNAO/jcQOo+Napz9fZmCRILS+2F1freIHeXzFVZ13HJTIw6NPVJYHzsXAXoF/7BGGgXRcvwS3UeBdSlae8pwgnDir+Ttm+CPyriSck6ZA4Gulr6KDdKbTrZ7PBynU0AQtoVN5RAmjsUDx7FQZrK8KrTYLKHghRoB6TWeO/fUqaXpLM1m0hUdjJ0Hf9Q4kr9xJ2N8V5Dv/WN4cNN1xZOp5hWeDEMY5SXlVm74yCS2Fefvsi1XzskqvZIq0OAUEKeIJNdzffM6LhVGnLt/BwSSG8UbQzEDBtU7IkAh9tZ4noghg26ZdoIiYn4yFmvlo37PlHYkr2kXTZUWZRgKBR081WsQ+bc97GbEUzQzcSlaPmuHGq/Jv9DDR8XwEzmAvRBWixNJj+A/5GOu3qOg= Content-Type: multipart/alternative; boundary="_000_AM0PR03MB4499A03C46A28A22693EAA439D890AM0PR03MB4499eurp_" MIME-Version: 1.0 X-OriginatorOrg: ecitele.com X-MS-Exchange-CrossTenant-Network-Message-Id: 0462e468-617d-4428-fc4b-08d808837aaa X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Jun 2020 12:33:26.3929 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: aCT7U+3db9zXuycCebVfwqPbkGT4Xm/+YIrPJNljHfTg9LiUn23wR8+3wsMhQmfvr44v0g5sIo92lTNCMaQn1g== X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR03MB3905 X-CFilter-Loop: Reflected X-DetectorID-Processed: d8d3a2b3-1594-4c39-92fb-b8312fe65a8a Archived-At: Subject: [Pals] Change of email address X-BeenThere: pals@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Pseudowire And LDP-enabled Services dicussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 12:33:41 -0000 --_000_AM0PR03MB4499A03C46A28A22693EAA439D890AM0PR03MB4499eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear colleagues, Following the acquisition of my employer - ECI Telecom, by Ribbon, startin= g from 09-Jun-20 all the mails I will send to IETF will use alexander.vain= shtein@rbbn.com as my address. I will still be receiving emails addressed to alexander.vainshtein@ecitele= .com (at least for the time being= ). I will re-subscribe to all the IETF mailing lists using my new email once = it becomes operational. Regards, and apologies for possible inconvenience, Sasha Office: +972-39266302 Cell: +972-549266302 Email: Alexander.Vainshtein@ecitele.com __________________________________________________________________________= _ This e-mail message is intended for the recipient only and contains inform= ation which is=20 CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have rece= ived this=20 transmission in error, please inform us by e-mail, phone or fax, and then = delete the original=20 and all copies thereof. __________________________________________________________________________= _ --_000_AM0PR03MB4499A03C46A28A22693EAA439D890AM0PR03MB4499eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear colleagues,

Following the acquisition of my employer – EC= I Telecom, by Ribbon, starting from 09-Jun-20 all the mails I will send to= IETF will use alexander.vainshtein@rbbn= .com as my address.

 

I will still be receiving emails addressed to alexander.vainshtein@ecitele.com (at least for the time being).

 

I will re-subscribe to all the IETF mailing lists u= sing my new email once it becomes operational.

 

Regards, and apologies for possible inconvenience,<= o:p>

Sasha

 

Office: +972-39266302

Cell:      +972-549266= 302

Email:   Alexander.Vainshtein@ecitele.com=

 


__________________________________________________________________________= _

This e-mail message is intended for the recipient only and contains inform= ation which is
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have rece= ived this
transmission in error, please inform us by e-mail, phone or fax, and then = delete the original
and all copies thereof.
__________________________________________________________________________= _
--_000_AM0PR03MB4499A03C46A28A22693EAA439D890AM0PR03MB4499eurp_-- From nobody Fri Jun 5 15:47:42 2020 Return-Path: X-Original-To: pals@ietf.org Delivered-To: pals@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 282C43A0EDF; Fri, 5 Jun 2020 15:47:40 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: agmalis@gmail.com, pals@ietf.org, db3546@att.com, pals-chairs@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.1.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <159139725975.16744.17174485008660501323@ietfa.amsl.com> Date: Fri, 05 Jun 2020 15:47:40 -0700 Archived-At: Subject: [Pals] pals - Not having a session at IETF 108 X-BeenThere: pals@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Pseudowire And LDP-enabled Services dicussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jun 2020 22:47:40 -0000 Andrew Malis, a chair of the pals working group, indicated that the pals working group does not plan to hold a session at IETF 108. This message was generated and sent by the IETF Meeting Session Request Tool. From nobody Thu Jun 11 03:01:13 2020 Return-Path: X-Original-To: pals@ietfa.amsl.com Delivered-To: pals@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E893A07EA for ; Thu, 11 Jun 2020 03:01:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 tays5oYyY9Wj for ; Thu, 11 Jun 2020 03:01:09 -0700 (PDT) Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF0303A07E6 for ; Thu, 11 Jun 2020 03:01:08 -0700 (PDT) Received: by mail-wr1-x42f.google.com with SMTP id p5so5476698wrw.9 for ; Thu, 11 Jun 2020 03:01:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=2TFoQR0PhlzGti8KaSXFF0VeUlb/Uk/fSGKyziWTjII=; b=NZtdvAOruKwZUXEP5NdcRQ+/ijdbSSfeuEvz1StgNi/JkutmLuraS+Co+rUBtOQHam ODlq4o9Nz/UOcCzRDEtZdzsR4Y1kH3Aa3tfsTWvr3yDZG8w+7Kqx4FkPzvEK/cnrJ3Rm NKF7a7rPtRs33Di3Pw62lrz4vUa9bGI1jr13CAc6bARlaVUeyoaswzp8AvCQplpm3y4W nfeRYeNFQxk2D8CI1p45Jg7cAonLkV97HhCOEw4uHjGnd7USE7EDL5A8MH/bot7jUIoo xTt2pepqE2XzSqbFNd53VS3mJTq/wQx4fKrGW5J1ujx09cBTHN7mUpZ5FCFHbvcc1pFu MIdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=2TFoQR0PhlzGti8KaSXFF0VeUlb/Uk/fSGKyziWTjII=; b=DOFnJjKmB9V5RzFqq1p74InmnCPQF1mkbjCEBElBqX3OqtxsWfHxO441buhw0D48E/ n5JLZhDozeH6OZcTepaTJojRDud5nRVb7BpI7CkSjwoLCGNH2rKopZjP6rLQ/W9jGYL7 iAQEIU/sAfkrzw+2sRcXuW2AVYnqHHh/snw3D9pkF6nWoTLa2qOVLmi1pPClHCq91Oxq MAR98P6+wNoBQP/yxK4KXgz8SMRhdTwRDcDcc+0ZOBIQv48DMIkX3OrYOdMTrzRsLEYF zZMO4kYx8LwtqIzfD41LFtv8lVgUYqV+xNOQ3y03FFmwT3ZhAoTYV1jc+bclCtY1vb+X UAOA== X-Gm-Message-State: AOAM533RXkF1VVHgsqY+uLYaHdodTz4urT+ZOEjxmvzU4FKIXJeye9Mx oqWoYq25V9IWeFGXvMKndhgkkcDP97c= X-Google-Smtp-Source: ABdhPJw55DTviGopSOGmQb7x77JPaKoEaeUtxJTpYL3HKYLndiY13rJyF2SjuGvNHKrSN/ucKK/cqA== X-Received: by 2002:a5d:6b85:: with SMTP id n5mr8609490wrx.11.1591869664747; Thu, 11 Jun 2020 03:01:04 -0700 (PDT) Received: from appleton.fritz.box ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id s72sm3111394wme.35.2020.06.11.03.01.03 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jun 2020 03:01:04 -0700 (PDT) From: Stewart Bryant Message-Id: <25854DC3-731F-49F4-B08D-5B13831D3524@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_19C1ED2A-49C4-4F19-AEAC-21F0E852C718" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Date: Thu, 11 Jun 2020 11:01:02 +0100 In-Reply-To: <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com> Cc: Stewart Bryant To: pals@ietf.org References: <159181529656.16063.6964178024900109434@ietfa.amsl.com> <90F43A4B-9A1E-480A-B7BF-75A93842C261@att.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) Archived-At: Subject: Re: [Pals] Nomcom 2020-2021 Second Call For Volunteers X-BeenThere: pals@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Pseudowire And LDP-enabled Services dicussion list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2020 10:01:11 -0000 --Apple-Mail=_19C1ED2A-49C4-4F19-AEAC-21F0E852C718 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Two of our ADs are up for selection, so this is important for us: both = to make sure that the Nomcom pool is large enough, and making sure that = there is an adequate pool of candidates for the Nomcom to select from in = a few months. - Stewart > On 10 Jun 2020, at 22:50, STARK, BARBARA H wrote: >=20 > Hi fellow chairs, > Would you mind sending this announcement on to your WGs and impress on = them how important it is? Especially if the WG=E2=80=99s AD is up for = selection.=20 > Thx, > Barbara=20 >=20 >=20 > Begin forwarded message: >=20 >> From: NomCom Chair 2020 >> Date: June 10, 2020 at 1:55:21 PM CDT >> To: IETF Announcement List >> Cc: "ietf@ietf.org" >> Subject: Nomcom 2020-2021 Second Call For Volunteers >>=20 >> =EF=BB=BFThis is the second sending of the call for volunteers for = the 2020-2021 NomCom. >>=20 >> 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=3Dhttps-3A__datatracker.ietf.or= g_nomcom_2020_&d=3DDwIDaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DLoGzhC-8sc8SY8Tq4= vrfog&m=3DZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=3DNgIu-7Ij0nEdsFcb= JOLcl2M56RxyREhLAtcaHLatD34&e=3D 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. >>=20 >> 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. >>=20 >> The details of the operation of the NomCom can be found in BCP 10 = (RFC 8713). RFC 3797 details the selection algorithm. >>=20 >> 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: >>=20 >> Members of the IETF community must have attended at least three = of >> the last five in-person IETF meetings in order to volunteer. >>=20 >> 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=20 >> 106 [Singapore; November 2019]. >>=20 >> 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=3Dhttps-3A__www.ietf.org_regist= ration_nomcom.py&d=3DDwIDaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DLoGzhC-8sc8SY8T= q4vrfog&m=3DZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=3D7_9x9PPoUIajJs= 2AnUFYg0KnEg8gkD3Jnwf1v079EQo&e=3D . >>=20 >> 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. >>=20 >> 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! >>=20 >> 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 >>=20 >> IETF Trust: >> Joel Halpern >>=20 >> LLC: >> Maja Andjelkovic >>=20 >> IAB: >> Jari Arkko >> Jeff Tantsura >> Mark Nottingham >> Stephen Farrell >> Wes Hardaker >> Zhenbin Li >>=20 >> IESG: >> Alissa Cooper, IETF Chair/GEN AD >> Alvaro Retana, RTG AD >> Barry Leiba, ART AD >> Deborah Brungard, RTG AD >> =C3=89ric Vyncke, INT AD >> Magnus Westerlund, TSV AD >> Roman Danyliw, SEC AD >> Warren Kumari, OPS AD >>=20 >> 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. >>=20 >> 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. >>=20 >> While being a NomCom member does require some time commitment it is = also a very rewarding experience. >>=20 >> 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. >>=20 >> Please volunteer by sending me an email before 23:59 UTC June 24, = 2020, as follows: >>=20 >> To: nomcom-chair-2020@ietf.org >> Subject: NomCom 2020-21 Volunteer >>=20 >> Please include the following information in the email body: >>=20 >> Your Full Name:=20 >> // as you write it on the IETF registration form >>=20 >> Current Primary Affiliation: >> // Typically what goes in the Company field >> // in the IETF Registration Form >>=20 >> Emails:=20 >> // All email addresses used to register for the past 5 IETF = meetings >> // Preferred email address first >>=20 >> Telephone:=20 >> // For confirmation if selected >>=20 >> 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. >>=20 >> 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! >>=20 >> You can find a detailed timeline on the NomCom web site at: >> = https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf.or= g_nomcom_2020_&d=3DDwIDaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&r=3DLoGzhC-8sc8SY8Tq4= vrfog&m=3DZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEnsbPBtI&s=3DNgIu-7Ij0nEdsFcb= JOLcl2M56RxyREhLAtcaHLatD34&e=3D=20 >>=20 >> 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. >>=20 >> Thank you! >>=20 >> Barbara Stark >> bs7652 at att dot com >> nomcom-chair-2020 at ietf dot org >>=20 --Apple-Mail=_19C1ED2A-49C4-4F19-AEAC-21F0E852C718 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Two of our ADs are up for selection, so this is = important for us: both to make sure that the Nomcom pool is large = enough, and making sure that there is an adequate pool of candidates for = the Nomcom to select from in a few months.

- Stewart


On 10 = Jun 2020, at 22:50, STARK, BARBARA H <bs7652@att.com> wrote:

Hi fellow chairs,
Would you mind sending this announcement on = to your WGs and impress on them how important it is? Especially if the = WG=E2=80=99s AD is up for selection. 
Thx,
Barbara 


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

=EF=BB=BFThis 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=3Dhttps-3A__datatrac= ker.ietf.org_nomcom_2020_&d=3DDwIDaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&am= p;r=3DLoGzhC-8sc8SY8Tq4vrfog&m=3DZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEn= sbPBtI&s=3DNgIu-7Ij0nEdsFcbJOLcl2M56RxyREhLAtcaHLatD34&e=3D  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=3Dhttps-3A__www.ietf= .org_registration_nomcom.py&d=3DDwIDaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&= amp;r=3DLoGzhC-8sc8SY8Tq4vrfog&m=3DZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzm= EnsbPBtI&s=3D7_9x9PPoUIajJs2AnUFYg0KnEg8gkD3Jnwf1v079EQo&e=3D .

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
   =C3=89ric 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=3Dhttps-3A__datatrac= ker.ietf.org_nomcom_2020_&d=3DDwIDaQ&c=3DLFYZ-o9_HUMeMTSQicvjIg&am= p;r=3DLoGzhC-8sc8SY8Tq4vrfog&m=3DZsNIRqCxjDeOYYDNalOSHcuwQG23wBJtxzmEn= sbPBtI&s=3DNgIu-7Ij0nEdsFcbJOLcl2M56RxyREhLAtcaHLatD34&e=3D

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


= --Apple-Mail=_19C1ED2A-49C4-4F19-AEAC-21F0E852C718--