Re: [apps-discuss] Review of draft-ietf-appsawg-file-scheme

Graham Klyne <gk@ninebynine.org> Wed, 13 April 2016 10:46 UTC

Return-Path: <gk@ninebynine.org>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39C5412D6CE; Wed, 13 Apr 2016 03:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 xjZ2x_7xDkkJ; Wed, 13 Apr 2016 03:46:16 -0700 (PDT)
Received: from relay12.mail.ox.ac.uk (relay12.mail.ox.ac.uk [129.67.1.163]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D309D12D1CB; Wed, 13 Apr 2016 03:46:15 -0700 (PDT)
Received: from smtp4.mail.ox.ac.uk ([129.67.1.207]) by relay12.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1aqIJJ-0002rj-eZ; Wed, 13 Apr 2016 11:46:13 +0100
Received: from modemcable171.142-37-24.static.videotron.ca ([24.37.142.171] helo=[192.168.55.103]) by smtp4.mail.ox.ac.uk with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1aqIJJ-0005Tj-E0; Wed, 13 Apr 2016 11:46:13 +0100
Message-ID: <570E2373.20209@ninebynine.org>
Date: Wed, 13 Apr 2016 11:46:11 +0100
From: Graham Klyne <gk@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Matthew Kerwin <matthew@kerwin.net.au>, Dave Crocker <dcrocker@bbiw.net>
References: <570D4C99.1030405@dcrocker.net> <CACweHND-OX+5okkJ+oE=6UN84x+CFtPBpMnU8HqaPbgQgJ_oWA@mail.gmail.com>
In-Reply-To: <CACweHND-OX+5okkJ+oE=6UN84x+CFtPBpMnU8HqaPbgQgJ_oWA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/5tB_gcGqsddM0Arem4CHGAI5NJY>
Cc: draft-ietf-appsawg-file-scheme@ietf.org, Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Review of draft-ietf-appsawg-file-scheme
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 13 Apr 2016 10:46:17 -0000

On 13/04/2016 09:28, Matthew Kerwin wrote:
>> >
>>> >>    o  the use of slashes to denote boundaries between directory levels
>>> >>       of a hierarchical file system; and
>>> >>
>>> >>    o  the requirement that client software convert the file URI into a
>>> >>       file name in the local file name conventions.
>>> >>
>> >
>> >*** Hmmm. A requirement like that moves this from being a URI
>> >specification to being a file protocol specification...
>> >
>> >
> Thank you for saying that, you've triggered a bit of a light-bulb moment
> for me about why I've had so much trouble getting this draft straight in my
> head -- maybe it is actually a protocol spec. That said, I'd rather cut it
> back to be a URI scheme spec. If we need to define the protocol in future,
> then that's a future issue.
>

Yes, I think staying clear of "protocol" is probably best.

#g
--