<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.fairhurst-taps-neat" target="https://datatracker.ietf.org/doc/html/draft-fairhurst-taps-neat-01">
   <front>
      <title>The NEAT Interface to Transport Services</title>
      <author initials="G." surname="Fairhurst" fullname="Gorry Fairhurst">
         <organization>University of Aberdeen</organization>
      </author>
      <author initials="T." surname="Jones" fullname="Tom Jones">
         <organization>University of Aberdeen</organization>
      </author>
      <author initials="A." surname="Brunstrom" fullname="Anna Brunstrom">
         <organization>Karlstad University</organization>
      </author>
      <author initials="D." surname="Ros" fullname="David Ros">
         <organization>Simula Research Laboratory</organization>
      </author>
      <date month="November" day="12" year="2017" />
      <abstract>
	 <t>   The NEAT System provides an example of a system designed to implement
   the TAPS Transport Services.  This document presents the transport
   services that the NEAT User API provides to an application or upper-
   layer protocol.  It also describes primitives needed to interface to
   the NEAT Policy Manager and how policies can be adjusted to match the
   API behaviour to the properties required by an application or upper-
   layer protocol using the NEAT User API.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-fairhurst-taps-neat-01" />
   
</reference>
