Re: [Taps] Conflict with next meeting - Jan 26
Tommy Pauly <tpauly@apple.com> Tue, 18 January 2022 16:33 UTC
Return-Path: <tpauly@apple.com>
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 5F7D83A09E9 for <taps@ietfa.amsl.com>; Tue, 18 Jan 2022 08:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.672
X-Spam-Level:
X-Spam-Status: No, score=-2.672 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.576, 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 (2048-bit key) header.d=apple.com
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 bcIrqWEKAepP for <taps@ietfa.amsl.com>; Tue, 18 Jan 2022 08:33:37 -0800 (PST)
Received: from rn-mailsvcp-ppex-lapp35.apple.com (rn-mailsvcp-ppex-lapp35.rno.apple.com [17.179.253.44]) (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 6487E3A09EF for <taps@ietf.org>; Tue, 18 Jan 2022 08:33:36 -0800 (PST)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp35.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp35.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 20IGU3YX027216; Tue, 18 Jan 2022 08:33:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=Mxs1ltqZCLy7eks9tDHu2BB+L1qPpfI12/noAkvAYcs=; b=OXM7fmP6rp22DePW1rbybwNzo4foo8Z74nLssvLSsOHmwbwYPWD4gBsDA1STOZZ+onjP 1yUI954oMY3/EovFGjRzVYnY6axvstE5EckFAIM86fAEON5iVkwkd2V8s0saHJe4TTZj mIac5egSrA6jeadPa6BLcZa9tMgGw85L9CKel69yfODsty9gZ2Nf8Vr/RVmBPyvq91xs 6ycIW3KPHOsvLg81dL8nyfqPpmmPszTW/F5Q58/n/tFy229zAfDRqjLbEIZOq2oAXQA+ HCFwNdrJKW0AlAVVJSgvpjURnGzkP9YrSi+rpHMqpr1LX37mQrBMQuOfFhyUiUJrs7oR 0A==
Received: from rn-mailsvcp-mta-lapp01.rno.apple.com (rn-mailsvcp-mta-lapp01.rno.apple.com [10.225.203.149]) by rn-mailsvcp-ppex-lapp35.rno.apple.com with ESMTP id 3dktp9bx5y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 18 Jan 2022 08:33:34 -0800
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) with ESMTPS id <0R5W00M0LZBYKZ80@rn-mailsvcp-mta-lapp01.rno.apple.com>; Tue, 18 Jan 2022 08:33:34 -0800 (PST)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) id <0R5W00A00Z89RP00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Tue, 18 Jan 2022 08:33:34 -0800 (PST)
X-Va-A:
X-Va-T-CD: 9ea90e61654dad0c8920388428deae70
X-Va-E-CD: eba0927130a3cd39fa0b703733c2ae2e
X-Va-R-CD: 51c82bf44641bb13624078750faa2ad7
X-Va-CD: 0
X-Va-ID: a58187b0-8ec1-48a6-b3e0-5ca48662c93a
X-V-A:
X-V-T-CD: 9ea90e61654dad0c8920388428deae70
X-V-E-CD: eba0927130a3cd39fa0b703733c2ae2e
X-V-R-CD: 51c82bf44641bb13624078750faa2ad7
X-V-CD: 0
X-V-ID: c3029a1c-e734-404e-b244-52c3039ae6dc
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-01-18_04:2022-01-17, 2022-01-18 signatures=0
Received: from smtpclient.apple (unknown [17.234.28.215]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.12.20210903 64bit (built Sep 3 2021)) with ESMTPSA id <0R5W00OI3ZBXY300@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Tue, 18 Jan 2022 08:33:34 -0800 (PST)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <A70C0A11-0489-4EC3-9E97-3836B4EAFE2F@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_709AE371-548D-42CA-AF11-454BDED546C3"
MIME-version: 1.0 (Mac OS X Mail 15.0 \(3691.0.3\))
Date: Tue, 18 Jan 2022 08:33:33 -0800
In-reply-to: <CAD62q9X-XVObCdyf04j7MnmR4UZ3fJx1-G_qAN_xK+Ly=2+v=A@mail.gmail.com>
Cc: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>, "taps@ietf.org" <taps@ietf.org>
To: Aaron Falk <aaron.falk@gmail.com>
References: <640F223D-ACCF-47FB-A131-4C3880AC3193@ericsson.com> <CAD62q9X-XVObCdyf04j7MnmR4UZ3fJx1-G_qAN_xK+Ly=2+v=A@mail.gmail.com>
X-Mailer: Apple Mail (2.3691.0.3)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.816 definitions=2022-01-18_04:2022-01-17, 2022-01-18 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/x0cTsMRykpJ7geI8iHPeKWj6WHQ>
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: Tue, 18 Jan 2022 16:33:41 -0000
With the ADD and IAB meetings, I don’t think I’ll be able to make it on Jan 26 — Feb 2 would be perfectly fine. Best, Tommy > On Jan 15, 2022, at 1:26 PM, 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’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> > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps
- [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