Re: [Taps] Conflict with next meeting - Jan 26
"Philipp S. Tiesel" <phils@in-panik.de> Mon, 17 January 2022 08:57 UTC
Return-Path: <phils@in-panik.de>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62A053A00E0 for <taps@ietfa.amsl.com>; Mon, 17 Jan 2022 00:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.496
X-Spam-Level:
X-Spam-Status: No, score=-1.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 j0bMbnonbdhB for <taps@ietfa.amsl.com>; Mon, 17 Jan 2022 00:57:33 -0800 (PST)
Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 4A3A83A00E3 for <taps@ietf.org>; Mon, 17 Jan 2022 00:57:32 -0800 (PST)
X-Envelope-From: phils@in-panik.de
Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de with ESMTPS id 20H8vPum006017 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 17 Jan 2022 09:57:25 +0100
Received: from [193.16.224.5] (helo=smtpclient.apple) by x-berg.in-berlin.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <phils@in-panik.de>) id 1n9NpN-0003R7-Jr; Mon, 17 Jan 2022 09:57:25 +0100
From: "Philipp S. Tiesel" <phils@in-panik.de>
Message-Id: <D793A815-5E78-463B-A232-9F710F6B70F2@in-panik.de>
Content-Type: multipart/alternative; boundary="Apple-Mail=_343EA977-B1B7-49BB-8C14-EF16660C10CC"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
Date: Mon, 17 Jan 2022 09:57:24 +0100
In-Reply-To: <f7c350e7ef1b44b8ba4b5419ce1a9be7@kau.se>
Cc: Aaron Falk <aaron.falk@gmail.com>, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>, "taps@ietf.org" <taps@ietf.org>
To: Anna Brunström <anna.brunstrom@kau.se>
References: <640F223D-ACCF-47FB-A131-4C3880AC3193@ericsson.com> <CAD62q9X-XVObCdyf04j7MnmR4UZ3fJx1-G_qAN_xK+Ly=2+v=A@mail.gmail.com> <f7c350e7ef1b44b8ba4b5419ce1a9be7@kau.se>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Os46MrCYPN_s5yCyRJOBAeSbsNY>
Subject: Re: [Taps] Conflict with next meeting - Jan 26
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2022 08:57:37 -0000
Hi, same here – I could make teh 26th, but would prefer to move to Feb. 2nd. AVE! Philipp > On 17. Jan 2022, at 01:00, Anna Brunström <anna.brunstrom@kau.se> wrote: > > I plan to attend, but moving the meeting to Feb 2 would be better also for me. > > Anna > > From: Taps <taps-bounces@ietf.org <mailto:taps-bounces@ietf.org>> On Behalf Of Aaron Falk > Sent: den 15 januari 2022 22:26 > To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org <mailto:mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>> > Cc: taps@ietf.org <mailto:taps@ietf.org> > Subject: Re: [Taps] Conflict with next meeting - Jan 26 > > Can folks who are planning to attend the TAPS interim on Jan 26 at 11am EST reply to this message? Let’s see if we still have a critical mass. > > —aaron > > On Fri, Jan 14, 2022 at 5:26 AM Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org <mailto:40ericsson.com@dmarc.ietf.org>> wrote: > Hi all, > > I just notice that I have a conflict with the next meeting. In the first half we now scheduled an IESG/IAB workshop, which will also impact Tommy and Colin. And the second half collides with the joint ADD/DPRIVE/DNSOP interim meeting, which I guess also impacts Tommy and maybe others. > > You definitely don't have to move the meeting because of me but maybe it would be good to check again who would be actually able to join. > > Mirja > > > > _______________________________________________ > Taps mailing list > Taps@ietf.org <mailto:Taps@ietf.org> > https://www.ietf.org/mailman/listinfo/taps <https://www.ietf.org/mailman/listinfo/taps> > När du skickar e-post till Karlstads universitet behandlar vi dina personuppgifter <https://www.kau.se/gdpr>. > When you send an e-mail to Karlstad University, we will process your personal data <https://www.kau.se/en/gdpr>. > > _______________________________________________ > Taps mailing list > Taps@ietf.org <mailto:Taps@ietf.org> > https://www.ietf.org/mailman/listinfo/taps <https://www.ietf.org/mailman/listinfo/taps> AVE! Philipp S. Tiesel -- Philipp S. Tiesel https://philipp.tiesel.net/
- [Taps] Conflict with next meeting - Jan 26 Mirja Kuehlewind
- Re: [Taps] Conflict with next meeting - Jan 26 Aaron Falk
- Re: [Taps] Conflict with next meeting - Jan 26 Brian Trammell (IETF)
- Re: [Taps] Conflict with next meeting - Jan 26 Colin Perkins
- Re: [Taps] Conflict with next meeting - Jan 26 Anna Brunström
- Re: [Taps] Conflict with next meeting - Jan 26 Philipp S. Tiesel
- Re: [Taps] Conflict with next meeting - Jan 26 Michael Welzl
- Re: [Taps] Conflict with next meeting - Jan 26 Reese Enghardt
- Re: [Taps] Conflict with next meeting - Jan 26 Gorry (erg)
- Re: [Taps] Conflict with next meeting - Jan 26 Tommy Pauly
- [Taps] Rescheduling to Feb 2 (Re: Conflict with n… Reese Enghardt