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

Matthew Kerwin <matthew@kerwin.net.au> Sun, 15 May 2016 09:53 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 006B512D150; Sun, 15 May 2016 02:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level:
X-Spam-Status: No, score=-2.15 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.198, 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 RCyqRIjrY7m3; Sun, 15 May 2016 02:53:22 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (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 B90D212D14D; Sun, 15 May 2016 02:53:22 -0700 (PDT)
Received: by mail-ig0-x22b.google.com with SMTP id qe5so34180112igc.1; Sun, 15 May 2016 02:53:22 -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=lgGREtS+V2ObEfida4+Wr/afeVFawtSZXt8LBPQPjvM=; b=N6FSyQ2GX0lqlDi2+iSQRLtvggMj6d5mozD9SPVc1YGS9V4+8R9fo+TEG0B2tDPL6F qQiqUP5WHHVFXZBjsbVphcRgwdytNxGIWN7zx2j8Ekd1bcALCSeJP0YyQ+eeTRLMJg9J XT+CH9vTiasAgIcBw2spxqysnVF9Yt9retqKOToI8dd281u7xKhT2re9JmTvbtC4cGr/ peMyKklVmE67S6SbSKdMMNSu7lB5YUEBlzuDFOMQXIdIb9CguiH5Vbq0+IPuS4j6qnSY m43i8rWg48q1UFoYh4rffz8fUJFWzGYhAmukT/euTu3spPbgoIx7+T3YT5/oG5tB434N N7jw==
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=lgGREtS+V2ObEfida4+Wr/afeVFawtSZXt8LBPQPjvM=; b=O+2wH/22+XMm/syztxXHWK7nMnWpLMCoVxvuhkrM1OL4pydKZDgjxhX/HgVVvL+o7n /nZAWoESyBPkWy/Uk7TlfkOjcrr7fk4Y91GsbZb/tc76ERrM/eirSVw7pcT0oeZLIqq6 PNnip6ES6IglpIJzc1kfEiU2J1RHBhD8+K4zHDPjYIGYUI36lfAyskYCSjxgcGtS7h1o cEj0b1tYggt0OAmrK3cm+kHyQvgiWtkreJUIEtrdItJiMvnMyOuzpVHNxE+/ac9dOLQ9 x3CDV9D/zs/oCidDAadFunvBPK0afHQbgOR5RmeAoNqc0oVEL/WUSB/o34BlGdKjS5ZF aQhQ==
X-Gm-Message-State: AOPr4FUEg59isS3PAzFyGQwIeVIzK8XeyxTJ0kLRboQ7wQXUTCjmJHURCXx/nLiU79gS3u0iNoFnMEhPuc4++A==
MIME-Version: 1.0
X-Received: by 10.50.183.132 with SMTP id em4mr5526641igc.50.1463306002028; Sun, 15 May 2016 02:53:22 -0700 (PDT)
Sender: phluid61@gmail.com
Received: by 10.107.138.230 with HTTP; Sun, 15 May 2016 02:53:21 -0700 (PDT)
In-Reply-To: <f4ebfccc-070a-fc8d-1693-5289f712d43f@seantek.com>
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> <B3F27B33707E397A452D158D@JcK-HP8200.jck.com> <6f2915b6-d36b-fbf6-f8a5-e35cf646faeb@it.aoyama.ac.jp> <88F1BC9BE8337F5D3B95E1BA@JcK-HP8200.jck.com> <01Q01K03ULG000005M@mauve.mrochek.com> <CACweHNATdZxvjjbPswiZUCghjFUEMV-7sYyG+J7c096BZd2uLA@mail.gmail.com> <CACweHNDZTCOpDFJaPDBL6o-FxxNR7QqXpzoZGXUFpAvYxerKEA@mail.gmail.com> <5735D10C.4010305@dcrocker.net> <CACweHNAfQbn=8ozAky7XTSCiBrTARXpndJmatq29QsMEVGYW3A@mail.gmail.com> <f4ebfccc-070a-fc8d-1693-5289f712d43f@seantek.com>
Date: Sun, 15 May 2016 19:53:21 +1000
X-Google-Sender-Auth: rCzSyaEXCjgWySboIJHUbUaZrkw
Message-ID: <CACweHNBoqKbm83wZYVVUt5mGt5wS6u87T8V8QoiZn9QtCUu5Yg@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Sean Leonard <dev+ietf@seantek.com>
Content-Type: multipart/alternative; boundary=14dae9340c9572e3a60532de7a84
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/q67SXsATNj2Wl9ikamCmasXbX18>
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF Apps Discuss <apps-discuss@ietf.org>, Ned Freed <ned.freed@mrochek.com>, Dave Crocker <dcrocker@bbiw.net>, 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: Sun, 15 May 2016 09:53:25 -0000

On 15 May 2016 at 19:38, Sean Leonard <dev+ietf@seantek.com> wrote:

> On 5/14/2016 10:26 PM, Matthew Kerwin wrote:
>
>
>
> On 13 May 2016 at 23:05, Dave Crocker <dcrocker@gmail.com> wrote:
>
>> On 5/13/2016 12:05 AM, Matthew Kerwin wrote:
>>
>>> 4. Encoding
>>>
>>> File systems use various encoding schemes to store file and directory
>>> names.
>>>
>>
>>
>> Just to be particularly picky, since the text is about name encoding and
>> not, for example, content encoding, I suggest the title be
>>
>>    4. File Name Encoding
>>
>> d/
>>
>>
> ​Fair enough. I've published this version, with the cut down text and the
> new section name, as -09 so people can view it in the whole or using the
> diff tools.
>
>
> In the picky vein, Section 4 should be called
> 4. Path Encoding
>
> Since we are talking about the whole path (including the host), not just
> file names; "path" is a well-defined computing term and the draft itself
> uses it. (But not really the fragment, which is not part of the path.) The
> text of Section 4 does not need to be changed.
>
>
​Actually, the host isn't part of the path, and this doesn't cover the host
anyway (that's handled by the term "fully qualified domain name" and the
ABNF for `host`.) The text actually talks about the file system encoding
(i.e. file path/name) rather than URI encoding. I was wondering about "File
Path Encoding" as a title, but I stuck with the suggested "File Name
Encoding" because I think people get it (it's only a title, after all, not
an interop-dependent normative requirement), and we've previously stated
that directories can be treated as files, so dirname encoding should also
be covered by filename encoding.​

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