RFC 8445: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal
In plain English — editorial summary, not part of the RFC
This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based communication. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). This document obsoletes RFC 5245.
Document record
- Document ID
- RFC8445
- Published
- July 2018
- Authors
- A. Keranen; C. Holmberg; J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 100
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 6544TCP Candidates with Interactive Connectivity Establishment (ICE)Current
March 2012
- RFC 3605Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)Current
October 2003
- RFC 8656Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Current
February 2020
- RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent
January 2017
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9028Native NAT Traversal Mode for the Host Identity ProtocolCurrent
July 2021
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?