%% You should probably cite rfc5389 instead of this I-D. @techreport{ietf-behave-rfc3489bis-18, number = {draft-ietf-behave-rfc3489bis-18}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-behave-rfc3489bis/18/}, author = {Philip Matthews and Jonathan Rosenberg and Dan Wing and Rohan Mahy}, title = {{Session Traversal Utilities for NAT (STUN)}}, pagetotal = 51, year = 2008, month = jul, day = 28, abstract = {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{]}}, }