Re: [113attendees] IETF 113 Update: 2022-02-10
Alexander Mayrhofer <alexander.mayrhofer@nic.at> Thu, 17 February 2022 07:00 UTC
Return-Path: <alexander.mayrhofer@nic.at>
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 3A57D3A14A3 for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 23:00:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=nic.at
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 o2KTuLUGILIN for <113attendees@ietfa.amsl.com>; Wed, 16 Feb 2022 23:00:10 -0800 (PST)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) (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 467443A14A1 for <113attendees@ietf.org>; Wed, 16 Feb 2022 23:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.at; s=it2019; h=From:From:To:CC:Subject:Date:Message-Id:Content-Type:Received:Received:Received; bh=FoeiZTWxhDQZC7dpLZsziMc3O885WPFiadaTLmLjkF8=; b=dfYdKJyqKHslAMlxAWG50J4Qz1GAwVsrPU/YYNl7gsiCg9pVpuDkdIsGcR+kxmbsQ0+uARrLnS1+ClhLPbMiBvpb3AfsOXbj9bC3vLu/TNp++hWydHBzPCozCJX8lcw+EwhVLL+MuRZ4aVDTFM+Tocc2Cj0zzx7DWP0uoFvjZZHNkg/+iYIZFwtZVe8i3pn3ta4WeDCLIhTSSgUPEqgOJmUSlti8o1oz4ajnfxR1NHJxlJMtGU5ZE+XoHjrWrzn2xanpZfcjvvdqXc1K/mDT4wUW1vGpFGlFsEPEV0x0my+1xQ8yTOj790DN07h9w7Rf+8rAHleHT7bFPCCKYrOiBg==;
Received: from nics-exch3.sbg.nic.at ([10.17.175.2]) by mail.sbg.nic.at over TLS secured channel (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) with XWall v3.56 ; Thu, 17 Feb 2022 08:00:06 +0100
Received: from nics-exch3.sbg.nic.at (10.17.175.2) by nics-exch3.sbg.nic.at (10.17.175.2) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.12; Thu, 17 Feb 2022 08:00:06 +0100
Received: from nics-exch3.sbg.nic.at ([fe80::3079:e311:a6d4:792b]) by nics-exch3.sbg.nic.at ([fe80::3079:e311:a6d4:792b%2]) with mapi id 15.01.2375.012; Thu, 17 Feb 2022 08:00:06 +0100
Thread-Topic: [113attendees] IETF 113 Update: 2022-02-10
Thread-Index: AQHYIyEG/gh51qfOvUGhroVVBZ9WT6yWUfAAgAAG2QCAAACiAIAAQN2AgABO4QCAAGfzgA==
References: <9989E0B6-A0F6-4A4C-A681-FDB6C046455D@staff.ietf.org> <718578905.42881.1645007735648@appsuite-gw2.open-xchange.com> <E9A51103-58DB-47ED-A2D6-D83932150754@gmail.com> <LOYP265MB2094A4F9FD7386914BB06819C2359@LOYP265MB2094.GBRP265.PROD.OUTLOOK.COM> <c0928f11-b5a4-7d27-1d66-e641009f93f4@joelhalpern.com> <656A62B6-4C21-4A37-B92C-4B5B967D7894@cisco.com> <CAHw9_iJf-qmHGiPqPKs=Uas23VbkzEqB6Kv7+2FvdQydJonGKw@mail.gmail.com>
In-Reply-To: <CAHw9_iJf-qmHGiPqPKs=Uas23VbkzEqB6Kv7+2FvdQydJonGKw@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.11.83.53]
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: Warren Kumari <warren@kumari.net>, "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>
Cc: "113attendees@ietf.org" <113attendees@ietf.org>, Andrew Campling <andrew.campling@419.consulting>, "Joel M. Halpern" <jmh@joelhalpern.com>, Bob Hinden <bob.hinden@gmail.com>, Greg Wood <ghwood@staff.ietf.org>
Date: Thu, 17 Feb 2022 08:00:05 +0100
X-Assembled-By: XWall v3.56
Message-ID: <203fb37f24fc4864b7b6b00cb1f9f70a@nic.at>
X-XWALL-BCKS: auto
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="_NextPart_1_5ssey5umhazKkiyPrQRGhlVSVCr"
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/yf8s32-C9PAw19eMwmRfgmeU-Yo>
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: Thu, 17 Feb 2022 07:00:15 -0000
Hello, On Wed, Feb 16, 2022 at 3:03 PM Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>> wrote: A delegate on site would indeed be preferred and it can be decided the week before IETF-113. As an AD, I intend to check with all the chairs before and we will try to get a delegate who will be in Vienna. And I am sure that it will be the process for all ADs and for all WGs. Yup. For at least one of my WGs, the chairs have already let me know that they will not be able to make it to Vienna, and asked if I could please sit in the monkey chair and do the button clickin' and mic wranglin'. I've done this in the past, and can probably still manage it, but I figured that it's a good opportunity for some others to experience a small bit of what chairing is like, and so will either have someone join me, or will have both chair seats filled with non-chairs.... [AM] I’ve been a WG chair long time ago, and can volunteer to fill the monkey chair in groups shall there be need. Best, Alex
- [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