Hi all,

we just uploaded a new version of our draft for Shared Resources in RELOAD. Please take a look

http://www.ietf.org/id/draft-knauf-p2psip-share-01.txt

Best regards,

Alexander

Change Log:

   1.  Integrated the USER-PATTERN-MATCH access policy into USER-CHAIN-
       MATCH

   2.  Access Control List Kind uses USER-CHAIN-ACL exclusively

   3.  Resources to be shared use USER-CHAIN-ACL exclusively

   4.  More precise specification of mandatory User_name and
       Resource_name fields for Shared Resources

   5.  Added mechanism for isolating stored data to prevent race
       conditions while concurrent storing

   6.  XML Extension for variable resource names uses its own namespace

   7.  Many editorial improvements



A new version of I-D, draft-knauf-p2psip-share-01.txt has been successfully 
submitted by Alexander Knauf and posted to the IETF repository.

Filename:        draft-knauf-p2psip-share
Revision:        01
Title:           A Usage for Shared Resources in RELOAD (ShaRe)
Creation date:   2011-07-11
WG ID:           Individual Submission
Number of pages: 22

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.




The IETF Secretariat

_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip

Reply via email to