Session Traversal Utilities for NAT (STUN)
RFC 5389
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2020-02-22
|
(System) | Received changes through RFC Editor sync (created obsoletes relation between draft-ietf-behave-rfc3489bis and RFC 8489) |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other … Received changes through RFC Editor sync (changed abstract to '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]') |
|
2015-10-14
|
(System) | Notify list changed from behave-chairs@ietf.org, philip_matthews@magma.ca, draft-ietf-behave-rfc3489bis@ietf.org to (None) |
|
2013-02-23
|
(System) | Posted related IPR disclosure: SSH Communications Security Corporation's Statement about IPR related to RFC 5389 |
|
2008-10-28
|
Cindy Morgan | State Changes to RFC Published from RFC Ed Queue by Cindy Morgan |
|
2008-10-28
|
Cindy Morgan | [Note]: 'RFC 5389' added by Cindy Morgan |
|
2008-10-24
|
(System) | RFC published |