[Taps] Last Call: <draft-ietf-taps-arch-17.txt> (An Architecture for Transport Services) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 31 March 2023 01:25 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: Zaheduzzaman.Sarker@ericsson.com, draft-ietf-taps-arch@ietf.org, michawe@ifi.uio.no, taps-chairs@ietf.org, taps@ietf.org
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <168022590299.28684.10139253009510901093@ietfa.amsl.com>
Date: Thu, 30 Mar 2023 18:25:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/PGwfK6pnAbLFQ5gs6dCSGKNyNiU>
Subject: [Taps] Last Call: <draft-ietf-taps-arch-17.txt> (An Architecture for Transport Services) to Proposed Standard

The IESG has received a request from the Transport Services WG (taps) to
consider the following document: - 'An Architecture for Transport Services'
  <draft-ietf-taps-arch-17.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2023-04-14. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document describes an architecture for exposing transport
   protocol features to applications for network communication, a
   Transport Services system.  The Transport Services Application
   Programming Interface (API) is based on an asynchronous, event-driven
   interaction pattern.  This API uses messages for representing data
   transfer to applications, and describes how implementations can use
   multiple IP addresses, multiple protocols, and multiple paths, and
   provide multiple application streams.  This document further defines
   common terminology and concepts to be used in definitions of a
   Transport Service API and a Transport Services implementation.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-taps-arch/



No IPR declarations have been submitted directly on this I-D.

[Taps] Last Call: <draft-ietf-taps-arch-17.txt> (… The IESG