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

Bind a channel for repeated traffic

04

A channel number associates a client-side compact framing identifier with a peer transport address.

Related RFCs and changes

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

DIAGRAM§ 12 ↗
RFC 8656 · § 12EXAMPLE
3 / 3
Bind a channel for repeated trafficA channel number associates a client-side compact framing identifier with a peer transport address.ChannelBind: 0x4001 → peer IP:portexample valid channel number0x4001ChannelData payloadLookup binding → deliver to peer transportCompact framing still needs a valid binding and permission
03
The server resolves the binding to the peer transport address.

The server resolves the binding to the peer transport address.

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

ChannelBind establishes the association and also creates or refreshes a permission as specified.

  • ChannelBind establishes the association and also creates or refreshes a permission as specified.
  • ChannelData framing reduces overhead; it does not replace authorization or make channels permanent.
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 ↗