Re: [113attendees] IETF 113 Update: 2022-02-10
Toerless Eckert <tte@cs.fau.de> Wed, 16 February 2022 17:01 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: 113attendees@ietfa.amsl.com
Delivered-To: 113attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FE33A13DC for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 09:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.65
X-Spam-Level:
X-Spam-Status: No, score=-6.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 Q1DStLuzAVVk for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 09:01:11 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (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 9F8163A13C3 for <113attendees@ietf.org>; Wed, 16 Feb 2022 09:01:03 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 60B48549C89; Wed, 16 Feb 2022 18:00:57 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 46A404EA68A; Wed, 16 Feb 2022 18:00:57 +0100 (CET)
Date: Wed, 16 Feb 2022 18:00:57 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Greg Wood <ghwood@staff.ietf.org>
Cc: 113attendees@ietf.org
Message-ID: <Yg0tyUvL2exvf/wS@faui48e.informatik.uni-erlangen.de>
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/E31r_OjtByzrZnyB0kYJgmNkohI>
Subject: Re: [113attendees] IETF 113 Update: 2022-02-10
X-BeenThere: 113attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 113 attendees <113attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/113attendees>, <mailto:113attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/113attendees/>
List-Post: <mailto:113attendees@ietf.org>
List-Help: <mailto:113attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/113attendees>, <mailto:113attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2022 17:01:29 -0000
Greg, *: Thanks a lot for the update, but i am disappointed that the FAQ does not explain the crucial problem wrt to vaccination, even though i did bring up this topic some weeks ago and asked for it to be documented: a) Entry into Austria is with WHO approved vaccine. WHich includes for example sinovac WHich means its no problem to get into Austria given how the IETF also expects you to be WHO vaccinated. b) Overnight stay in a Vienna Hotel requires EMA approved vaccination. This has not changed with the updated rules from Feb 12th, even though it is unclear whether that is a voluntary rules by hotels or a city mandate (https://coronavirus.wien.gv.at/neue-corona-regeln/). c) I just called the Hilton and they did not know whether the relaxation for rules from March 5th on (as just announced) would include removal of the 2G rule for hotels in Vienna. The hotel speculated that it could be converted to 3G for overnight stay. It would be good to at least make IETF community members with non-EMA approved vaccines aware of the issue in the FAQ. Thanks Toerless On Thu, Feb 10, 2022 at 06:31:04PM -0500, Greg Wood wrote: > Hello, > > As promised, here is a brief update about the IETF 113 meeting (19-25 March 2022): > > # IETF 113 hotel reservations > > The reservation link for the Hilton Vienna Park meeting hotel is now available directly from the IETF 113 webpage: > > https://www.ietf.org/how/meetings/113/hotel/ > > # Pre-meeting site visit report > > A short informal report from the pre-meeting venue visit with information about the experience in Vienna is now available: > > https://www.ietf.org/blog/ietf113-venue-visit-report > > # Meeting Schedule update > > The IESG has announced the schedule for 21-25 March: > > https://mailarchive.ietf.org/arch/msg/113all/Ibfc66Xwoi3aZQnQFwOhTlrzqGg/ > > Further details about sessions and events on 19-20 March should be available shortly > > # FAQ > > The FAQ has been updated to include additional information about the meeting schedule and hotel reservations: > > https://www.ietf.org/how/meetings/113/faq/ > > The FAQ will be updated as additional information is available. > > As always, questions about IETF 113 are welcome at support@ietf.org. > > - Greg > > > -- > Greg Wood > IETF LLC > +1-703-625-3917 > -- --- tte@cs.fau.de
- [113attendees] IETF 113 Update: 2022-02-10 Greg Wood
- Re: [113attendees] IETF 113 Update: 2022-02-10 Michael Richardson
- Re: [113attendees] IETF 113 Update: 2022-02-10 Dr Eberhard W Lisse
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jeffrey (Zhaohui) Zhang
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Vittorio Bertola
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexander Mayrhofer
- [113attendees] Breaking news: IETF 113 will be af… Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Bob Hinden
- Re: [113attendees] IETF 113 Update: 2022-02-10 Toerless Eckert
- Re: [113attendees] IETF 113 Update: 2022-02-10 Andrew Campling
- Re: [113attendees] IETF 113 Update: 2022-02-10 Joel M. Halpern
- Re: [113attendees] IETF 113 Update: 2022-02-10 Eric Vyncke (evyncke)
- Re: [113attendees] IETF 113 Update: 2022-02-10 Warren Kumari
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexander Mayrhofer
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jan Zorz - Go6
- [113attendees] Predicting go/no go dates for IETF… Jim Reid
- Re: [113attendees] Predicting go/no go dates for … Salz, Rich
- Re: [113attendees] Predicting go/no go dates for … Jan Zorz - Go6
- Re: [113attendees] Predicting go/no go dates for … Jim Reid
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jay Daley
- Re: [113attendees] IETF 113 Update: 2022-02-10 Carsten Bormann
- Re: [113attendees] IETF 113 Update: 2022-02-10 Marc Petit-Huguenin
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jay Daley
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Dr Eberhard W Lisse
- Re: [113attendees] IETF 113 Update: 2022-02-10 Vittorio Bertola
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 John C Klensin
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Michael Richardson
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jan Zorz - Go6
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Eberhard W Lisse
- Re: [113attendees] IETF 113 Update: 2022-02-10 Scheffenegger, Richard
- Re: [113attendees] IETF 113 Update: 2022-02-10 Jan Zorz - Go6
- Re: [113attendees] IETF 113 Update: 2022-02-10 Petr Špaček
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Petr Špaček
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre PETRESCU
- Re: [113attendees] Breaking news: IETF 113 will b… Alexandre Petrescu
- Re: [113attendees] Breaking news: IETF 113 will b… Alexander Mayrhofer
- Re: [113attendees] Breaking news: IETF 113 will b… Marc Petit-Huguenin
- Re: [113attendees] Breaking news: IETF 113 will b… Greg Wood
- Re: [113attendees] Breaking news: IETF 113 will b… Rohan Mahy
- Re: [113attendees] Breaking news: IETF 113 will b… Marc Petit-Huguenin
- Re: [113attendees] Breaking news: IETF 113 will b… Eric Vyncke (evyncke)
- Re: [113attendees] Breaking news: IETF 113 will b… Dr Eberhard W Lisse
- Re: [113attendees] Breaking news: IETF 113 will b… Corine de Kater
- Re: [113attendees] Breaking news: IETF 113 will b… Marc Petit-Huguenin
- Re: [113attendees] Breaking news: IETF 113 will b… Scheffenegger, Richard
- Re: [113attendees] Breaking news: IETF 113 will b… Alexandre Petrescu
- Re: [113attendees] Breaking news: IETF 113 will b… Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu
- Re: [113attendees] IETF 113 Update: 2022-02-10 Alexandre Petrescu