<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-taps-interface" target="https://datatracker.ietf.org/doc/html/draft-ietf-taps-interface-26">
   <front>
      <title>An Abstract Application Layer Interface to Transport Services</title>
      <author initials="B." surname="Trammell" fullname="Brian Trammell">
         <organization>Google Switzerland GmbH</organization>
      </author>
      <author initials="M." surname="Welzl" fullname="Michael Welzl">
         <organization>University of Oslo</organization>
      </author>
      <author initials="R." surname="Enghardt" fullname="Reese Enghardt">
         <organization>Netflix</organization>
      </author>
      <author initials="G." surname="Fairhurst" fullname="Gorry Fairhurst">
         <organization>University of Aberdeen</organization>
      </author>
      <author initials="M." surname="Kühlewind" fullname="Mirja Kühlewind">
         <organization>Ericsson</organization>
      </author>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <author initials="P. S." surname="Tiesel" fullname="Philipp S. Tiesel">
         <organization>SAP SE</organization>
      </author>
      <author initials="T." surname="Pauly" fullname="Tommy Pauly">
         <organization>Apple Inc.</organization>
      </author>
      <date month="March" day="16" year="2024" />
      <abstract>
	 <t>   This document describes an abstract application programming
   interface, API, to the transport layer that enables the selection of
   transport protocols and network paths dynamically at runtime.  This
   API enables faster deployment of new protocols and protocol features
   without requiring changes to the applications.  The specified API
   follows the Transport Services architecture by providing
   asynchronous, atomic transmission of messages.  It is intended to
   replace the BSD sockets API as the common interface to the transport
   layer, in an environment where endpoints could select from multiple
   network paths and potential transport protocols.

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