Visual RFC.
ALL RFCs / RFC 8656
Read the RFC ↗
RFC 8656 / PROTOCOL MECHANISMS

Allocate a relayed transport address

01

A TURN client authenticates and requests an allocation associated with a relayed address.

Related RFCs and changes

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

DIAGRAM§ 7 ↗
RFC 8656 · § 7EXAMPLE
3 / 3
Allocate a relayed transport addressA TURN client authenticates and requests an allocation associated with a relayed address.clientTURNAllocateauthenticate exchangerelayed address + granted lifetimeAllocation has finite resource scope, not unlimited relay permission
03
Receive the relayed address and lifetime.

Receive the relayed address and lifetime.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 5766 + RFC 6156RFC 8656 § 24

This revision incorporates IPv6 support and REQUESTED-ADDRESS-FAMILY, adds DTLS support, and aligns TURN with updated STUN.

Read the updated RFC section ↗
KEY POINT

An allocation has a lifetime and is associated with the relevant client-server transport context.

  • An allocation has a lifetime and is associated with the relevant client-server transport context.
  • Relayed transport support and requested address family are negotiated; an address is not an unlimited relay entitlement.
DETAILS

The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. Allocate a relayed transport address
  2. Install a permission for a peer
  3. Relay using Send and Data indications
  4. Bind a channel for repeated traffic
  5. Refresh or delete the allocation
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗