<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-behave-rfc3489bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-behave-rfc3489bis-18">
   <front>
      <title>Session Traversal Utilities for NAT (STUN)</title>
      <author initials="P." surname="Matthews" fullname="Philip Matthews">
         <organization>Unaffiliated</organization>
      </author>
      <author initials="J." surname="Rosenberg" fullname="Jonathan Rosenberg">
         <organization>Cisco</organization>
      </author>
      <author initials="D." surname="Wing" fullname="Dan Wing">
         <organization>Cisco</organization>
      </author>
      <author initials="R." surname="Mahy" fullname="Rohan Mahy">
         <organization>Unaffiliated</organization>
      </author>
      <date month="July" day="28" year="2008" />
      <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. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-behave-rfc3489bis-18" />
   
</reference>
