IETF Logo Mail Archive

Re: IETF in July

Jared Mauch <jared@puck.nether.net> Fri, 20 March 2020 20:45 UTC

Return-Path: <jared@puck.nether.net>
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 1B2A13A0E29 for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2020 13:45:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 IM2D2toXDdeX for <ietf@ietfa.amsl.com>; Fri, 20 Mar 2020 13:45:34 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1711B3A0E0F for <ietf@ietf.org>; Fri, 20 Mar 2020 13:45:33 -0700 (PDT)
Received: from [10.0.0.129] (c-68-49-104-93.hsd1.mi.comcast.net [68.49.104.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 42B935403DA; Fri, 20 Mar 2020 16:45:31 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
Subject: Re: IETF in July
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <DM6PR05MB63488A5D5D14D11CBF145CEBAEF50@DM6PR05MB6348.namprd05.prod.outlook.com>
Date: Fri, 20 Mar 2020 16:45:30 -0400
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1AAA027D-2EF1-4087-BBDB-E4C2BF564A36@puck.nether.net>
References: <DM6PR05MB63488A5D5D14D11CBF145CEBAEF50@DM6PR05MB6348.namprd05.prod.outlook.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kLbxCPcRGyBsapERqC7273AuKo0>
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: Fri, 20 Mar 2020 20:45:41 -0000

Ron,

Might I suggest we get through the next week first? :-)

I’ll wait to see the hotel announcement like everyone else, which I presume won’t be sent until travel normalizes, since many international borders are closed.

- Jared

> On Mar 20, 2020, at 4:42 PM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
> 
> Folks,
>  
> Is anybody planning contingencies for a fully remote IETF in July? (I don’t mean to be a pessimist, but planning for a worst-case scenario is never a bad idea).
>  
> Clearly, the plan would have to included technical aspects. But it might also need to address financial aspects (e.g., how will we keep the IETF funded without registration fees?)
>  
>                                                                                                        Ron
>  
> 
> Juniper Business Use Only

v2.23.0 | Report a Bug | By Email