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

Install a permission for a peer

02

A permission authorizes relayed traffic from a particular peer IP address.

Related RFCs and changes

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

DIAGRAM§ 9 ↗
RFC 8656 · § 9EXAMPLE
3 / 3
Install a permission for a peerA permission authorizes relayed traffic from a particular peer IP address.peer IPrelayno permissionCreatePermission: peer IPpermitted peer trafficPermission is keyed by peer IP, not an application identity
03
Traffic from the permitted peer can pass the permission check.

Traffic from the permitted peer can pass the permission check.

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

Permissions are keyed by peer IP, not by every individual peer port.

  • Permissions are keyed by peer IP, not by every individual peer port.
  • A permission has a finite lifetime and can be refreshed; it is not a full application identity assertion.
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 ↗