<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.salgueiro-tram-stunbis" target="https://datatracker.ietf.org/doc/html/draft-salgueiro-tram-stunbis-01">
   <front>
      <title>Session Traversal Utilities for NAT (STUN)</title>
      <author initials="M." surname="Petit-Huguenin" fullname="Marc Petit-Huguenin">
         </author>
      <author initials="G." surname="Salgueiro" fullname="Gonzalo Salgueiro">
         </author>
      <author initials="J." surname="Rosenberg" fullname="Jonathan Rosenberg">
         </author>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         </author>
      <author initials="R." surname="Mahy" fullname="Rohan Mahy">
         </author>
      <author initials="P." surname="Matthews" fullname="Philip Matthews">
         </author>
      <date month="October" day="10" year="2014" />
      <abstract>
	 <t>   Session Traversal Utilities for NAT (STUN) is a protocol that serves
   as a tool for other protocols in dealing with Network Address
   Translator (NAT) traversal.  It can be used by an endpoint to
   determine the IP address and port allocated to it by a NAT.  It can
   also be used to check connectivity between two endpoints, and as a
   keep-alive protocol to maintain NAT bindings.  STUN works with many
   existing NATs, and does not require any special behavior from them.

   STUN is not a NAT traversal solution by itself.  Rather, it is a tool
   to be used in the context of a NAT traversal solution.  This is an
   important change from the previous version of this specification (RFC
   3489), which presented STUN as a complete solution.

   This document obsoletes RFC 3489.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-salgueiro-tram-stunbis-01" />
   
</reference>
