Re: [P2PSIP] Ben Campbell's No Objection on draft-ietf-p2psip-share-09: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Fri, 04 November 2016 22:58 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: p2psip@ietfa.amsl.com
Delivered-To: p2psip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C491296AF; Fri, 4 Nov 2016 15:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=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 2lnvzaEgkwTL; Fri, 4 Nov 2016 15:58:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 5DA2D1294C6; Fri, 4 Nov 2016 15:58:10 -0700 (PDT)
Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uA4Mw52s037607 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 4 Nov 2016 17:58:06 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21]
From: Ben Campbell <ben@nostrum.com>
To: "Thomas C. Schmidt" <t.schmidt@haw-hamburg.de>
Date: Fri, 04 Nov 2016 17:58:06 -0500
Message-ID: <BA3EC449-7190-47B3-9235-F1AE53973884@nostrum.com>
In-Reply-To: <988577c9-f8a9-1a1a-a077-a522ead6076e@haw-hamburg.de>
References: <2ea1f1a9466348ef9608232182626c11@HUB02.mailcluster.haw-hamburg.de> <1b5e197c-cabf-3463-c8e5-8add4fd46974@haw-hamburg.de> <398f4e3e19d84c108af172d134931192@HUB02.mailcluster.haw-hamburg.de> <ef20ba15-9bec-ae1e-ee2a-eca1df677485@haw-hamburg.de> <2e66251e2d584a139713c44debb5bd8c@HUB01.mailcluster.haw-hamburg.de> <988577c9-f8a9-1a1a-a077-a522ead6076e@haw-hamburg.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.5r5263)
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/mjN4NRHdac3Ik3lfOxmdnzKFk-s>
Cc: "draft-ietf-p2psip-share@ietf.org" <draft-ietf-p2psip-share@ietf.org>, "marc@petit-huguenin.org" <marc@petit-huguenin.org>, The IESG <iesg@ietf.org>, "p2psip-chairs@ietf.org" <p2psip-chairs@ietf.org>, "p2psip@ietf.org" <p2psip@ietf.org>
Subject: Re: [P2PSIP] Ben Campbell's No Objection on draft-ietf-p2psip-share-09: (with COMMENT)
X-BeenThere: p2psip@ietf.org
X-Mailman-Version: 2.1.17
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: <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: Fri, 04 Nov 2016 22:58:11 -0000

On 4 Nov 2016, at 17:51, Thomas C. Schmidt wrote:

> HI Ben,
>
> On 04.11.2016 23:17, Ben Campbell wrote:
>
>>>>>> ----------------------------------------------------------------------
>>>>>> COMMENT:
>>>>>> ----------------------------------------------------------------------
>>>>>>
>
>>>>>  ... then you identify the user in the ACL and walk up the
>>>>> delegation
>>>>> chain.
>>>>>
>>>>> In step 5, you have arrived at the root of the delegation tree. 
>>>>> This
>>>>> is the case, when the to_user equals the signer equals the owner 
>>>>> of
>>>>> the resources (see see Figure 1). This is also how it terminates -
>>>>> the
>>>>> owner of the resource is the root of the trust chain.
>>>>
>>>> I'm probably being dense here, but my confusion is in the phrasing 
>>>> of
>>>> "the "to_user" value user name of the signer of the previously
>>>> selected
>>>> ACL item".  Won't that always be true for every ACL item up the 
>>>> chain
>>>> after the first?
>>>>
>>>
>>> No, the selected ACL item from the previous step is the row you are
>>> in. It basically says that the "to_user" value equals the username 
>>> of
>>> the signer. This is the "A  A" case in row 4 in your example below.
>>> This row should be in an ACL only once and the user must be the 
>>> owner
>>> of the resource, which is requested to be verified separately.
>>>
>>>> As an example, Lets say I have a delegation chain of A,B,C,D, where 
>>>> A
>>>> is
>>>> the owner. Would the ACL chain look like the following (in
>>>> leave-to-root
>>>> order )?
>>>>
>>>>    signer to_user
>>>> 1   C        D
>>>> 2   B        C
>>>> 3   A        B
>>>> 4   A        A
>>>>
>>>> If so, then ACL 2 seems to have a to_user that matches the signer 
>>>> of
>>>> ACL
>>>> 1 (the previously selected ACL), which seems to terminate early.
>>>>
>>>> Again, I'm sure I'm missing something.
>>>>
>>>
>>> I believe the confusion comes from the "previously" - this is meant 
>>> to
>>> refer to the "previous step" and the actual row. We changed
>>> "previously" to "previous step" to avoid this confusion.
>>
>> I still think I'm confused. Step 5 basically says iterate over steps 
>> 3
>> and 4. If I'm currently looking at the ACL from the Nth iteration of 
>> 3
>> and 4, it seems to me that the "ACL from the previous step" is ACL 
>> N-1.
>>
>
> The delegation is a tree - so it's not a linear chain.
>
>> If the terminal condition is when you find an ACL where the signer 
>> and
>> the to_user are the same, then I you could say _that_ without getting
>> into "previous steps."
>>
>
> Guess you are right. Why don't we simplify the sentence to
>
> "Repeat steps 3 and 4 until the "to_user" value is equal to the user 
> name of the signer of the ACL in the selected item." ?

Assuming that gives the right results (I'll leave that to you to 
decide), I think it would be easier to understand.

Thanks!

Ben.

>
> Thanks,
>  thomas
>
> -- 
>
> Prof. Dr. Thomas C. Schmidt
> ° Hamburg University of Applied Sciences                   Berliner 
> Tor 7 °
> ° Dept. Informatik, Internet Technologies Group    20099 Hamburg, 
> Germany °
> ° http://www.haw-hamburg.de/inet                   Fon: 
> +49-40-42875-8452 °
> ° http://www.informatik.haw-hamburg.de/~schmidt    Fax: 
> +49-40-42875-8409 °