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

Martin Duke <martin.h.duke@gmail.com> Mon, 01 May 2023 16:07 UTC

Return-Path: <martin.h.duke@gmail.com>
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 75605C1524DB; Mon, 1 May 2023 09:07:36 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1tZ0dxpUpk6n; Mon, 1 May 2023 09:07:32 -0700 (PDT)
Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 1191EC1595E5; Mon, 1 May 2023 09:07:32 -0700 (PDT)
Received: by mail-vk1-xa2c.google.com with SMTP id 71dfb90a1353d-4403744aa44so947230e0c.2; Mon, 01 May 2023 09:07:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682957251; x=1685549251; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1VBJqCpSOsYo6sGrcZyHQGA7rZ0SSzmwj7aIln+x0xU=; b=qX5gU2bNzx9/v94Fpt1S3XgJS1enI3UQWYkv56T6rBkVYunnRoQkwjvEGNrNIKd1FA JSnciLRco56u4ETsEonJEvMiPI1QdhsnLqIvrA+PmlaCBkotdHKNbBD/6g8iRUtvo931 2RNx5+UHLTVzMlX4pjdPE6on2X7rosAyI2ZFCjQgOa3Zz2QtABwCNGe4aQAIi+GIQDIe o1v3kN0onFUZJowv4QKT8shTgxQ7AQk4kgy0v7A5SxYmqkfHKIJ5dmbBE6bFo+vZCuGQ bXk9wtFYO5M3p/SZtXp6qm3wizjc6aU5VxnkgZpRBlMW5r49FGmArUJrduB2LxXmCHUz NwJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682957251; x=1685549251; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=1VBJqCpSOsYo6sGrcZyHQGA7rZ0SSzmwj7aIln+x0xU=; b=E5Mk4oLD9wk8dl91pukTSc7Nox2o9+AmJgGL5v4tT/0sD1ISaTH2DDjeD49gctuuKt ENTsf12F4P/zmsIhxNW5XQPvky2LaEWG/QI/DANcdFrwNa8iFjv3OZWB7FmGd9ec6T9Q /RrMIK699yvwoKj7FJV0aIedsjur1Bqc7lPXijPKigfLLL0Ef2N28uT9pH/fQtHLIif6 qGlwbnIJoGYC8Qc4lrlnxyrjyXpKHxsKBNdnx7ExPTyXruP0553PniM7/Cp8BFa65/to Ef6zxw30NUWIBdnrW06Tih2SNrrF119bu9C+gZPLkQmTi4Mfv5N8PoXdvcs24pEHkLzz lQ6w==
X-Gm-Message-State: AC+VfDztKAkS3NY5zzqycnifjbiexJ1ImoE7FUCT/Slzyn7Hg8mTaRf8 GeKyTzMjzj7hRsO/egXlwSdbO+c/m0NUaIpiknbFVIS0
X-Google-Smtp-Source: ACHHUZ70QkrDta9FvpUuuthZOWMQzo9x231r88ORl0Yrh4CSZg7S7cBsLB2Y+dDL33lg4trQrutqtqyApPSQJ7KWRYU=
X-Received: by 2002:a1f:4544:0:b0:440:499:7747 with SMTP id s65-20020a1f4544000000b0044004997747mr3828977vka.10.1682957250609; Mon, 01 May 2023 09:07:30 -0700 (PDT)
MIME-Version: 1.0
References: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net> <CABKfq-ZyQYB_A1SS3hfstLnQwdFEmvQtxzQBVb4A9Gu+vkJWrg@mail.gmail.com> <CAM4esxTkPiV-9vffhtZRh++Ua5xQp+SVf3X3Ppo05z0AmfJfzQ@mail.gmail.com>
In-Reply-To: <CAM4esxTkPiV-9vffhtZRh++Ua5xQp+SVf3X3Ppo05z0AmfJfzQ@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 01 May 2023 09:07:15 -0700
Message-ID: <CAM4esxS6W9_dJrY92NCZ1CLTQ=7RB_7M_5enp5pqLnbRWJxYTg@mail.gmail.com>
To: "Devon H. O'Dell" <dhobsd=40google.com@dmarc.ietf.org>
Cc: Reese Enghardt <ietf@tenghardt.net>, "taps@ietf.org" <taps@ietf.org>, "taps-chairs@ietf.org" <taps-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001845ff05faa4059c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/phnVTV9OlZzMKtFNh2EgUqawzCk>
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: Mon, 01 May 2023 16:07:36 -0000

Addendum:

I got a private note that there is at least one other potentially major
TAPS project going on, though they are not ready to go public. So I
withdraw that part of my comment.

On Tue, Apr 25, 2023 at 12:16 PM Martin Duke <martin.h.duke@gmail.com>
wrote:

> I'm glad we did this work, but the energy here has gotten pretty low and I
> wonder if it's worth doing extensions if there's exactly 1 deployment of
> any significance.
>
> Furthermore, if the only thing people are excited about is a QUIC mapping,
> I'd rather we just do it in QUICWG than have the overhead of a WG for this.
>
> On Thu, Mar 16, 2023 at 12:26 PM Devon H. O'Dell <dhobsd=
> 40google.com@dmarc.ietf.org> wrote:
>
>> Hi all,
>>
>> Most of my questions / comments / contributions have been about
>> discoverability / configuration, and I wondered if there'd be interest in
>> exploring the policy and configuration space for Transport Services. I'm
>> thinking along the lines of APIs for configuration tools to manage or
>> discover policy (e.g. enumerate local endpoints, gather properties, collect
>> / set resolver configurations). My apologies for having missed the last
>> several meetings, but would love to discuss this at the next interim.
>>
>> Kind regards,
>>
>> --dho
>>
>> On Wed, Mar 15, 2023 at 11:35 AM 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
>>
>