[Gen-art] Gen-ART Review of draft-sanchez-webdav-current-principal-01

Christian Vogt <christian.vogt@nomadiclab.com> Wed, 24 September 2008 15:47 UTC

Return-Path: <gen-art-bounces@ietf.org>
X-Original-To: gen-art-archive@optimus.ietf.org
Delivered-To: ietfarch-gen-art-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CFCF28C2FE; Wed, 24 Sep 2008 08:47:48 -0700 (PDT)
X-Original-To: gen-art@core3.amsl.com
Delivered-To: gen-art@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8B993A6DE8 for <gen-art@core3.amsl.com>; Wed, 24 Sep 2008 08:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.301
X-Spam-Level:
X-Spam-Status: No, score=0.301 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8Uf8LLpQDFW for <gen-art@core3.amsl.com>; Wed, 24 Sep 2008 08:47:45 -0700 (PDT)
Received: from n2.nomadiclab.com (n2.nomadiclab.com [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id C32313A6DE7 for <gen-art@ietf.org>; Wed, 24 Sep 2008 08:47:44 -0700 (PDT)
Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 62F881F0E9C; Wed, 24 Sep 2008 18:47:48 +0300 (EEST)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by n2.nomadiclab.com (Postfix) with ESMTP id E68C21F0E9A; Wed, 24 Sep 2008 18:47:47 +0300 (EEST)
Message-Id: <3B31855D-DE79-4C3A-BBB5-78635B660978@nomadiclab.com>
From: Christian Vogt <christian.vogt@nomadiclab.com>
To: Gen-ART Mailing List <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Wed, 24 Sep 2008 18:47:47 +0300
X-Mailer: Apple Mail (2.929.2)
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: cyrus@daboo.name, wsanchez@wsanchez.net
Subject: [Gen-art] Gen-ART Review of draft-sanchez-webdav-current-principal-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.


Document..........:  draft-sanchez-webdav-current-principal-01
Reviewer..........:  Christian Vogt
Review date.......:  September 24, 2008
IESG Telechat date:  September 25, 2008


Summary:  This draft is basically ready for publication, but has nits
          that should be fixed before publication.


This document explains the need for a new WebDAV property containing
the principal of an online resource, and it specifies such a property.

The document is in good shape overall, and I think it can be published
very soon.  However, I have one technical comment, which may either
require some rethinking and rewriting, or some additional explanation
in the document.  I have also identified a few editorial nits, which
are easy to fix.


TECHNICAL

Section 3, 2nd paragraph of "description" field:

  This paragraph specifies the return value for the principal resource
  in case there are multiple possible values.  The return value is in
  this a case to be freely chosen by the server.  Why not return all
  possible values?

  The disadvantage of returning only a single principal resource value
  is that it may lead to consistency problems.  The paragraph attempts
  to prevent this by urging servers to /try/ to be consistent.  But
  since consistency cannot be guaranteed, consistency problems may
  still come up.  Always returning all possible values would fix this.

  The authors should consider changing the protocol behavior to always
  returning all available principal resource values.  If there are
  reasons to restrict the number of values returned to a single one,
  then these reasons should be explained in section 3 of the document.


EDITORIAL

Section 1, 1st paragraph:

  The acronym "ACL" appears here for the first time and should
  therefore be spelled out.

Section 1, 1st paragraph:

  "principal resource" which --> "principal" resource, which

Section 1, 2nd paragraph:

  recommended way to do identify --> recommended way to identify

Section 3, "purpose" field:

  current authenticated --> currently authenticated

Section 3, "value" field:

  The value is currently specified to always be a DAV:href element.
  But according to the description that follows, it could also be a
  DAV:unauthenticated element.  This inconsistency should be fixed.

Section 4:

  issues beyond those defined in HTTP --> issues beyond those
  identified for HTTP

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art