IETF Logo Mail Archive

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

"Devon H. O'Dell" <dhobsd@google.com> Thu, 16 March 2023 19:26 UTC

Return-Path: <dhobsd@google.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 3CC91C14CF1D for <taps@ietfa.amsl.com>; Thu, 16 Mar 2023 12:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.597
X-Spam-Level:
X-Spam-Status: No, score=-17.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, 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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 xFFoSebVXCHL for <taps@ietfa.amsl.com>; Thu, 16 Mar 2023 12:26:03 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 6CDC2C14CEFA for <taps@ietf.org>; Thu, 16 Mar 2023 12:26:03 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id d8so1584374pgm.3 for <taps@ietf.org>; Thu, 16 Mar 2023 12:26:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; t=1678994763; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6qoCeDn6COq2+FYTcZGjACKSk8W+74LrEwVmK72eyNc=; b=OYo5f20Omr0IhMAwl4PSzV3sf0x62TCtiD6dZtIP9wurCo3VEnqsXOlykJUhwhHSR/ H5cpVDW1hhKU4kZ93x0EDV/6X8pmCwUiCxUztOOcQaXdqAEfyDy7ZAbUKhUvtGazysGt 3a3PhaIrv6l+iRuxiJWybKk8N+KuBFDMLOaLCuN34wA2EtPZS4Z4ungozMqEM9ZqH89+ Zq11zVPRS/KJua0MVYN9QVgKllQ5finVphp+jsm4OqzIXmH0Jiup72ZkCiShehR9dDx9 UJtG/b0dXR+uDqyGzlnumJL2na4iDH4pgizGQI+FCVQVl0d8jhuu+8smgS2LrpvyuI+U Jc5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678994763; 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=6qoCeDn6COq2+FYTcZGjACKSk8W+74LrEwVmK72eyNc=; b=Jqj8NHBBj454nJHxBf7ROjxTxjs7gneWpPi5dagvuaOeoOgpjmJPpfv2C16Yfd+ZRa zpk/CDoBjJ1O+QRwkNrhJCxN/lNbNgv1S1xZuodNdRRrJZTL/2UhVQ/OHhv3W399hc3+ iO6VkRoZcGMN0ZqRDjA3ug1KOzeJW6uBN12oRLHoMXiT1/1a6suVwCZS6evaykQDMBYo NCtYoOdNEK9Po2mVmgwJ0H5CsPGzv/cTFTuCclMxM8F6S7dq1+P17CSaE2eV8xiYVHz8 JuB9KrmSAio2virp1UNqTJoyoeFqjti5f+A/40Yh8IOE4dsXkhmg90XWEzJx1z3GVcD0 XDsw==
X-Gm-Message-State: AO0yUKWwZwPCLOO6MCnbxkFEFXZgcCjU8vvyiNUUtF9WRi9iHC6oa99A xbFGFsbCtpIxQzyJvelwTFa1v934KNDo1OrQ+hXXeg==
X-Google-Smtp-Source: AK7set9BdZ3q+5QIrvUCngQJ57TT91sxder4OWbQKANJ3JJN+7ugij2TY41bXB0BTtppvepPzLKozDtq6IcZiznssd0=
X-Received: by 2002:a65:43c4:0:b0:50b:217f:20dc with SMTP id n4-20020a6543c4000000b0050b217f20dcmr1163036pgp.4.1678994762503; Thu, 16 Mar 2023 12:26:02 -0700 (PDT)
MIME-Version: 1.0
References: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net>
In-Reply-To: <01ee447f-7608-703f-31cf-12dfaa68df1f@tenghardt.net>
From: "Devon H. O'Dell" <dhobsd@google.com>
Date: Thu, 16 Mar 2023 15:25:51 -0400
Message-ID: <CABKfq-ZyQYB_A1SS3hfstLnQwdFEmvQtxzQBVb4A9Gu+vkJWrg@mail.gmail.com>
To: Reese Enghardt <ietf@tenghardt.net>
Cc: "taps@ietf.org" <taps@ietf.org>, "taps-chairs@ietf.org" <taps-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000066db5005f7096e2d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/bkzqj67gpowPQz_aMkyRjRx-tc8>
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 19:26:07 -0000

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
>

v2.23.0 | Report a Bug | By Email