<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hurtig-tsvwg-transport-apis" target="https://datatracker.ietf.org/doc/html/draft-hurtig-tsvwg-transport-apis-00">
   <front>
      <title>Transport APIs</title>
      <author initials="P." surname="Hurtig" fullname="Per Hurtig">
         <organization>Karlstad University</organization>
      </author>
      <author initials="S." surname="Gjessing" fullname="Stein Gjessing">
         <organization>University of Oslo</organization>
      </author>
      <author initials="M." surname="Welzl" fullname="Michael Welzl">
         <organization>University of Oslo</organization>
      </author>
      <author initials="M." surname="Sustrik" fullname="Martin Sustrik">
         </author>
      <date month="December" day="15" year="2013" />
      <abstract>
	 <t>   Commonly used networking APIs are currently limited by the transport
   layer&#x27;s inability to expose services instead of protocols.  An API/
   application/user is therefore forced to use exactly the services that
   are implemented by the selected transport.  This document surveys
   networking APIs and discusses how they can be improved by a more
   expressive transport layer that hides and automatizes the choice of
   the transport protocol.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hurtig-tsvwg-transport-apis-00" />
   
</reference>
