--- 1/draft-ietf-p2psip-share-03.txt	2014-08-29 06:14:33.246936390 -0700
+++ 2/draft-ietf-p2psip-share-04.txt	2014-08-29 06:14:33.286937360 -0700
@@ -1,22 +1,22 @@
 
 P2PSIP Working Group                                            A. Knauf
 Internet-Draft                                           T. Schmidt, Ed.
 Intended status: Standards Track                             HAW Hamburg
-Expires: September 4, 2014                                       G. Hege
+Expires: March 2, 2015                                           G. Hege
                                                              daviko GmbH
                                                             M. Waehlisch
                                                     link-lab & FU Berlin
-                                                           March 3, 2014
+                                                         August 29, 2014
 
              A Usage for Shared Resources in RELOAD (ShaRe)
-                       draft-ietf-p2psip-share-03
+                       draft-ietf-p2psip-share-04
 
 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.
@@ -32,21 +32,21 @@
    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 September 4, 2014.
+   This Internet-Draft will expire on March 2, 2015.
 
 Copyright Notice
 
    Copyright (c) 2014 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
@@ -636,23 +636,23 @@
    store request on a Kind that uses the USER-CHAIN-ACL access policy,
    the following rules MUST be applied:
 
    In the USER-CHAIN-ACL policy, a given value MUST be written or
    overwritten, if either one of USER-MATCH or USER-NODE-MATCH
    (mandatory if the data model is dictionary) access policies of the
    base document [RFC6940] applies.
 
    Otherwise, the value MUST be written if the certificate of the signer
    contains a username that matches to one of the variable resource name
-   pattern (c.f. Section 5) specified in the configuration document and,
-   additionally, the hashed Resource Name matches the Resource-ID.  The
-   Resource Name of the Kind to be stored MUST be taken from the
+   pattern (c.f.  Section 5) specified in the configuration document
+   and, additionally, the hashed Resource Name matches the Resource-ID.
+   The Resource Name of the Kind to be stored MUST be taken from the
    mandatory ResourceNameExtension field in the corresponding Kind data
    structure.
 
    Otherwise, the value MUST be written if the ACL validation procedure
    described in Section 6.3 has been successfully applied.
 
 7.  ACCESS-CONTROL-LIST Kind Definition
 
    This section defines the ACCESS-CONTROL-LIST Kind previously
    described in this document.
@@ -778,32 +778,32 @@
 
    [RFC6940]  Jennings, C., Lowekamp, B., Rescorla, E., Baset, S., and
               H. Schulzrinne, "REsource LOcation And Discovery (RELOAD)
               Base Protocol", RFC 6940, January 2014.
 
 11.2.  Informative References
 
    [I-D.ietf-p2psip-concepts]
               Bryan, D., Matthews, P., Shim, E., Willis, D., and S.
               Dawkins, "Concepts and Terminology for Peer to Peer SIP",
-              draft-ietf-p2psip-concepts-05 (work in progress), July
-              2013.
+              draft-ietf-p2psip-concepts-06 (work in progress), June
+              2014.
 
    [I-D.ietf-p2psip-disco]
               Knauf, A., Schmidt, T., Hege, G., and M. Waehlisch, "A
               RELOAD Usage for Distributed Conference Control (DisCo)",
               draft-ietf-p2psip-disco-02 (work in progress), July 2013.
 
    [I-D.ietf-p2psip-sip]
               Jennings, C., Lowekamp, B., Rescorla, E., Baset, S.,
               Schulzrinne, H., and T. Schmidt, "A SIP Usage for RELOAD",
-              draft-ietf-p2psip-sip-12 (work in progress), January 2014.
+              draft-ietf-p2psip-sip-13 (work in progress), July 2014.
 
    [RFC3550]  Schulzrinne, H., Casner, S., Frederick, R., and V.
               Jacobson, "RTP: A Transport Protocol for Real-Time
               Applications", STD 64, RFC 3550, July 2003.
 
 Appendix A.  Change Log
 
    The following changes have been made from version draft-ietf-p2psio-
    share-02: