Re: [Taps] Heads-up: Should we conclude TAPS after the three docs are done?

"Philipp S. Tiesel" <phils@in-panik.de> Thu, 16 March 2023 15:02 UTC

Return-Path: <phils@in-panik.de>
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 2486FC15952A for <taps@ietfa.amsl.com>; Thu, 16 Mar 2023 08:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.893
X-Spam-Level:
X-Spam-Status: No, score=-6.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 1acx6Yp9TZ-f for <taps@ietfa.amsl.com>; Thu, 16 Mar 2023 08:02:48 -0700 (PDT)
Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (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 1DB68C1522CD for <taps@ietf.org>; Thu, 16 Mar 2023 08:02:40 -0700 (PDT)
X-Envelope-From: phils@in-panik.de
Received: from x-berg.in-berlin.de (x-change.in-berlin.de [217.197.86.40]) by einhorn.in-berlin.de with ESMTPS id 32GF2ZqB3641792 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 16 Mar 2023 16:02:35 +0100
Received: from p200300ed5f042e00257f62ee7bd4cfa7.dip0.t-ipconnect.de ([2003:ed:5f04:2e00:257f:62ee:7bd4:cfa7] helo=smtpclient.apple) by x-berg.in-berlin.de with esmtpsa (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <phils@in-panik.de>) id 1pcp7i-0000Iz-Mn; Thu, 16 Mar 2023 16:02:34 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: "Philipp S. Tiesel" <phils@in-panik.de>
In-Reply-To: <49921147-8321-7ffc-1dd6-1ca727bbd511@erg.abdn.ac.uk>
Date: Thu, 16 Mar 2023 16:02:23 +0100
Cc: Michael Welzl <michawe@ifi.uio.no>, Reese Enghardt <ietf@tenghardt.net>, "taps@ietf.org" <taps@ietf.org>, "taps-chairs@ietf.org" <taps-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <90047740-F28D-4C9B-9D16-1A4DD03089DD@in-panik.de>
References: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net> <759B53CA-7172-488C-A2B3-B426E3988C30@ifi.uio.no> <49921147-8321-7ffc-1dd6-1ca727bbd511@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/yNWPDCL99Swa5EVL4pqSEGMEuYg>
Subject: Re: [Taps] 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: Thu, 16 Mar 2023 15:02:52 -0000

Hi, 

> On 15. Mar 2023, at 22:07, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> 
> On 15/03/2023 20:52, Michael Welzl wrote:
>> Hi !
>> 
>> I would love to have an interim. These are the things that I personally would like to discuss:
>> 1) what could we now do to foster deployment of this?
>> 2) is anyone really planning to write an http mapping document, ever?  this would have to be (and should be easy for!) someone with the right implementation experience…….   ahem…
>> 3) like 2), but s/http/quic
>> 
>> If the WG closes, where else could 2) and 3) happen?  Does this relate to item 1) somehow?
>> 
>> If everyone just shrugs their shoulders to all of these questions (as I do), I guess this could be a short interim followed by closing the group. Just my 2 cents.
>> 
>> Cheers,
>> Michael
> 
> I think we previously said we could fo 2,3 after we had the base drafts published - I expect that is going to be soon, and I think once that is done we ought to have that interim and talk about this!
> 
> Gorry

I fully agree, we should have an interim to see whether we have a critical mass to work on mapping documents for HTTP and QUIC. I am willing to contribute there, but that is only of limited use as I have no implementation experience for QUIC.  

AVE!
Philipp
> 
>> 
>>> On Mar 15, 2023, at 4:35 PM, Reese Enghardt <ietf@tenghardt.net> wrote:
>>> 
>>> Dear TAPS,
>>> 
>>> As we are moving towards finishing the three core documents, the next step will be to recharter or conclude.
>>> 
>>> We have talked about possible further milestones related to mapping documents, and we have a few related issues on the Github (https://github.com/ietf-tapswg/api-drafts/issues?q=is%3Aissue+is%3Aopen+label%3Amappings).
>>> 
>>> However, we have not seen much activity on this topic since IETF 113, and we have no related currently active documents.
>>> 
>>> I wanted to give you a heads-up that, given this state, 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.
>>> 
>>> Nothing has been decided yet, and we will be happy to discuss this question.
>>> 
>>> TAPS is not meeting at IETF 116, but we can consider scheduling a virtual interim meeting or a WG meeting at IETF 117 if we have content for a fruitful discussion.
>>> 
>>> Please let me know your thoughts.
>>> 
>>> Best,
>>> Reese
>>> 
>>> _______________________________________________
>>> 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
> 
> 
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps