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

Graham Klyne <gk@ninebynine.org> Wed, 13 April 2016 10:53 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 E877112DCAB; Wed, 13 Apr 2016 03:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 IfQXkD57jIuQ; Wed, 13 Apr 2016 03:53:09 -0700 (PDT)
Received: from relay16.mail.ox.ac.uk (relay16.mail.ox.ac.uk [163.1.2.166]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7802812DB56; Wed, 13 Apr 2016 03:53:09 -0700 (PDT)
Received: from smtp4.mail.ox.ac.uk ([129.67.1.207]) by relay16.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1aqIPy-0006aT-ro; Wed, 13 Apr 2016 11:53:06 +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 1aqIPy-0006Ca-EQ; Wed, 13 Apr 2016 11:53:06 +0100
Message-ID: <570E2510.4040408@ninebynine.org>
Date: Wed, 13 Apr 2016 11:53:04 +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=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Oxford-Username: zool0635
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/i3zJzf1_fL4rEILc27rVlhr9oBI>
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:53:11 -0000

On 13/04/2016 09:28, Matthew Kerwin wrote:
>>>     Systems exhibit different levels of case-sensitivity.  Unless the
>>> >>    file system is known to be case-insensitive, implementations MUST
>>> >>    maintain the case of file and directory names when translating file
>>> >>    URIs to and from the local system's representation of file paths, and
>>> >>    any systems or devices that transport file URIs MUST NOT alter the
>>> >>    case of file URIs they transport.
>>> >>
>> >
>> >This is protocol language, not URI format/semantics language.
>> >
>> >I believe that the needs of this spec are served by something along the
>> >lines of:
>> >
>> >​​
>> >     Some systems have case-sensitive file naming and some do not.  Hence
>> >the  file scheme supports case sensitivity, in order to retain the case
>> >as given. Any transport-related handling of the file URI scheme MUST
>> >retain the case as given. Any mapping to or from a case-insensitive form
>> >is soley the responsibility of the implementation processing the file
>> >URI on behalf of the referenced file system.
>> >
>> >
> Sure thing, I'll work with that suggestion.

I think this is pretty much redundant.  URIs are case sensitive per RFC3986.

(Local interpretation may not be, but I'd suggest that's a local implementation 
issue.  At most, make a note as a local handling issue in the appendices? 
Hmmm... are there any security considerations here that should be flagged - 
relating to possible unexpected aliasing from case-only differences between files.)

#g