From nobody Sun Jan 16 01:15:27 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 A6E1B3A0F2F for ; Sun, 16 Jan 2022 01:15:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trammell.ch 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 WAcmOlyhOdLB for ; Sun, 16 Jan 2022 01:15:19 -0800 (PST) Received: from smtp-42a8.mail.infomaniak.ch (smtp-42a8.mail.infomaniak.ch [84.16.66.168]) (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 8A57E3A0F35 for ; Sun, 16 Jan 2022 01:15:19 -0800 (PST) Received: from smtp-3-0001.mail.infomaniak.ch (unknown [10.4.36.108]) by smtp-3-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4Jc8Wm6HFczMptNf; Sun, 16 Jan 2022 10:15:16 +0100 (CET) Received: from smtpclient.apple (unknown [IPv6:2a02:169:17b2:0:f1de:8cf4:4443:93bc]) by smtp-3-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 4Jc8Wm4TLyzlhMBY; Sun, 16 Jan 2022 10:15:16 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=trammell.ch; s=20191114; t=1642324516; bh=YeMPRLej7OAaScPju+HC0qkL5qgpmDwlVkrMwPrLqEQ=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=ntWtkokmo7HHUFu1kNmxcV95/RM5UU7iySkes0vzAI6E2d3Az7RgftsD4R2AOg8/y JowEZWkGMJ7Ajm2F5Lo0sGkIgM4ti5nyBqL15GLJIGqB/MXV6GnYu4T44DgRyUVRIl gTh88IJXstBPdtxXY8wqt8JXc8leeD36am0aQnHc= From: "Brian Trammell (IETF)" Message-Id: <5596D659-4DED-4B6A-8C62-4990E4D3C9CF@trammell.ch> Content-Type: multipart/alternative; boundary="Apple-Mail=_44E7CBE1-C29F-4156-B07C-2858ADE4DE77" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Date: Sun, 16 Jan 2022 10:15:16 +0100 In-Reply-To: Cc: Mirja Kuehlewind , "taps@ietf.org" To: Aaron Falk References: <640F223D-ACCF-47FB-A131-4C3880AC3193@ericsson.com> X-Mailer: Apple Mail (2.3654.120.0.1.13) 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: Sun, 16 Jan 2022 09:15:25 -0000 --Apple-Mail=_44E7CBE1-C29F-4156-B07C-2858ADE4DE77 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m planning on being there. If we reschedule, pushing to 2 Feb = will work for me, but after that my next available Wednesday at the = normal slot is 2 Mar. Cheers, Brian > On 15 Jan 2022, at 22:26, Aaron Falk wrote: >=20 > Can folks who are planning to attend the TAPS interim on Jan 26 at = 11am EST reply to this message? Let=E2=80=99s see if we still have a = critical mass. >=20 > =E2=80=94aaron >=20 > On Fri, Jan 14, 2022 at 5:26 AM Mirja Kuehlewind = > wrote: > Hi all, >=20 > 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. >=20 > 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. >=20 > Mirja >=20 >=20 >=20 > _______________________________________________ > 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 --Apple-Mail=_44E7CBE1-C29F-4156-B07C-2858ADE4DE77 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I=E2=80= =99m planning on being there. If we reschedule, pushing to 2 Feb will = work for me, but after that my next available Wednesday at the normal = slot is 2 Mar.

Cheers,

Brian

On 15 Jan 2022, at 22:26, Aaron = Falk <aaron.falk@gmail.com> wrote:

Can folks who are planning to attend the TAPS interim on Jan = 26 at 11am EST reply to this message?  Let=E2=80=99s see if we = still have a critical mass.

=E2=80=94aaron

On Fri, Jan 14, 2022 at 5:26 AM Mirja Kuehlewind = <mirja.kuehlewind=3D40ericsson.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
https://www.ietf.org/mailman/listinfo/taps
_______________________________________________
Taps = mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps

= --Apple-Mail=_44E7CBE1-C29F-4156-B07C-2858ADE4DE77--