From nobody Mon Jan 17 18:42:19 2022 Return-Path: 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 B22823A1219 for ; Mon, 17 Jan 2022 18:42:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.813 X-Spam-Level: X-Spam-Status: No, score=-2.813 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, NICE_REPLY_A=-0.714, 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=tenghardt.net 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 9Wqt-CBJTNKl for ; Mon, 17 Jan 2022 18:42:13 -0800 (PST) Received: from mail.hemio.de (mail.hemio.de [136.243.12.180]) (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 1DA243A12B0 for ; Mon, 17 Jan 2022 18:42:12 -0800 (PST) Received: from user.client.invalid (localhost [136.243.12.180]) by mail.hemio.de (Postfix) with ESMTPSA id F1D18AA for ; Tue, 18 Jan 2022 03:42:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tenghardt.net; s=20170414; t=1642473730; bh=zAmLN6WpqPIlcWtb6toUh3PGJ1hwgVYa/5nq63a4eKI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=FbvMggMSRCbXZ45vXBpbLsg8bCSMDEpoQgewRCPlkSHWk5yZhf3LHrnWcje7p6Uci Otjo9MOnXm2ITDKoUd7jaEtQmdwlFFk0pYkggd+uteJrt6b2k70hqJgUc40m06w5hd Sz3IkgHQsvIDpERN2HKEbtk7gs9/rXw5Y/GRyDEAp14RNNLdbkXu8eai3nPE2Ms9+X VbZ4nSsPaW8hqlN1f6TRyZG5zpXJPSJZSKFQsZemhtJ8hfGBu5JWsz+wTwh9XSSs/X r28mgAIKNtA7NTzsxWiRhsZZbPGiRolqBR4HsqR1JeZQPY5+9klPu+jOtRDl6flK2P 2g26GNbReQfQQ== To: taps@ietf.org References: <640F223D-ACCF-47FB-A131-4C3880AC3193@ericsson.com> From: Reese Enghardt Message-ID: <475873c8-313b-1846-4b4f-fd8be8347a93@tenghardt.net> Date: Mon, 17 Jan 2022 18:42:07 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Archived-At: 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2022 02:42:18 -0000 I can still attend on Jan 26, and Feb 2 would also work for me. Best, Reese On 1/15/22 1:26 PM, Aaron Falk wrote: > 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 > > 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 > https://www.ietf.org/mailman/listinfo/taps > > > > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps