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

internet-drafts@ietf.org Mon, 13 July 2020 17: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 C23DA3A160B; Mon, 13 Jul 2020 10:53:49 -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: 7.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: taps@ietf.org
Message-ID: <159466282974.28485.17963693359369952266@ietfa.amsl.com>
Date: Mon, 13 Jul 2020 10:53:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/buacx1dOBHivEXkjHyiZtq83-zY>
Subject: [Taps] I-D Action: draft-ietf-taps-arch-08.txt
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 13 Jul 2020 17:53:50 -0000

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

        Title           : An Architecture for Transport Services
        Authors         : Tommy Pauly
                          Brian Trammell
                          Anna Brunstrom
                          Godred Fairhurst
                          Colin Perkins
                          Philipp S. Tiesel
                          Christopher A. Wood
	Filename        : draft-ietf-taps-arch-08.txt
	Pages           : 28
	Date            : 2020-07-13

   This document describes an architecture for exposing transport
   protocol features to applications for network communication, the
   Transport Services architecture.  The Transport Services Application
   Programming Interface (API) is based on an asynchronous, event-driven
   interaction pattern.  It uses messages for representing data transfer
   to applications, and it 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
   Transport Services APIs and implementations.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at: