[P2PSIP] Mirja Kühlewind's No Objection on draft-ietf-p2psip-share-09: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Mon, 31 October 2016 14:06 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: p2psip@ietf.org
Delivered-To: p2psip@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BA52C12973E; Mon, 31 Oct 2016 07:06:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147792281676.32457.7489100118055807317.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2016 07:06:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/A5Fqnu4KxXinRgcJv3IeacEAy9g>
Cc: draft-ietf-p2psip-share@ietf.org, marc@petit-huguenin.org, p2psip@ietf.org, p2psip-chairs@ietf.org
Subject: [P2PSIP] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-p2psip-share-09=3A_=28with_COMMENT=29?=
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 31 Oct 2016 14:06:57 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-p2psip-share-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-p2psip-share/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Quick questions on sec 6.3. (Validating Write Access through an ACL):
Do I really need to validate the authorization chain in the ACL every
time I give access to a resource? Wouldn't I rather validate the ACL when
it's modified and then simply assume that it is sufficient that I have an
entry in the ACL to provide access?