Re: [apps-discuss] Working Group Last Call for draft-ietf-appsawg-file-scheme

Matthew Kerwin <matthew@kerwin.net.au> Thu, 26 November 2015 01:50 UTC

Return-Path: <phluid61@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B791A8902 for <apps-discuss@ietfa.amsl.com>; Wed, 25 Nov 2015 17:50:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.373
X-Spam-Level:
X-Spam-Status: No, score=0.373 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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 YYbJkcM3qQdx for <apps-discuss@ietfa.amsl.com>; Wed, 25 Nov 2015 17:50:22 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::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 4DDDA1A88FF for <apps-discuss@ietf.org>; Wed, 25 Nov 2015 17:50:22 -0800 (PST)
Received: by qkda6 with SMTP id a6so22655813qkd.3 for <apps-discuss@ietf.org>; Wed, 25 Nov 2015 17:50:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=lrbKco7Kyn0wyIAZy7pwQgXf+yrfgBABSdrXH0zumhg=; b=0z1hhJ4agKppBw0CnGBEFUItJWbL/dDcspuz6e4Mnqr8Z4q4rDqdLHlOlAEb84B1q8 TB8Wj0X4/k/gNXYC700pV8OVzRYPda6uo2lfm4XQk2JhaBCzaow1V9Q+CqPsjMNGWLK7 UFacm1KOP4RYm9yBfRoE6WW8ICqonvqCb230+BRE6FP7ABCQx4Bwi3BEdNl+Pcoj84gy WZDjc77E8ESeDYEKsiQW2Gv+Fg4GNLRg/6iig9snvusrgLkz9n36EfNbb+Dzt0BBjauU 1KVuxrndj4aGTI1Dll8dMJED2waOE32Km7BwImS/MpTlDzgcMepA4caL9mGTmUXVl34R D1Zw==
MIME-Version: 1.0
X-Received: by 10.55.79.86 with SMTP id d83mr22901102qkb.22.1448502621569; Wed, 25 Nov 2015 17:50:21 -0800 (PST)
Sender: phluid61@gmail.com
Received: by 10.55.184.129 with HTTP; Wed, 25 Nov 2015 17:50:21 -0800 (PST)
In-Reply-To: <56545687.3010400@ninebynine.org>
References: <CAL0qLwb-p0zMpw3+YWRuFY+T5ZwOpWjDNpXehXXpS9WfwJkKqA@mail.gmail.com> <56545687.3010400@ninebynine.org>
Date: Thu, 26 Nov 2015 11:50:21 +1000
X-Google-Sender-Auth: HsOe08EPTISbrdQRHK6On6eS4uw
Message-ID: <CACweHNBUKP1krY0M3Oxpbyujuc0sbcBq2Vv+CP5PZLRyJ=nu0w@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Graham Klyne <gk@ninebynine.org>
Content-Type: multipart/alternative; boundary="001a114a727e37099b052567cc10"
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/f484pclbwpVxpag--lIIhJhhG7I>
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Working Group Last Call for draft-ietf-appsawg-file-scheme
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Nov 2015 01:50:24 -0000

On 24 November 2015 at 22:22, Graham Klyne <gk@ninebynine.org> wrote:

> All,
>
> Apologies for my late response - I missed the original last call, and
> early follow-up.
>
> I would be happy for this to go forward as-is, but I do have a couple of
> minor comments to offer (if only to prove I actually read it again!).
>
>
​Thanks, it's appreciated.​



> ...
>
> [Minor] In section 3, I'm finding the reference to "implementation" a bit
> vague (does this mean URI generators, parsers, or what?), though I suppose
> it's easy enough to figure from the context.
>
> Suggest:
>
> OLD:
> 3.  Operations on file URIs
>
>    Implementations SHOULD, at a minimum, provide a read-like operation
>    to return the contents of a file located by a file URI.  Additional
>    operations MAY be provided, such as writing to, creating, and
>    deleting files.  See the POSIX file and directory operations [POSIX]
>    for examples of standardized operations that can be performed on
>    files.
>
> NEW:
> 3.  Operations on file URIs
>
>    Implementations that provide dereferencing operations on file: URIs
>    SHOULD, at a minimum, provide a read-like operation
>    to return the contents of a file located by a file URI.  Additional
>    operations MAY be provided, such as writing to, creating, and
>    deleting files.  See the POSIX file and directory operations [POSIX]
>    for examples of standardized operations that can be performed on
>    files.
>
> (I hope it's clear that "dereference" is used here in the sense of section
> 1.2.2 of RFC3986 - https://tools.ietf.org/html/rfc3986#section-1.2.2)
>
>
​Yeah, that's a fair call. I'll take the suggested addition.​



> ...
>
> [Minor] In section 3, the text "can only be dereferenced" seems a bit
> strong - in that it appears to prohibit dereferencing lon-local file URIs.
>
> Suggest:
>
> OLD:
>    A file URI can only be dereferenced or translated to a local file
>    path if it is local.  A file URI is considered "local" if it has a
>    blank or no authority, or the authority is the special string
>    "localhost".
>
>
> NEW:
>    A file URI can be dependably dereferenced or translated to a local file
>    path only if it is local.  A file URI is considered "local" if it has a
>    blank or no authority, or the authority is the special string
>    "localhost".
>
>
​Again, yes, that's good. I think it better expresses the intent.  This is
a little different from 1738, which seemed to carry the weight of judgement
(remote files are bad, don't read them) but I don't think that's what we
want to say now.


> ...
>
> (Section 6, aside: it's really strange for me to read "HP OpenVMS Systems
> Documentation" -- but of course, it's quite correct.)
>
>
Starlet? VAX? Micro? (I used Wikipedia to look those up; to me they're just
arcane words you see from time to time in ancient manuals.)



> ...
>
> Good work!
>
> #g
> --
>
>
​Thanks!

​Cheers
-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/