A Usage for Shared Resources in RELOAD (ShaRe)
draft-knauf-p2psip-share-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Alexander Knauf , Gabriel Hege , Thomas C. Schmidt , Matthias Wählisch | ||
Last updated | 2012-10-15 (Latest revision 2012-04-25) | ||
Replaced by | draft-ietf-p2psip-share | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-p2psip-share | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines a 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 which is useful whenever peer-independent rendezvous processes are required.
Authors
Alexander Knauf
Gabriel Hege
Thomas C. Schmidt
Matthias Wählisch
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)