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

Check candidate pairs

02

Local and remote candidates form prioritized pairs that must be tested for connectivity.

Related RFCs and changes

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

RFC 8445 · § 6.1.2EXAMPLE
3 / 3
Check candidate pairsLocal and remote candidates form prioritized pairs that must be tested for connectivity. Current state: Successful pair.Check candidate pairsL1R1STUN checkL2R2check failsL3R3check succeedsSignaled addresses become useful only after connectivity checks.
03
Successful pair

Record a validated path rather than assuming reachability.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A signaled address alone is not proof of a working path.

  • A signaled address alone is not proof of a working path.
  • STUN connectivity checks test candidate pairs.
  • Successful checks populate a valid list.
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 ↗