A Usage for Shared Resources in RELOAD (ShaRe)
RFC 8076
Document | Type | RFC - Proposed Standard (March 2017; No errata) | |
---|---|---|---|
Authors | Alexander Knauf , Thomas Schmidt , Gabriel Hege , Matthias Wählisch | ||
Last updated | 2017-03-22 | ||
Replaces | draft-knauf-p2psip-share | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Marc Petit-Huguenin | ||
Shepherd write-up | Show (last changed 2016-01-03) | ||
IESG | IESG state | RFC 8076 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alissa Cooper | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) A. Knauf Request for Comments: 8076 T. Schmidt, Ed. Category: Standards Track HAW Hamburg ISSN: 2070-1721 G. Hege daviko GmbH M. Waehlisch link-lab & FU Berlin March 2017 A Usage for Shared Resources in RELOAD (ShaRe) 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8076. Knauf, et al. Standards Track [Page 1] RFC 8076 ShaRe March 2017 Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Knauf, et al. Standards Track [Page 2] RFC 8076 ShaRe March 2017 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Shared Resources in RELOAD . . . . . . . . . . . . . . . . . 5 3.1. Mechanisms for Isolating Stored Data . . . . . . . . . . 6 4. Access Control List Definition . . . . . . . . . . . . . . . 7 4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Data Structure . . . . . . . . . . . . . . . . . . . . . 9 5. Extension for Variable Resource Names . . . . . . . . . . . . 10 5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2. Data Structure . . . . . . . . . . . . . . . . . . . . . 11 5.3. Overlay Configuration Document Extension . . . . . . . . 12 6. Access Control to Shared Resources . . . . . . . . . . . . . 13 6.1. Granting Write Access . . . . . . . . . . . . . . . . . . 13 6.2. Revoking Write Access . . . . . . . . . . . . . . . . . . 14 6.3. Validating Write Access through an ACL . . . . . . . . . 14 6.4. Operations of Storing Peers . . . . . . . . . . . . . . . 15 6.5. Operations of Accessing Peers . . . . . . . . . . . . . . 16 6.6. USER-CHAIN-ACL Access Policy . . . . . . . . . . . . . . 16 7. ACCESS-CONTROL-LIST Kind Definition . . . . . . . . . . . . . 17 8. Security Considerations . . . . . . . . . . . . . . . . . . . 17 8.1. Resource Exhaustion . . . . . . . . . . . . . . . . . . . 17 8.2. Malicious or Misbehaving Storing Peer . . . . . . . . . . 18 8.3. Trust Delegation to a Malicious or Misbehaving Peer . . . 18 8.4. Privacy Issues . . . . . . . . . . . . . . . . . . . . . 18 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 9.1. Access Control Policy . . . . . . . . . . . . . . . . . . 19 9.2. Data Kind-ID . . . . . . . . . . . . . . . . . . . . . . 19 9.3. XML Namespace Registration . . . . . . . . . . . . . . . 19Show full document text