A Usage for Shared Resources in RELOAD (ShaRe)
draft-ietf-p2psip-share-10

Document Type Active Internet-Draft (p2psip WG)
Last updated 2016-12-12 (latest revision 2016-11-13)
Replaces draft-knauf-p2psip-share
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html 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 Ed Queue
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
RFC Editor RFC Editor state EDIT
P2PSIP Working Group                                            A. Knauf
Internet-Draft                                           T. Schmidt, Ed.
Intended status: Standards Track                             HAW Hamburg
Expires: May 17, 2017                                            G. Hege
                                                             daviko GmbH
                                                            M. Waehlisch
                                                    link-lab & FU Berlin
                                                       November 13, 2016

             A Usage for Shared Resources in RELOAD (ShaRe)
                       draft-ietf-p2psip-share-10

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 17, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Knauf, et al.             Expires May 17, 2017                  [Page 1]
Internet-Draft                    ShaRe                    November 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Shared Resources in RELOAD  . . . . . . . . . . . . . . . . .   4
     3.1.  Mechanisms for Isolating Stored Data  . . . . . . . . . .   5
   4.  Access Control List Definition  . . . . . . . . . . . . . . .   6
     4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Data Structure  . . . . . . . . . . . . . . . . . . . . .   8
   5.  Extension for Variable Resource Names . . . . . . . . . . . .   9
     5.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Data Structure  . . . . . . . . . . . . . . . . . . . . .  10
     5.3.  Overlay Configuration Document Extension  . . . . . . . .  11
   6.  Access Control to Shared Resources  . . . . . . . . . . . . .  12
     6.1.  Granting Write Access . . . . . . . . . . . . . . . . . .  12
     6.2.  Revoking Write Access . . . . . . . . . . . . . . . . . .  13
     6.3.  Validating Write Access through an ACL  . . . . . . . . .  13
     6.4.  Operations of Storing Peers . . . . . . . . . . . . . . .  14
     6.5.  Operations of Accessing Peers . . . . . . . . . . . . . .  14
     6.6.  USER-CHAIN-ACL Access Policy  . . . . . . . . . . . . . .  15
   7.  ACCESS-CONTROL-LIST Kind Definition . . . . . . . . . . . . .  15
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
     8.1.  Resource Exhaustion . . . . . . . . . . . . . . . . . . .  16
     8.2.  Malicious or Misbehaving Storing Peer . . . . . . . . . .  16
     8.3.  Trust Delegation to a Malicious or Misbehaving Peer . . .  17
     8.4.  Privacy Issues  . . . . . . . . . . . . . . . . . . . . .  17
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     9.1.  Access Control Policy . . . . . . . . . . . . . . . . . .  17
Show full document text