Protocol Action: 'Architecture and Requirements for Transport Services' to Proposed Standard (draft-ietf-taps-arch-19.txt)

The IESG <iesg-secretary@ietf.org> Thu, 18 April 2024 18:28 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>
Subject: Protocol Action: 'Architecture and Requirements for Transport Services' to Proposed Standard (draft-ietf-taps-arch-19.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-taps-arch@ietf.org, michawe@ifi.uio.no, rfc-editor@rfc-editor.org, taps-chairs@ietf.org, taps@ietf.org, zahed.sarker.ietf@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <171346492774.36072.13609411550382211156@ietfa.amsl.com>
Date: Thu, 18 Apr 2024 11:28:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/xSvuxBqBunzYnkCDuPoqEwvJU-c>

The IESG has approved the following document:
- 'Architecture and Requirements for Transport Services'
  (draft-ietf-taps-arch-19.txt) as Proposed Standard

This document is the product of the Transport Services Working Group.

The IESG contact persons are Zaheduzzaman Sarker and Francesca Palombini.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-arch/




Technical Summary

   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.

Working Group Summary

   This document reached broad agreement, with contributions from most active WG
members. 

Document Quality

   This draft has benefited from broad TSV area review within the WG
itself, and has had secdir and artart early review.

Personnel

   The Document Shepherd for this document is Michael Welzl. The
   Responsible Area Director is Zaheduzzaman Sarker.

Protocol Action: 'Architecture and Requirements f… The IESG