IETF Logo Mail Archive

Re: [Taps] Taps working group status and way forward

Aaron Falk <aaron.falk@gmail.com> Mon, 13 November 2023 19:19 UTC

Return-Path: <aaron.falk@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 343D8C1524DC for <taps@ietfa.amsl.com>; Mon, 13 Nov 2023 11:19:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 B9Vb4q4fL9ln for <taps@ietfa.amsl.com>; Mon, 13 Nov 2023 11:19:43 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 98040C151707 for <taps@ietf.org>; Mon, 13 Nov 2023 11:19:32 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-5079f6efd64so6347345e87.2 for <taps@ietf.org>; Mon, 13 Nov 2023 11:19:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699903171; x=1700507971; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3oiFif5BUdR11BMMuUTEtvaSLnEidQ5/9Qr9Fepi9Ww=; b=TCS+nMXBzzlTAqTBN52GhOKtqdRen7zW5rnpw/lJ6kOqLsP+5ermCJn1rnFJpF/Emq MbXWnnJHHANqO5bOeN6NMgbfa6LTq0prIIQ+odM7IMuREVYClHuod0S3IxpbTxh9jojm ZauKQzOJ9it+e4frqIFlxj7LQWBtEEL6CACIxdQQdgk5gmd05Wo34ZaQb945fFb/xHZf IM9OX1gIOxe5bUSjvrmn6uXx0j2NutMGqRSsSb56cU3MZDD1kvEK6VDce4xGh3GsAozV 23UERA5UOPoTFnWCOYCvBCfSL7kBju9qM+g73148xU1QDHrP+7clHVkvih9eNY5dA1mF +Twg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699903171; x=1700507971; 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=3oiFif5BUdR11BMMuUTEtvaSLnEidQ5/9Qr9Fepi9Ww=; b=DT1B1ky3pzAsGYyqaj53QF5Mf8zqr/m2IFbu3oEHD5YO0nL5uS6tVm2uS+OsJJXLvi 4w2fXaXoRqzrbBk7io3d6TYcnSCMqW5Am/bgUP3L5ZZbf1v3l/mdLA0hLLBn1KbMHF+O PeKgdJsxAJjaKTgG6/tX/K25sr/jmOZGgRqmTf0HFbACU7PuCt5/u7ERr8cS5n2BhmT/ Orzs/ycH+c/e6FqdWlw12iPOaaj/8ZO/y2yJN8Y9Fft91eK4/Djf4LxczbjcKuR6sGxe 4lQgeig3gTB7AJXjWA3ueD+9lqLX9rQoRkHe7JIAxS2MbfYuo39oGneoqH7lxm6TtCAH 7VGA==
X-Gm-Message-State: AOJu0YxL2W1orjya4HIj7dy4lk1FI98jLA4M0lwbiYAvs7lSbHuC3GYC idj3di1qQeEttvFDvahlCjDnFuXVuAQm5rQCiWU=
X-Google-Smtp-Source: AGHT+IG4DEzYr2WH0D8Cfbk+IR/JfWfudcNY8qp9eosddGKFUCh93SpLB+Zjz+L74rsQYnovpuuwCmHe7KldR88WdbU=
X-Received: by 2002:a19:4f47:0:b0:4fb:7559:aea3 with SMTP id a7-20020a194f47000000b004fb7559aea3mr4926424lfk.39.1699903170418; Mon, 13 Nov 2023 11:19:30 -0800 (PST)
MIME-Version: 1.0
References: <CAEh=tccp05Z+fUTfO5yLbzPeA2YO+zAePk1WeJwe9Je4mmtSHw@mail.gmail.com>
In-Reply-To: <CAEh=tccp05Z+fUTfO5yLbzPeA2YO+zAePk1WeJwe9Je4mmtSHw@mail.gmail.com>
From: Aaron Falk <aaron.falk@gmail.com>
Date: Mon, 13 Nov 2023 12:19:20 -0700
Message-ID: <CAD62q9XKWKoZxbpWgN5dDmpbSqCD-YJnvJDD5+yGnzgXQMykEA@mail.gmail.com>
To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Cc: taps WG <taps@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a01eb0060a0d8cb2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/xfIxc0G0z6XdQ0P2kDHi_6gZcRo>
Subject: Re: [Taps] Taps working group status and way forward
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, 13 Nov 2023 19:19:47 -0000

Thanks, Zahed.  It's been a long road and I'm gratified the (publication)
end is in sight.  The TAPS BoF was scheduled in January 2014 so it's been
just about exactly a decade this work has been in the IETF.  Thanks to all
for your longtime commitment to this effort.

--aaron

On Mon, Nov 13, 2023 at 8:43 AM Zaheduzzaman Sarker <
zahed.sarker.ietf@gmail.com> wrote:

> Hello working group,
>
> It is a great pleasure to see that the final deliverables under our
> current charter have been worked out and moved to the final stages of
> publication. The three documents - architecture, interface and
> implementation, are in IESG evaluation. The comments and discusses are
> being addressed and hopefully we will approve them soon.
>
> We also have been discussing potential new works and rechartering of this
> working group for a while. Those discussions didn't really create huge
> interest and enthusiasm to take in new works. One of the prominent idea was
> about QUIC mapping on TAPS. I have talked with those were interested, and
> my view is that we need more motivation to do that, especially as the QUIC
> implementation and improvements are still undergoing, this has to be
> motivated from QUIC implementers point of views that the QUIC mapping will
> be used and required. From that point of view, if the interest grows in
> future then QUIC working group would be best place to do that, or we can
> create a working group just to focus on that deliverable.
>
> With the current status of this working group, I don't see any need for
> rechartering now and I have decided to close this working group after the
> current three documents are published. This means, we will not take any new
> working group item under the current charter. The working group will remain
> open till we publish the architecture, interface and implementation
> documents.
>
> I am proud of the works that have been done in TAPS working group and
> looking forward to see TAPS in action in the industrial implementations.
> Let's hope the developers utilizes the true potential of TAPS standards.
>
> I would like to take this opportunities to thank all the working group
> participants and chairs and previous AD for doing a great job.
>
> Please feel free to send any feedback to me.
>
> Cheers,
>
> Zahed
> Your responsible transport AD
>
>
>
>
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
>

v2.23.0 | Report a Bug | By Email