RFC 6336: IANA Registry for Interactive Connectivity Establishment (ICE) Options
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by 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
It has been identified that "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols" (RFC 5245) is missing a registry for ICE options. This document defines this missing IANA registry and updates RFC 5245. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6336
- Published
- July 2011
- Authors
- M. Westerlund; C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 5
- Also known as
- —
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 6332Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
July 2011
- RFC 6341Use Cases and Requirements for SIP-Based Media Recording (SIPREC)Current
August 2011
- RFC 6365Terminology Used in Internationalization in the IETFCurrent
September 2011
- RFC 6366Requirements for an Internet Audio CodecCurrent
August 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6295RTP Payload Format for MIDICurrent
June 2011
- RFC 6262RTP Payload Format for IP-MR Speech CodecCurrent
August 2011
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?