Visual RFC.
ALL RFCs / RFC 8445
Read the RFC ↗
RFC 8445 / MECHANISMS

Gather possible addresses

01

ICE collects local, server-reflexive, and relayed candidate addresses.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 8445 · § 5.1.1EXAMPLE
3 / 3
Gather possible addressesICE collects local, server-reflexive, and relayed candidate addresses. Current state: Relay candidate.Gather possible addressesEndpointhost addressSTUNmappingserver-reflexiveTURNallocationrelay address
03
Relay candidate

Obtain a TURN relay address when needed.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 5245 ICERFC 8445 § 1

This specification replaces RFC 5245 and separates the core ICE procedure from its signaling usage.

Read the updated RFC section ↗
KEY POINT

Host candidates come from local interfaces.

  • Host candidates come from local interfaces.
  • Server-reflexive candidates describe a NAT-mapped address discovered using STUN.
  • Relayed candidates use a TURN allocation.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Gather possible addresses
  2. Check candidate pairs
  3. Nominate a selected path
  4. Restart changes the credentials
  5. Traversal is not media encryption
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗