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

"Thomas C. Schmidt" <t.schmidt@haw-hamburg.de> Thu, 03 November 2016 16:01 UTC

Return-Path: <t.schmidt@haw-hamburg.de>
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 33221129A7F; Thu, 3 Nov 2016 09:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] 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 Zy1hb7nTO73B; Thu, 3 Nov 2016 09:01:33 -0700 (PDT)
Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 091C6129A3F; Thu, 3 Nov 2016 09:01:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.31,587,1473112800"; d="scan'208";a="30000760"
Received: from post.haw-hamburg.de (HELO HUB01.mailcluster.haw-hamburg.de) ([141.22.24.50]) by mail3.is.haw-hamburg.de with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Nov 2016 17:01:30 +0100
Received: from CAS02.mailcluster.haw-hamburg.de (2002:8d16:183d::8d16:183d) by HUB01.mailcluster.haw-hamburg.de (2002:8d16:1832::8d16:1832) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 3 Nov 2016 17:01:30 +0100
Received: from [10.19.59.174] (141.22.250.35) by haw-mailer.haw-hamburg.de (141.22.24.61) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 3 Nov 2016 17:01:29 +0100
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <abdad8a96fbe484d8a8cdaa30f2f4802@HUB02.mailcluster.haw-hamburg.de>
From: "Thomas C. Schmidt" <t.schmidt@haw-hamburg.de>
Message-ID: <6c639771-f141-489e-af64-18460c951708@haw-hamburg.de>
Date: Thu, 3 Nov 2016 17:01:22 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <abdad8a96fbe484d8a8cdaa30f2f4802@HUB02.mailcluster.haw-hamburg.de>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [141.22.250.35]
Archived-At: <https://mailarchive.ietf.org/arch/msg/p2psip/yC-Q9xu425JV8icCm83_Z4NFScE>
Cc: "draft-ietf-p2psip-share@ietf.org" <draft-ietf-p2psip-share@ietf.org>, "marc@petit-huguenin.org" <marc@petit-huguenin.org>, "p2psip@ietf.org" <p2psip@ietf.org>, "p2psip-chairs@ietf.org" <p2psip-chairs@ietf.org>
Subject: Re: [P2PSIP] Stephen Farrell'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: Thu, 03 Nov 2016 16:01:37 -0000

Hi,

please see inline.

On 03.11.2016 13:43, Stephen Farrell wrote:
> Stephen Farrell 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:
> ----------------------------------------------------------------------
>
>
> - General: this feels more like an experimental spec. If the
> authors didn't object I think that'd be more appropriate.
>

Well authors hope(d) for this to serve as an enabling standard ...

> - General: can these ACLs be resources to which access is
> controlled via another of these ACLs? If so, then it seems like
> there may be some nasty corner-cases where things get lost (so
> nobody can change 'em in future) and I don't see how one might
> recover from that. (Apologies if I'm just mixed up here, I read
> this fairly quickly and didn't reload RELOAD into my little head
> first;-)
>

No. The ACL is itself a shared resource owned by the initial creator 
that will have full rights as long as the resource (and the owner) 
exist. There is no way of disabling the owner.

> - 3.1: 24 bits of collision resistance isn't many. I'm not clear
> why that's ok
>

This actually is meant for small numbers and the storing peer protects 
against collisions (see SecDir review).

> - 3.1, last para: SHA-1 isn't a good example really, SHA-256
> would be better today.
>

This is from Reload - we are not specifying overlay hash functions in 
this document.

> - 5.3: Is the mapping to USER and DOMAIN from certificates
> well-defined? It may be in RELOAD, I forget, sorry;-) It doesn't
> seem to be well-defined here anyway.
>

Yes, certificate and usernames are held in correspondence by reload.

Cheers,
  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 °