IETF Logo Mail Archive

Re: [Taps] Conflict with next meeting - Jan 26

Colin Perkins <csp@csperkins.org> Sun, 16 January 2022 23:53 UTC

Return-Path: <csp@csperkins.org>
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 568863A0B25 for <taps@ietfa.amsl.com>; Sun, 16 Jan 2022 15:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=csperkins.org
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 hx-DmLPqTTIZ for <taps@ietfa.amsl.com>; Sun, 16 Jan 2022 15:52:58 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 B50F73A0B29 for <taps@ietf.org>; Sun, 16 Jan 2022 15:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=uRc18KLIlsKP8AuobAp0Wh7CUyqGrOfw2/zgBiwJSfM=; b=yVALuhHqDVcsduy6MjqrwabxOf bzUwROVE5dNf/LJ6bEFj2U3TD2dpeFJy2OnV1TptBP02rkxqZxoWF7bcexmEQJWLL5JIHSmpzfRQB 5uoQ1alGbJQv7pRva5L1c40BYSWv5C7wi7/1T6tgxfBagpc9WLIj8e0TphryadeXqMza+5kVByNx/ 8+xJ110FJFqc5lpzrEBC9Qsx7vzeqmbecSj8Igw5wqKEJNPAlkY9aemEtpytFc9CvhaBCBQiT6oWw I2dIeb3M9nBWaFy5knIxAj4hgCn9N8Z8cxhCYF7asvxV6+LHgeMHnSNTohm6AdNxeqztmkZUWqDkM N9KTZKcQ==;
Received: from [81.187.2.149] (port=32967 helo=[192.168.0.67]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1n9FKO-0003DX-2B; Sun, 16 Jan 2022 23:52:56 +0000
From: Colin Perkins <csp@csperkins.org>
Message-Id: <F64EACBA-A4A9-42A8-B056-193EB5290D49@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7437E58F-2BEB-488A-9B37-0182E2F897F3"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Sun, 16 Jan 2022 23:52:46 +0000
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.3445.104.21)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/hUHjQjqZQ0E-QoxjvhpR-A3Cgbg>
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: Sun, 16 Jan 2022 23:53:05 -0000

I’ll definitely miss the first hour; unclear about the second.
Colin



> On 15 Jan 2022, at 21: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’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

v2.23.0 | Report a Bug | By Email