Re: Remote hubs for IETF 98
<nalini.elkins@insidethestack.com> Sat, 04 February 2017 16:36 UTC
Return-Path: <nalini.elkins@insidethestack.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 D0E7112964E for <ietf@ietfa.amsl.com>; Sat, 4 Feb 2017 08:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level:
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 BIokC546m44E for <ietf@ietfa.amsl.com>; Sat, 4 Feb 2017 08:36:29 -0800 (PST)
Received: from nm39.bullet.mail.gq1.yahoo.com (nm39.bullet.mail.gq1.yahoo.com [98.136.217.22]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E93412964F for <ietf@ietf.org>; Sat, 4 Feb 2017 08:36:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1486226187; bh=3cRhP9wWlCXHH7oOxIhPfFgPaCjd3GRzognGKqNiRsA=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=CtoJoACoXO7IYuyT+7Uv7gJ9cxKx4VGTec4GTrdZwgcCKjwGWwuZSZR9Qgg8bmbK/vLYhytrP8cL6MIB2eKJz1JyO5kBGpPfhcZFlACpNDS7tEhXAoHEEgkZa2jxQ4Xn6KvmV9+p3FcxAjtd6RyjFHaWqO4gK0duzhcCR0+iMrop613bwzhCFe6mjZ/7hbqsyJKsI3mWH12DT89goiCf/yvNbIOSo/ZGtBj0GtD1V2x7cC+SV//cNOaRjfrABzLSYc55RKg4TCsEaiuqv2NulyOOF6zvHt8gJkCrvljc5sjdHmfjp+w8zu0gaIrUxy9GwGrR7+1Oy+1NnWObV3AvjQ==
Received: from [127.0.0.1] by nm39.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:36:27 -0000
Received: from [98.137.12.59] by nm39.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:33:46 -0000
Received: from [98.137.12.215] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:32:46 -0000
Received: from [127.0.0.1] by omp1023.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:32:46 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 516516.64437.bm@omp1023.mail.gq1.yahoo.com
X-YMail-OSG: H52lNU4VM1k4TMdWtvP54EvgUQXkDxKY.x7_mfDU4riPJA.umskEhyP5gPabruW _ZFUpJPKhR34gwAI4y7_euiq5VMUF2Oe1RJt_hPAIm6zfuZ0GkKXDj0ltWPkb7TGEVM4R.mW6Gv. w4RCiOrxRz2MpAF0zMWf6NBosqp8M7WXZl3L_ddS8nKBWoN5e4uPJy3kKk8W.Yv5qZnfLppW9Phw upm5bo6SgnJKyFAVW_0cS0kdOm3UP0cofrlT2Hc7.uupFRQCscu_8.RdZoiUXRdq9Is_93NlsYGL .lrUPnPAlgIZk6_IlSgerGkOBXsv2MlzH.xh6LUHfobUv_HoWc9_qE2liMMJ_b1BHH.exdQZNI78 DbsSaXGlqxU6hjUmvYuEBatCZsNyIoW1xtbnHx7p30EfdMAK6tqE5JmUEpTP09TzhdLm7nALiZXQ 6z7Y5BoXJ6sQok6SRCL6UEmdoqowkrAwS80UBejXuf1b3h0m9pr2JW1YNp6GNiNVqxCNgE3cJl7t FaCHo2SfanfUaFuIYjPU9XTxeXtcOUtdKaQB4WQ--
Received: from jws300066.mail.gq1.yahoo.com by sendmailws104.mail.gq1.yahoo.com; Sat, 04 Feb 2017 16:32:46 +0000; 1486225966.156
Date: Sat, 04 Feb 2017 16:32:45 +0000
From: nalini.elkins@insidethestack.com
To: IETF Announcement List <ietf-announce@ietf.org>, chair@ietf.org, ted.ietf@gmail.com, warren@kumari.net
Message-ID: <1810751398.1259948.1486225965881@mail.yahoo.com>
Subject: Re: Remote hubs for IETF 98
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
References: <1810751398.1259948.1486225965881.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rpLlIUJOgUU-clQcUD7Cs0vFHC4>
Cc: ted.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Sat, 04 Feb 2017 16:36:30 -0000
Thank you, Ted, Warren and Google for doing this. You are setting a precedent for others to follow. Nalini Elkins Inside Products, Inc. www.insidethestack.com (831) 659-8360 -------------------------------------------- On Fri, 2/3/17, IETF Chair <chair@ietf.org> wrote: Subject: Remote hubs for IETF 98 To: "IETF Announcement List" <ietf-announce@ietf.org> Cc: ted.ietf@gmail.com, ietf@ietf.org Date: Friday, February 3, 2017, 12:56 PM I’m happy to report that Ted Hardie and Warren Kumari and Google have stepped up to make alternate arrangements for people who might have difficulty travelling due to the recent travel restrictions. Thank you! Please see the details below: ------- Hi Jari, Warren and I have arranged for Google to provide two remote hubs for participants who won't be able to attend IETF 98 in Chicago because of the recent travel restrictions. While we understand that many folks might prefer to simply attend remotely from their home or office, experience with the IGF and the Latin American remote IETF hubs suggests that there may be folks who prefer to be with others for the events. We hope that providing this option makes things a bit easier for them. The current plan is to use two Google offices, one in eastern Canada (so as to be in a nearby time zone) and one in Europe (which seems to have the highest percentage of affected participants). These offices will be staffed by volunteers and will provide local conference room facilities, wireless network, and snacks. We have some flexibility on which offices to use, and we'd be happy to take email from potential remote participants on their preferences. Alternatively, we've also set up a form at https://goo.gl/forms/pbuaDdhS2xyKpcps1 to collect this data, if people prefer not to use email for this. (The form does not require a Google login to complete). We understand, of course, that situation is fluid, but given the need to coordinate with local volunteers, it would be great to have an early insight into who many of the affected people might use this option. If you could share this option with the community so we can get that insight, we'd appreciate it. thanks, Ted Hardie Warren Kumari
- Remote hubs for IETF 98 IETF Chair
- Re: Remote hubs for IETF 98 Leif Johansson
- Re: Remote hubs for IETF 98 nalini.elkins