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

Relay using Send and Data indications

03

The client can send a Send indication toward a peer, while returning peer data is delivered using Data indications.

Related RFCs and changes

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

DIAGRAM§ 11 ↗
RFC 8656 · § 11EXAMPLE
3 / 3
Relay using Send and Data indicationsThe client can send a Send indication toward a peer, while returning peer data is delivered using Data indications.clientrelaypeerSendpayloadsource = relayed addressreplyDataTURN relays payload; it does not itself provide end-to-end secrecy
03
A permitted peer reply becomes a Data indication back to the client.

A permitted peer reply becomes a Data indication back to the client.

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

The server relays from the allocated relay address after relevant permission checks.

  • The server relays from the allocated relay address after relevant permission checks.
  • TURN does not make the relayed application payload end-to-end encrypted by itself.
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 ↗