IETF Logo Mail Archive

[Taps] Will schedule interim after IETF 116 (Re: Heads-up: Should we conclude TAPS after the three docs are done?)

Reese Enghardt <ietf@tenghardt.net> Fri, 17 March 2023 17:18 UTC

Return-Path: <ietf@tenghardt.net>
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 C4143C14F749 for <taps@ietfa.amsl.com>; Fri, 17 Mar 2023 10:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BCKVXNg9zWXE for <taps@ietfa.amsl.com>; Fri, 17 Mar 2023 10:17:57 -0700 (PDT)
Received: from mail.hemio.de (mail.hemio.de [136.243.12.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAF39C14F747 for <taps@ietf.org>; Fri, 17 Mar 2023 10:17:56 -0700 (PDT)
Received: from user.client.invalid (localhost [136.243.12.180]) by mail.hemio.de (Postfix) with ESMTPSA id 293C3B2 for <taps@ietf.org>; Fri, 17 Mar 2023 18:17:54 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tenghardt.net; s=20170414; t=1679073474; bh=0ZYgmg2BHhrtl5F88/Pb0cq/mA7ST3BGKizby/pbHUg=; h=Date:Subject:To:References:From:In-Reply-To:From; b=DqqwXxEZ6+/fSTs2ioEF0Q6IbwzJeuKRj9CWEZVFY0YkkPO2NFOwuK/E/q/1zkvYR BA9AaweIavu0rJ+GQg6szZW/ZGX/vO7g7JB1ZyFOf5xhQZ9A1tquRdcHJcr3Q5OYVt XGpjox3zWxB/ACsXwFPoaioweRSq0fNpnv5TkqyZ+5n7B0+PPilfyLa1UNa2IydWRv HaNFndVkIS4uemGr97Amy0bXo12aNyGZgyR8J8l+42O5bSNkv7FNvaIM8kKgq/dL/N ykShVZEN0y/zqQU2O5CAUzX9Gnc5a3oQswcIjgm7DrrltiY/yZcwggvcE6R9vFyWZq 2YcQIfFjijHXQ==
Message-ID: <b1543349-2b21-e666-2f2f-10750f732f5f@tenghardt.net>
Date: Fri, 17 Mar 2023 10:17:51 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
Content-Language: en-US
To: taps@ietf.org
References: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net> <CABKfq-ZyQYB_A1SS3hfstLnQwdFEmvQtxzQBVb4A9Gu+vkJWrg@mail.gmail.com>
From: Reese Enghardt <ietf@tenghardt.net>
In-Reply-To: <CABKfq-ZyQYB_A1SS3hfstLnQwdFEmvQtxzQBVb4A9Gu+vkJWrg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/4yR9S2DndhU_QXFAjz0lWCv9A74>
Subject: [Taps] Will schedule interim after IETF 116 (Re: Heads-up: Should we conclude TAPS after the three docs are done?)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 17 Mar 2023 17:18:01 -0000

Hi all,

Thanks all for your input.

I will reach out in early April to schedule a TAPS virtual interim 
meeting to discuss the questions raised in this thread.

Please let the chairs know if you have any additional input.

Best,
Reese

v2.23.0 | Report a Bug | By Email