Session Traversal Utilities for NAT (STUN)
RFC 8489
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2020-09-16
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
|
2020-08-31
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2020-02-25
|
(System) | IANA registries were updated to include RFC8489 |
|
2020-02-21
|
(System) | Received changes through RFC Editor sync (created alias RFC 8489, changed abstract to 'Session Traversal Utilities for NAT (STUN) is a protocol that serves … Received changes through RFC Editor sync (created alias RFC 8489, changed abstract to 'Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with 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 document obsoletes RFC 5389.', changed pages to 67, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-02-21, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-tram-stunbis and RFC 5389) |
|
2020-02-21
|
(System) | RFC published |