[P2PSIP] Fwd: New Version Notification for draft-ietf-p2psip-share-05.txt
"Thomas C. Schmidt" <t.schmidt@haw-hamburg.de> Mon, 02 March 2015 19:05 UTC
Return-Path: <t.schmidt@haw-hamburg.de>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBC9C1A891A for <p2psip@ietfa.amsl.com>; Mon, 2 Mar 2015 11:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level:
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Fk_OTHxspEH for <p2psip@ietfa.amsl.com>; Mon, 2 Mar 2015 11:05:14 -0800 (PST)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C37F1A88E7 for <p2psip@ietf.org>; Mon, 2 Mar 2015 11:05:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.09,676,1418079600"; d="scan'208";a="25196610"
Received: from post.haw-hamburg.de (HELO HUB01.mailcluster.haw-hamburg.de) ([141.22.24.50]) by mail6.is.haw-hamburg.de with ESMTP/TLS/AES128-SHA; 02 Mar 2015 20:05:02 +0100
Received: from CAS01.mailcluster.haw-hamburg.de (2002:8d16:183c::8d16:183c) by HUB01.mailcluster.haw-hamburg.de (2002:8d16:1832::8d16:1832) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 2 Mar 2015 20:05:01 +0100
Received: from [192.168.12.141] (141.22.200.50) by haw-mailer.haw-hamburg.de (141.22.24.60) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 2 Mar 2015 20:05:01 +0100
Message-ID: <54F4B456.8000402@haw-hamburg.de>
Date: Mon, 02 Mar 2015 20:04:54 +0100
From: "Thomas C. Schmidt" <t.schmidt@haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "p2psip@ietf.org" <p2psip@ietf.org>
References: <1520fccf63be447bb960a7504e75f375@HUB01.mailcluster.haw-hamburg.de>
In-Reply-To: <1520fccf63be447bb960a7504e75f375@HUB01.mailcluster.haw-hamburg.de>
X-Forwarded-Message-Id: <1520fccf63be447bb960a7504e75f375@HUB01.mailcluster.haw-hamburg.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/xPUyEdHJbHEMUPt2SjejbPSGz3Q>
Subject: [P2PSIP] Fwd: New Version Notification for draft-ietf-p2psip-share-05.txt
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Peer-to-Peer SIP working group discussion list <p2psip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/p2psip>, <mailto:p2psip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/p2psip/>
List-Post: <mailto:p2psip@ietf.org>
List-Help: <mailto:p2psip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2psip>, <mailto:p2psip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Mar 2015 19:05:16 -0000
Folks, ShaRe was updated to converge these days. We would really love some more feedback ... does someone like to share? Cheers, Thomas -------- Forwarded Message -------- A new version of I-D, draft-ietf-p2psip-share-05.txt has been successfully submitted by Thomas C. Schmidt and posted to the IETF repository. Name: draft-ietf-p2psip-share Revision: 05 Title: A Usage for Shared Resources in RELOAD (ShaRe) Document date: 2015-03-02 Group: p2psip Pages: 20 URL: http://www.ietf.org/internet-drafts/draft-ietf-p2psip-share-05.txt Status: https://datatracker.ietf.org/doc/draft-ietf-p2psip-share/ Htmlized: http://tools.ietf.org/html/draft-ietf-p2psip-share-05 Diff: http://www.ietf.org/rfcdiff?url2=draft-ietf-p2psip-share-05 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. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat
- [P2PSIP] Fwd: New Version Notification for draft-… Thomas C. Schmidt