Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Obsoletes:

RFC 3489

Obsoleted by:

RFC 8489

Updated by:

RFC 7350,RFC 8553

Authors:

J. Rosenberg
R. Mahy
P. Matthews
D. Wing

Stream:

IETF

Source:

behave (tsv)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5389

Discuss this RFC: Send questions or comments to the mailing listbehave@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5389

Abstract

Session Traversal Utilities for NAT (STUN) is a protocol that servesas a tool for other protocols in dealing with Network AddressTranslator (NAT) traversal. It can be used by an endpoint todetermine the IP address and port allocated to it by a NAT. It canalso be used to check connectivity between two endpoints, and as akeep-alive protocol to maintain NAT bindings. STUN works with manyexisting NATs, and does not require any special behavior from them.

STUN is not a NAT traversal solution by itself. Rather, it is a toolto be used in the context of a NAT traversal solution. This is animportant change from the previous version of this specification (RFC3489), which presented STUN as a complete solution.

This document obsoletes RFC 3489. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.