Refresh or delete the allocation
05Allocations and their supporting state consume relay resources and must be maintained deliberately.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 8 ↗
RFC 8656 · § 8EXAMPLE
3 / 3
03
A zero-lifetime Refresh explicitly releases the allocation.
A zero-lifetime Refresh explicitly releases the allocation.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Refresh can extend allocation lifetime; a requested lifetime of zero deletes it.
- Refresh can extend allocation lifetime; a requested lifetime of zero deletes it.
- Permission and channel lifetimes are separate; refreshing an allocation does not automatically make all peer state permanent.
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