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

Encapsulate an exchange through relays

05

Relay-forward and Relay-reply messages carry client exchanges across the relay path.

This guide explains the 2018 publication. Superseded by RFC 9915.

Related RFCs and changes

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

DIAGRAM§ 19 ↗
RFC 8415 · § 19EXAMPLE
3 / 3
Encapsulate an exchange through relaysRelay-forward and Relay-reply messages carry client exchanges across the relay path.client messagerelayRelay-forwardlink-address / peer-addressclient messageRelay-reply → unwrapRelay context does not by itself authenticate the client
03
Decapsulate the returning Relay-reply toward the client.

Decapsulate the returning Relay-reply toward the client.

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

Relay messages include link-address and peer-address context and a Relay Message option.

  • Relay messages include link-address and peer-address context and a Relay Message option.
  • Relay-to-server protection and Reconfigure authentication are separate security mechanisms; base traffic is not universally authenticated.
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. Select a server and request configuration
  2. Group bindings using DUID and IAID
  3. Delegate a prefix to a router
  4. Renew or rebind before validity ends
  5. Encapsulate an exchange through relays
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗