Re: [Taps] Heads-up: Should we conclude TAPS after the three docs are done?
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 15 March 2023 21:07 UTC
Return-Path: <gorry@erg.abdn.ac.uk>
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 4B732C16B5A2; Wed, 15 Mar 2023 14:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Qf9SYkwsQFan; Wed, 15 Mar 2023 14:07:27 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id E413DC14CF0D; Wed, 15 Mar 2023 14:07:26 -0700 (PDT)
Received: from [192.168.1.64] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id ED1A71B0019B; Wed, 15 Mar 2023 21:07:17 +0000 (GMT)
Message-ID: <49921147-8321-7ffc-1dd6-1ca727bbd511@erg.abdn.ac.uk>
Date: Wed, 15 Mar 2023 21:07:17 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
To: Michael Welzl <michawe@ifi.uio.no>, Reese Enghardt <ietf@tenghardt.net>
Cc: "taps@ietf.org" <taps@ietf.org>, "taps-chairs@ietf.org" <taps-chairs@ietf.org>
References: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net> <759B53CA-7172-488C-A2B3-B426E3988C30@ifi.uio.no>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
In-Reply-To: <759B53CA-7172-488C-A2B3-B426E3988C30@ifi.uio.no>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/SxuDnqcsYlr5CiwsQ0B6Ur-QmAY>
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: Wed, 15 Mar 2023 21:07:29 -0000
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 > >> 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] Heads-up: Should we conclude TAPS after th… Reese Enghardt
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Michael Welzl
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Gorry Fairhurst
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Tommy Pauly
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Philipp S. Tiesel
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Devon H. O'Dell
- [Taps] Will schedule interim after IETF 116 (Re: … Reese Enghardt
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Martin Duke
- Re: [Taps] Heads-up: Should we conclude TAPS afte… Martin Duke