[Taps] I-D Action: draft-ietf-taps-arch-18.txt

internet-drafts@ietf.org Tue, 30 May 2023 09:53 UTC

Return-Path: <internet-drafts@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 1820EC151525; Tue, 30 May 2023 02:53:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: taps@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 10.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <168544040608.13149.8516617743932523267@ietfa.amsl.com>
Date: Tue, 30 May 2023 02:53:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/nryYIN_p_yrMJ7gSsRd8BMUGW3M>
Subject: [Taps] I-D Action: draft-ietf-taps-arch-18.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: Tue, 30 May 2023 09:53:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts
directories. This Internet-Draft is a work item of the Transport Services
(TAPS) WG of the IETF.

   Title           : An Architecture for Transport Services
   Authors         : Tommy Pauly
                     Brian Trammell
                     Anna Brunstrom
                     Godred Fairhurst
                     Colin Perkins
   Filename        : draft-ietf-taps-arch-18.txt
   Pages           : 33
   Date            : 2023-05-30

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 IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-arch/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-taps-arch-18.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-taps-arch-18

Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts