IETF Logo Mail Archive

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

Martin Duke <martin.h.duke@gmail.com> Tue, 25 April 2023 19:16 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 92DF8C1524A3; Tue, 25 Apr 2023 12:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_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=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 ft7MSu-z037i; Tue, 25 Apr 2023 12:16:25 -0700 (PDT)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (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 9BE37C1522D3; Tue, 25 Apr 2023 12:16:25 -0700 (PDT)
Received: by mail-ua1-x931.google.com with SMTP id a1e0cc1a2514c-77215852592so1832099241.2; Tue, 25 Apr 2023 12:16:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682450184; x=1685042184; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MkJu8Ju9h5HRIndRThVbneOhNLMrH4n/VrffD+WZDjk=; b=rj/oXUHclsqCGLfewlF3fBPpJ6ciUwOEcscY7hNl2pQgFZZLZvtKPgCNbbMqpQB9IU bIz9k7Ki28bX091yrbk1tU97+aUowWmwH7YsHBxFejSP+9B8yNnczdJAKZ7yYeqWDpnr BCw/8kofZkClqTkKbuUZtSPPzCp0CavU+QvWueaskDf/GaJoN3SpiCWCPpqD/yT8XUR9 b97HmKTYuIaRAomTVxE/ZCm+YKlEpKyKxigUVYgLnkHVFJpWVqQDWUN6pLossSVE/huF xWPG8YSaCr+5FKbSG0GSFfeyvIqH/F5ygWvppA+kgxGr5q+EfVh+olh0ly1RAYmggyYh EXzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682450184; x=1685042184; 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=MkJu8Ju9h5HRIndRThVbneOhNLMrH4n/VrffD+WZDjk=; b=IiqLxG66mnjw4r99N1v5pxoNxPtr2DgX85n209eLMltzX1DOuGyBWHdsb204dwb9dK F6PHShb0zRuaKmAEoqbtU+moIJZtkItx7wIqfVK5IXlEMWj6R86JklU83t8jmkuM5Pa0 b0riIAKVYPzwg6e3QOfUC4L54I3hs78T33blC5NVRAAkf461G1+OLHs7wdhcURlUnpz1 9Tk0DFPPzVwwVNAWBDkHl431Fk3TX8+8fIfN4Y+usvZA4nsgmfke2oYNF3NRUwzoV55c uAeJKmbAqpGLQLqo6UUA4xUt1V93wKJ1LTD/Ejahi1M/pWoG9C5asNDIuQqY01K6aCKR aRMg==
X-Gm-Message-State: AAQBX9celtjRq9/uCdEvRXO44mHysA6MKe60KUUUevt9Tg73C8SNRS1y IMaZqn2kbKTKMc51ogixAqpaJOCxpfZ6+krIJkO5gHYY
X-Google-Smtp-Source: AKy350bV9cubpKK/0PXyUFDSlRY1Tj9jAqxB6k/vMbZM0XKM5orv9rx1FGa+eyajjSJPmFBOAcmmNSYCuOw7x6dbWkk=
X-Received: by 2002:a05:6102:34d0:b0:42e:69e9:e9cc with SMTP id a16-20020a05610234d000b0042e69e9e9ccmr7840595vst.11.1682450184331; Tue, 25 Apr 2023 12:16:24 -0700 (PDT)
MIME-Version: 1.0
References: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net> <CABKfq-ZyQYB_A1SS3hfstLnQwdFEmvQtxzQBVb4A9Gu+vkJWrg@mail.gmail.com>
In-Reply-To: <CABKfq-ZyQYB_A1SS3hfstLnQwdFEmvQtxzQBVb4A9Gu+vkJWrg@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 25 Apr 2023 12:16:13 -0700
Message-ID: <CAM4esxTkPiV-9vffhtZRh++Ua5xQp+SVf3X3Ppo05z0AmfJfzQ@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="00000000000096e8c705fa2df5ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/a5_VTwRHvbY7sJvn9QIlJm0S8NM>
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: Tue, 25 Apr 2023 19:16:29 -0000

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
>

v2.23.0 | Report a Bug | By Email