I-D Action: draft-ietf-taps-arch-19.txt

internet-drafts@ietf.org Thu, 09 November 2023 10:14 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD8DC151540; Thu, 9 Nov 2023 02:14:43 -0800 (PST)
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
Subject: I-D Action: draft-ietf-taps-arch-19.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 11.14.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <169952488382.40204.3989546290946380841@ietfa.amsl.com>
Date: Thu, 09 Nov 2023 02:14:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/-jTwkO8Qg3OpFVFU_pZM-Jvtdwk>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Nov 2023 10:14:43 -0000

Internet-Draft draft-ietf-taps-arch-19.txt is now available. It is a work item
of the Transport Services (TAPS) WG of the IETF.

   Title:   Architecture and Requirements for Transport Services
   Authors: Tommy Pauly
            Brian Trammell
            Anna Brunstrom
            Godred Fairhurst
            Colin Perkins
   Name:    draft-ietf-taps-arch-19.txt
   Pages:   35
   Dates:   2023-11-09

Abstract:

   This document describes an architecture for exposing transport
   protocol features to applications for network communication.  This
   system exposes transport protocol features to applications for
   network communication.  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 a Transport Services
   Implementation can use multiple IP addresses, multiple protocols, and
   multiple paths, and provide multiple application streams.  This
   document provides the architecture and requirements.  It 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-19.html

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

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