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

Matthew Kerwin <matthew@kerwin.net.au> Sat, 07 May 2016 10:03 UTC

Return-Path: <phluid61@gmail.com>
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 8BF6812D533; Sat, 7 May 2016 03:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level:
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Wym2IaPOa1wy; Sat, 7 May 2016 03:03:20 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 5A96912D168; Sat, 7 May 2016 03:03:20 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id 190so135513703iow.1; Sat, 07 May 2016 03:03:20 -0700 (PDT)
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; bh=o8AlKeQgAcQ6dR7QjJS31tV8MK4DEHf/Dt5dZBowEIU=; b=s+7a2q5lUhW3m+zge+EMphsDC/Xo/xNq6/sqI7RLgcotv68paQm3k3d42CtCxsvER5 SpvvMr0incLfB2Wh64EnR4NrESTQx1kY8NNfVja1P/7h70AFypEgzUVxwSLqHKKmXkle Tn8/SjEUQU+KpswJn3H6Bnu6cB/WDGCu/UQu/Y3DqSS7Py1lhR3/3lezmsQSCtrJecgl iD3clVUNptzys2aW4x5VTUf/wZP121OW1JxHQj7wYF8+D/GT/JzUguwgNjIcUEQASTCg 40jj0lg+WrniMmzb1K8RsdwXcRbppcv4i9neKqWd7qmrakXmSHc4Y2/AJO2wLqIqmVS0 Ipvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=o8AlKeQgAcQ6dR7QjJS31tV8MK4DEHf/Dt5dZBowEIU=; b=Y0zwaZ1S7pGYVeWeQY3ldO54xbnIdBMOjja7jSUo0pRmZ7Y/NvsD/Q5VBE14gfXVfX mYDpNbpb7DXwVOQ8DUiBcgUbipluJyOZJXDyLDu/Xx/PaQAGBsuCvgf/0btOKijh21PK yMFq+iu0rp1tSHqywnhCWLH8A1DReOewrnn82Ur9bAJDABUvPCpCM1fAd5HqopfgYF47 Ue+S4Ob3r3f/JdaPnTPPA1JdahL4jrFoGprUgy4aPuAg0lr/UDVhhntGHrPKR4XxZPe9 Ve/5HD/7csysBbdcVmsiTjw/zU9mxrAKIdfR/vPLxicMubfb1aiUclUbtonlOKFYoy6z OQRA==
X-Gm-Message-State: AOPr4FWYIGk6UBTXf8rs046EdC5nLOrRGCH8eyQH6HnEnE9nJl8O9R+v2EFmlemFl+OCdOXc5MPzX9KA6QmARQ==
MIME-Version: 1.0
X-Received: by 10.107.147.7 with SMTP id v7mr28072621iod.3.1462615399723; Sat, 07 May 2016 03:03:19 -0700 (PDT)
Sender: phluid61@gmail.com
Received: by 10.107.138.230 with HTTP; Sat, 7 May 2016 03:03:19 -0700 (PDT)
In-Reply-To: <a16b7cf5-3635-a3cb-b743-850f4047f862@gmx.de>
References: <570D4C99.1030405@dcrocker.net> <CACweHND-OX+5okkJ+oE=6UN84x+CFtPBpMnU8HqaPbgQgJ_oWA@mail.gmail.com> <570E2510.4040408@ninebynine.org> <CACweHNCLS+QU2QveqYjkuPnDybbm-dtX9qQPsO4tTkgUoc5QYg@mail.gmail.com> <5710953E.5040505@gmx.de> <CACweHNDuDnP4P-4suUaFpS0OX-CbAYxn39jsZ3O_s-KYn=qbKw@mail.gmail.com> <a16b7cf5-3635-a3cb-b743-850f4047f862@gmx.de>
Date: Sat, 7 May 2016 20:03:19 +1000
X-Google-Sender-Auth: wYev2jaNvjVdUswqdMkRigBcwaE
Message-ID: <CACweHNBbB2zhyPdV-QDb_Ske6b6ZDWdmA2rk8AL5DT56N8M0hQ@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: multipart/alternative; boundary=94eb2c055f6857fbee05323dafd4
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/mcYG3llud8fLSocX_TMNdhJqkXE>
Cc: IETF Apps Discuss <apps-discuss@ietf.org>, draft-ietf-appsawg-file-scheme@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: Sat, 07 May 2016 10:03:23 -0000

On 7 May 2016 at 19:31, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2016-05-07 09:54, Matthew Kerwin wrote:
>
>> Hi again everyone, sorry for the dead air. I've been trying to work on
>> these last open comments but am not really sure how tp address them.
>>
>> On 15/04/2016 5:17 PM, "Julian Reschke" <julian.reschke@gmx.de
>> <mailto:julian.reschke@gmx.de>> wrote:
>> ​​
>>
>>
>>> case-insensitive (DOS?) < case-preserving (NTFS) < case-sensitive
>>> (others)
>>>
>>> ...so maybe mention all the three cases.
>>>
>>>
>> A case-based typo in a case-sensitive system gives an unwanted 404; an
>> intentional difference in a case-insensitive system gives an unwanted
>> 200. Case preservation doesn't really add anything to the issue, does it?
>>
>
> That's true, but maybe we can rephrase it in a way that it doesn't seem to
> neglect this case?
>
> ""
> File systems vary in the way they handle case.
> ""
>

That works nicely, thanks.



> ​​
>>>
>>> PS: it might also be good to touch Unicode normalization forms...
>>>
>>>
>> How's this?
>>
>> ""
>> Care must be taken to avoid issues resulting from aliasing from
>> mismatched encodings or Unicode equivalences.
>> ""
>>
>
> That can't hurt.
>
> I wonder whether we can say something useful about how to map Unicode code
> points into the file URI (that is, before percent-encoding the UTF-8
> octets). Is it a good idea to apply unicode normalization at this step? (I
> don't know but maybe others do?)
>
>
That's kind of what Section 4 (Encoding) does; though that's the part that
Dave Crocker suggested I cut right back. In any case I am working on
rewriting that section since it doesn't quite feel right, but the intention
will remain the same -- use UCS + NFC + UTF-8 when possible.

Best regards, Julian
>
>
Cheers
-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/