IETF Logo Mail Archive

Re: [admin-discuss] Consultation on COVID management for IETF 114 - Closes 29 May 2022

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 24 May 2022 15:52 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FD5C1B92A0 for <admin-discuss@ietfa.amsl.com>; Tue, 24 May 2022 08:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LudcdjUeQxHm for <admin-discuss@ietfa.amsl.com>; Tue, 24 May 2022 08:52:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66659C19D46B for <admin-discuss@ietf.org>; Tue, 24 May 2022 08:52:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id AF1E138E19; Tue, 24 May 2022 12:07:07 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UzQMsS9JYS8h; Tue, 24 May 2022 12:07:03 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7CF7E38E0A; Tue, 24 May 2022 12:07:03 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1653408423; bh=LWIg2Xts/w06GryYkQSoHslDCxu9ilIdvJQrYjhQv/8=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=v2CgAWUwHljtxvKJT+Ktod7/VsXULVUEVDQO8w2tode2X79j79n04YnJlpSU1sqwi 1NJOw+OkTIke5dlMLfPDLsHZrTe6bB2Jj/zx8gNnewpVZyCiX89PVp8uSNXWYuy4Ey Am7KHQGwCt/OBRxZFXwHH2uqZOeBOMkHLDenzTVPP8cDjmYiJisqNj9J6xqF03KKka S9YXY7+3oR0Wh7No87R9eBTZfiQRkW0dHDOGrtJHnXDuMAnugP0GaUe8iX2Sk6HrNz PCMXOHiDgbdYlDWk7RrpUmMzLb7545UgvVqUqo7Eh3fjQsiWU0Lm6pEM19AhqTs5LT XgOjO4Xk/0d8w==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 47D3A3C3; Tue, 24 May 2022 11:52:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
cc: "admin-discuss@ietf.org" <admin-discuss@ietf.org>
In-Reply-To: <59FD8B0B-6C23-4100-82CA-B42504F101B2@cable.comcast.com>
References: <D1AD5F79-6546-4830-AB10-7814E573FBF7@ietf.org> <10149.1653345099@localhost> <59FD8B0B-6C23-4100-82CA-B42504F101B2@cable.comcast.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 24 May 2022 11:52:40 -0400
Message-ID: <4708.1653407560@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/FJqfLMIhyrhXo-CNeACNwZSNq_A>
Subject: Re: [admin-discuss] Consultation on COVID management for IETF 114 - Closes 29 May 2022
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2022 15:52:50 -0000

Livingood, Jason <Jason_Livingood@comcast.com> wrote:
    > On 5/23/22, 18:31, "admin-discuss on behalf of Michael Richardson" <admin-discuss-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:
    >> I believe that I will be flying in/out of Newark and taking Amtrak/NJTransit
    > to/from PHL.  If there are any Pennsylvia/NJ "border" crossing issues we need
    > to know about, it would be good to know in advance.

    > [JL] Ha! Thankfully, no border between the states, as such. And the
    > train transfer from EWR to NJ Transit and Amtrak or SEPTA is quite
    > easy. IIRC the first step is to take the "AirTrain" monorail from the
    > terminal over to the Newark Liberty International Airport Station. From
    > there, you can transfer to Amtrak, then get off at Philadelphia's 30th
    > Street Station. This is a short taxi ride from the venue/hotel and
    > there is a standing taxi queue to one side of 30th Street Station
    > (clearly marked above the exit to the building).

Well, I was thinking about differences in masking mandates on public transit
between US states.   For instance, NL does not require masks, but DE does,
and yet trains cross that border.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.46.0 | Report a Bug | By Email | System Status