[Taps] 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
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B6625C15107A; Thu, 18 Apr 2024 11:28:47 -0700 (PDT)
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>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.10.0
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/taps/AMRFrpSv3Uufjdj7EJBV0sMJKXg>
Subject: [Taps] Protocol Action: 'Architecture and Requirements for Transport Services' to Proposed Standard (draft-ietf-taps-arch-19.txt)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.39
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, 18 Apr 2024 18:28:47 -0000
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.