Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04
Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr> Thu, 23 April 2015 10:03 UTC
Return-Path: <emmanuel.baccelli@gmail.com>
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 BBC0B1A90BD for <p2psip@ietfa.amsl.com>; Thu, 23 Apr 2015 03:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.123
X-Spam-Level:
X-Spam-Status: No, score=0.123 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 1XFVRMiYP9l0 for <p2psip@ietfa.amsl.com>; Thu, 23 Apr 2015 03:03:46 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20A501A90C6 for <p2psip@ietf.org>; Thu, 23 Apr 2015 03:03:32 -0700 (PDT)
Received: by oica37 with SMTP id a37so10256269oic.0 for <p2psip@ietf.org>; Thu, 23 Apr 2015 03:03:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=2FJo6cJuODmp2uBiBSgM7JhbDiUxDD4U9WISo/51DXw=; b=vUciDMZ70ljUylc4t3NRajCKs6qbru85gRYZ9gtVhJBrdWx6lJeshKk2axrdmvPyvx 23SfMneRD9+y9CduYQ4T/aJ7j2j5mIJsgP7uKjAy6LXQBHtM7RgVpOyOFouq2TFmYrwe XY50id7uin5aqpwIO/3WCAuATTKE8OQ+Wb8LV8YjTP7Es7X2QGbBoxoqItY7iLCsTQTB OVumUsY0brlLy8ElBDLhUb9ES1LxhFkvmFEisgaodj3wb6EBTuLgzRDQ0c8TPd4M/5wf mhscPHJDKXLIN2V83kGhCPRtOGYRLyO8FjiEV/OfSHTHcbaoeTeZ5peR1Z60/XpSMcOU DS2Q==
X-Received: by 10.60.103.70 with SMTP id fu6mr1741687oeb.27.1429783411531; Thu, 23 Apr 2015 03:03:31 -0700 (PDT)
MIME-Version: 1.0
Sender: emmanuel.baccelli@gmail.com
Received: by 10.76.90.165 with HTTP; Thu, 23 Apr 2015 03:03:11 -0700 (PDT)
In-Reply-To: <B5B18BCE-DAB7-4C45-975A-5ECB3B6250B6@cooperw.in>
References: <CANK0pbaZden4A=wOgJ7VevjqaLjMnG=TqOAN7rToGc=ekp+HoQ@mail.gmail.com> <B5B18BCE-DAB7-4C45-975A-5ECB3B6250B6@cooperw.in>
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
Date: Thu, 23 Apr 2015 12:03:11 +0200
X-Google-Sender-Auth: QRwOPiYNCQAs5WRhyoeX7aFnE7c
Message-ID: <CANK0pbZ28XiTMSfOsO-aEswgSc61gbCfmO6VuTfN8r9Xqpw3XA@mail.gmail.com>
To: p2psip <p2psip@ietf.org>
Content-Type: multipart/alternative; boundary="089e0112c0a059a5910514616458"
Archived-At: <http://mailarchive.ietf.org/arch/msg/p2psip/TcDzDoLuR1KS4Qs2aPc8-1rBVUo>
Subject: Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04
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: Thu, 23 Apr 2015 10:03:47 -0000
Hi Alissa, Hi WG, I have reviewed draft-ietf-p2psip-share-05, and here are my comments. General comments: in my opinion the draft is in good shape and reads well. I have a few nits and editorial suggestions detailed below. I believe these can be addressed quite easily with a quick resubmission and my impression is the doc is ready to go. Detailed comments: in Section 1: refer to RFC6940 (and which section, if applicable) the first time specific terms are used such as "RELOAD Usage" or "RELOAD security model". Spoiler: I will have a lot of such comments below ;) in Section 2: for reader convenience, I suggest listing the key terms (without recalling their definitions) imported from RFC6940, and the p2psip-concepts draft in the paragraph right after the 2119 boilerplate. in Section 3.1: in step 3, I suggest being explicit that the 8bit part is a suffix (least significant bits) in Section 4.1: - "...Alice is also granted (limited) write access..." Either explain what "limited" means here, or remove this adjective. - "Note that overwriting existing items in an Access Control List that reference a different Kind-ID..." Clarify: different from what? I suppose you mean that the overwrite results in changing the Kind-ID - "The Resource Owner is allowed to overwrite any existing ACL item, but should be aware of its consequences." Either quickly explain / give examples of consequences or remove this sentence. in Section 5.1: "The specifications in this document scheme adhere to this paradigm...". add reference to RFC6940 (and the exact section). It will help readers grasp quicker what draft-ietf-p2psip-share specification adds here. in Section 6.1: - first sentence "Write access ... solely be issued by the Resource Owner." rephrase needed (confusing as readers already know that delegation is possible). - "... stored in the numerical order... starting with the index of the root item...". I have a (stupid) question: What if the Node-ID of the an authorized peer with ad=1 has a node-ID that is numerically smaller that that of the owner? I suggest rephrasing in order to clarify this corner case, just to make sure no one is confused? in Section 6.5: Step 1. reference "as per RFC 6940 Section X.Y." in Section 6.6: Because it is possible here, I would have preferred to see the last 2 paragraphs written in steps + pseudo-code style if...else..else. But that's a matter of taste. Best, Emmanuel On Tue, Apr 21, 2015 at 9:08 PM, Alissa Cooper <alissa@cooperw.in> wrote: > Yes, that’s fine, thanks. > Alissa > > On Apr 21, 2015, at 1:40 AM, Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr> > wrote: > > > > > Hi Alissa, > > > > if it is not too late: I am currently reviewing the document. ETA early > next week. > > Sorry for the delay. Is that alright with you? > > > > Best, > > > > Emmanuel > > > > > > > > > > > > _______________________________________________ > > P2PSIP mailing list > > P2PSIP@ietf.org > > https://www.ietf.org/mailman/listinfo/p2psip > >
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Alissa Cooper
- [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Carlos Jesús Bernardos Cano
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Marc Petit-Huguenin
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Emmanuel Baccelli
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Alissa Cooper
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Emmanuel Baccelli
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Thomas C. Schmidt
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Alissa Cooper
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Thomas C. Schmidt
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Alissa Cooper
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Thomas C. Schmidt
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Thomas C. Schmidt
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Emmanuel Baccelli
- Re: [P2PSIP] WGLC for draft-ietf-p2psip-share-04 Bless, Roland (TM)