A Usage for Shared Resources in RELOAD
RFC 8076, “A Usage for Shared Resources in RELOAD”, is a Proposed Standard document published in March 2017 by A. Knauf, T. Schmidt, G. Hege, M. Waehlisch. The canonical text is published by the RFC Editor.
Abstract
This document defines a REsource LOcation And Discovery (RELOAD) Usage for managing shared write access to RELOAD Resources. Shared Resources in RELOAD (ShaRe) form a basic primitive for enabling various coordination and notification schemes among distributed peers. Access in ShaRe is controlled by a hierarchical trust delegation scheme maintained within an access list. A new USER-CHAIN-ACL access policy allows authorized peers to write a Shared Resource without owning its corresponding certificate. This specification also adds mechanisms to store Resources with a variable name that is useful whenever peer-independent rendezvous processes are required.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8076 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8075 Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol
- RFC 8077 Pseudowire Setup and Maintenance Using the Label Distribution Protocol
- RFC 8074 Source Address Validation Improvement for Mixed Address Assignment Methods Scenario
- RFC 8078 Managing DS Records from the Parent via CDS/CDNSKEY
- RFC 8073 Coordinating Attack Response at Internet Scale Workshop Report
- RFC 8079 Guidelines for End-to-End Support of the RTP Control Protocol in Back-to-Back User Agents
- RFC 8072 YANG Patch Media Type
- RFC 8080 Edwards-Curve Digital Security Algorithm for DNSSEC