Re: [Taps] Doodle for Interim meeting in May 2023

Reese Enghardt <ietf@tenghardt.net> Mon, 17 April 2023 17:50 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 F394BC151522 for <taps@ietfa.amsl.com>; Mon, 17 Apr 2023 10:50:42 -0700 (PDT)
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, NICE_REPLY_A=-0.001, 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 1zcbrpbHQEid for <taps@ietfa.amsl.com>; Mon, 17 Apr 2023 10:50:38 -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 28465C151554 for <taps@ietf.org>; Mon, 17 Apr 2023 10:50:37 -0700 (PDT)
Received: from user.client.invalid (localhost [136.243.12.180]) by mail.hemio.de (Postfix) with ESMTPSA id D61D8B2 for <taps@ietf.org>; Mon, 17 Apr 2023 19:50:35 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tenghardt.net; s=20170414; t=1681753836; bh=Ah2UUPP1Pj0ITqyiJe6R7kn1X6FbKO2nPrC9JbOtuCk=; h=Date:Subject:From:To:References:In-Reply-To:From; b=PDDfPL7wMlXPFnpDaHXXllnE1dN7GdC47W0zcAHsuO4C6JRiPbLusWBlKaWfydtn0 lkanzrbSkb5QrSmXJb0QGK6eKJStt6IK1bnMVZ3Crfs3PG31Ud3oqhqCT7C6PybU4L I61B2m2le74tRwmBMyyEzNZpMXifTh22O95YePG5CPQKzsfNDVakh6DZp1jpI6xx/h nKW1oqbZQCwlI+EOf6GttJqVgKTmwMrviZkVJkJK+tiOpVrgfnc36AkH06pyhdLfQn JFU1XHYsbw/R5uHlmVI3PSHUab6SnEaIbCHya4Kt+jzxdP20s/1ZJsRwzXKnKqr4LJ +QKeyqCpVRrNQ==
Message-ID: <46aa4ce3-97ba-070e-e018-abe2409bbe06@tenghardt.net>
Date: Mon, 17 Apr 2023 10:50:32 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0
From: Reese Enghardt <ietf@tenghardt.net>
To: "taps@ietf.org" <taps@ietf.org>
References: <f770b472-ae78-53c2-c9c0-468cb3cb3d73@tenghardt.net>
Content-Language: en-US
In-Reply-To: <f770b472-ae78-53c2-c9c0-468cb3cb3d73@tenghardt.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/MNbNffFYy8OYU6h6uBQTDokMXWs>
Subject: Re: [Taps] Doodle for Interim meeting in May 2023
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: Mon, 17 Apr 2023 17:50:43 -0000

Dear TAPS,

Thank you for responding to the Doodle.

It looks like the best date is Monday May 15th, 08:00 PDT / 11:00 EDT / 
15:00 UTC / 17:00 CEST.

As mentioned, please let the chairs know if you'd like to present on any 
of the below agenda items, or if you have additional agenda items.

Looking forward to seeing you all in about a month!

Best,
Reese


On 4/11/23 08:44, Reese Enghardt wrote:
> […]
> Ideas for agenda items so far:
>
> - What can we do now to foster deployment of TAPS?
> - Implementation update
> - Discoverability/configuration
> - Mappings: QUIC, HTTP, any others?
>
> Please let the chairs know if you'd like to present on any of these. 
> If nobody presents, we'll have a free-form discussion.
>
> As mentioned in the original thread, the chairs are wondering if it'll 
> be time to conclude TAPS once the core documents have made their way 
> to the RFC editor, unless we see evidence of substantial interest and 
> activity regarding further milestones. This includes editorial activity.