RFC 8076: A Usage for Shared Resources in RELOAD (ShaRe)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8076
- Published
- March 2017
- Authors
- A. Knauf; T. Schmidt; G. Hege; M. Waehlisch
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 7890Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)Current
June 2016
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 2016
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 8197A SIP Response Code for Unwanted CallsCurrent
July 2017
- RFC 8224Authenticated Identity Management in the Session Initiation Protocol (SIP)Updated
February 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?