metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5245: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8445, RFC 8839.

Current document in this lineage: RFC 8445 — Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal; RFC 8839 — Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE)

In plain English — editorial summary, not part of the RFC

This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. 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). ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP). [STANDARDS-TRACK]

Document record

Document ID
RFC5245
Published
April 2010
Authors
J. Rosenberg
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
117
Also known as
—
Obsoletes:
RFC 4091, RFC 4092
Obsoleted by:
RFC 8445, RFC 8839
Updated by:
RFC 6336

Standards lineage

This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.

  1. RFC 4091 (2005)
  2. RFC 4092 (2005)
  3. RFC 5245 (2010)
  4. RFC 6336 (2011)
  5. RFC 8445 (2018)
  6. RFC 8839 (2021) ✓

Read the full history of Session Description Protocol (SDP) Offer/Answer Procedures for Interactive Connectivity Establishment (ICE) →

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5245-interactive-connectivity-establishment-ice-a-protocol-for-network-address-transl