<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-taps-arch" target="https://datatracker.ietf.org/doc/html/draft-ietf-taps-arch-17">
   <front>
      <title>An Architecture for Transport Services</title>
      <author initials="T." surname="Pauly" fullname="Tommy Pauly">
         <organization>Apple Inc.</organization>
      </author>
      <author initials="B." surname="Trammell" fullname="Brian Trammell">
         <organization>Google Switzerland GmbH</organization>
      </author>
      <author initials="A." surname="Brunstrom" fullname="Anna Brunstrom">
         <organization>Karlstad University</organization>
      </author>
      <author initials="G." surname="Fairhurst" fullname="Gorry Fairhurst">
         <organization>University of Aberdeen</organization>
      </author>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <date month="March" day="29" year="2023" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-taps-arch-17" />
   
</reference>
