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

Carry link context in a relay envelope

04

Relay-forward encapsulates a client message and Relay-reply returns it along the relay chain.

Related RFCs and changes

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

DIAGRAM§ 9 ↗
RFC 9915 · § 9EXAMPLE
3 / 3
Carry link context in a relay envelopeRelay-forward encapsulates a client message and Relay-reply returns it along the relay chain.client requestRelay-forward envelopelink-address + peer-addressoriginal requestRelay-replyunwrap toward the clientNested relays add envelopes, not a different client identity
03
Unwrap the corresponding Relay-reply on return toward the client.

Unwrap the corresponding Relay-reply on return toward the client.

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

Link-address and peer-address supply context; nested relays add explicit envelopes.

  • Link-address and peer-address supply context; nested relays add explicit envelopes.
  • Untrusted relay claims need appropriate deployment security; encapsulation alone does not authenticate the client.
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. Choose a two-message or four-message exchange
  2. Keep address and prefix associations distinct
  3. Use binding lifetimes and contact timers correctly
  4. Carry link context in a relay envelope
  5. Separate configuration from trust and privacy
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗