<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tram-turnbis" target="https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-06">
   <front>
      <title>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)</title>
      <author initials="T." surname="Reddy.K" fullname="Tirumaleswar Reddy.K">
         </author>
      <author initials="A." surname="Johnston" fullname="Alan Johnston">
         </author>
      <author initials="P." surname="Matthews" fullname="Philip Matthews">
         </author>
      <author initials="J." surname="Rosenberg" fullname="Jonathan Rosenberg">
         </author>
      <date month="September" day="11" year="2015" />
      <abstract>
	 <t>   If a host is located behind a NAT, then in certain situations it can
   be impossible for that host to communicate directly with other hosts
   (peers).  In these situations, it is necessary for the host to use
   the services of an intermediate node that acts as a communication
   relay.  This specification defines a protocol, called TURN (Traversal
   Using Relays around NAT), that allows the host to control the
   operation of the relay and to exchange packets with its peers using
   the relay.  TURN differs from some other relay control protocols in
   that it allows a client to communicate with multiple peers using a
   single relay address.

   The TURN protocol was designed to be used as part of the ICE
   (Interactive Connectivity Establishment) approach to NAT traversal,
   though it also can be used without ICE.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tram-turnbis-06" />
   
</reference>
