Re: [apps-discuss] I-D Action: draft-ietf-appsawg-file-scheme-09.txt

Matthew Kerwin <matthew@kerwin.net.au> Sun, 15 May 2016 12:24 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 BC75C12B024; Sun, 15 May 2016 05:24:10 -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 n8X-oRP1g-Tt; Sun, 15 May 2016 05:24:09 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 2907F12D09B; Sun, 15 May 2016 05:24:09 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id f89so181397353ioi.0; Sun, 15 May 2016 05:24:09 -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=1A+Vj1mdcFGvWgp6tCN308U57gzS9Y9XcE1/YJkm5lE=; b=bbHfmy1PFaVOrDSNN3eTVQJc9zsbrSM+i1WLaZGCnqcZbUywBrpRy++AbhDR89kLg2 gagEk8blQnU/J/AyctIWlzMpKgw9f80WTSWZCX9AVT8yiv6rgE7wA/m6Ok9aefxFuaBK YxmXzKxb/CAFTozzqMtwo6C0zmneT40BOMuaG2Zg1+BFbRGK7/jzlnOGBNZtdW6OaeKn lpFYGw/stycZxHcHx1vItHwBDeog9T3JscW98KgrtfTHEgLKifGwk0ljyAhJMWFGiUz5 UeU2YOZH0G/+ahN5p9OL0N4jAGmmULiQd5KIdxr4UE2PL6jJI0ATSldNFpkGrI1NhZmT M0fw==
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=1A+Vj1mdcFGvWgp6tCN308U57gzS9Y9XcE1/YJkm5lE=; b=gHoMv8gSE73PbdbktlObcc2K0+531XSWHmoi7yopVGOk87jsmqb51RZBQc/B+hCocK pzEQGiN6+Yg2LXGPel2Bloa4Pi0hLRPAKT3S+9YE29EJUo8Hl9/gdMWQIZKZrCABPBIk 23PVUXj2Y/IH0xRf8Xv79iCLQ9m3OAen7ylpEHVfnbYyVy/oEvD0m+c95U8KBtTq/+Ac bXwSxc2HAF22Uc/juynijVUVLaz1ppTtCLJhJAtvPDNC6x4Bh4a3IRyWrb0/9fMrsLSR 5gM5PWzBakQjTEI10Vo/d9CrbQsS9OqGOyQzer4P5HpMpt7nWUd6O1DVYNLyKp3etO4v RVpw==
X-Gm-Message-State: AOPr4FWqLV+nRE9PxKFi29dlyx6Z7/lxSJeShud80mdbO+C0dxx8wW9uiArDkuL2MUhqixLQaiUcY31BovfBlg==
MIME-Version: 1.0
X-Received: by 10.107.56.131 with SMTP id f125mr16600232ioa.188.1463315048441; Sun, 15 May 2016 05:24:08 -0700 (PDT)
Sender: phluid61@gmail.com
Received: by 10.107.138.230 with HTTP; Sun, 15 May 2016 05:24:08 -0700 (PDT)
In-Reply-To: <c52370bf-dffa-4b57-9f33-52a49456b3a8@seantek.com>
References: <20160515051508.2444.90815.idtracker@ietfa.amsl.com> <c52370bf-dffa-4b57-9f33-52a49456b3a8@seantek.com>
Date: Sun, 15 May 2016 22:24:08 +1000
X-Google-Sender-Auth: V7Zvddg1FZ4NYJls3VzXIsWl0nQ
Message-ID: <CACweHNBuR8X_ub6J-yOtvoV7CjZyDC5__qKNHWGtxsjZbvyB0w@mail.gmail.com>
From: Matthew Kerwin <matthew@kerwin.net.au>
To: Sean Leonard <dev+ietf@seantek.com>
Content-Type: multipart/alternative; boundary=001a114ac8d0a833b20532e095a5
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/3Nhe-4ykyt2Ak-Z7R6V8UcmQs0g>
Cc: draft-ietf-appsawg-file-scheme@ietf.org, IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] I-D Action: draft-ietf-appsawg-file-scheme-09.txt
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 12:24:11 -0000

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

> On 5/14/2016 10:15 PM, internet-drafts@ietf.org wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the ART Area General Applications Working
>> Group of the IETF.
>>
>>          Title           : The file URI Scheme
>>          Author          : Matthew Kerwin
>>         Filename        : draft-ietf-appsawg-file-scheme-09.txt
>>         Pages           : 18
>>         Date            : 2016-05-14
>>
>
> Did a full review; looks very good. Nice work!
>
> The References section lists several references to MSDN articles.
>
> Shorter MSDN article URLs are of the form:
> https://msdn.microsoft.com/library/{ARTICLEID}
>
> Such as:
> https://msdn.microsoft.com/library/gg465305
> https://msdn.microsoft.com/library/aa365247
>
> I suggest simplifying the links, and updating the dates. Note that some
> library articles have dates; others do not. For example, [MS-DTYP] is most
> recently dated October 16, 2015, revision 30.0, according to its changelog
> at article ID cc230273.
>
>
​Well, I did access the en-us versions. When I go to the short URL you
linked above, I get the en-au versions ;)

Nevertheless I can refresh the references and update the dates. I'm
confused, though; MS-DTYP now includes an ABNF (which is cool) but it's
broken (which is not cool.) I think I know what they meant to say, but
that's not what they've actually said. I don't feel great referencing that,
even informatively.
​


> In Appendix C, a discussion of Win32 Namespaces is given, but then it says
> "This specification does not define a mechanism for translating namespaced
> paths to or from file URIs." Readers would appreciate an informative
> reference for a mechanism to translate namespaced paths to and from file
> URIs, especially since there is a lot of technical content about Win32
> processing in the rest of the Appendices.
>
>
​They might, but I don't have one. What would you suggest? What is
currently done?
​


> I believe that the (American) English capitalization of Appendix D should
> be:
> Appendix D. System-Specific Operations
>
>
​Sure, I can do that.
​

Just curious: what happens if you try to access
file://USERNAME@HOST/foo/bar.txt
> on a Windows UNC/network share, using a Windows machine and suitable API
> operations (e.g., Internet Explorer)? Will Windows try to access the
> network path with the given username, or something else? And does USER:PASS
> work?
>
>
​Didn't work for me in IE11, with any combination of @, user@, user:pass@.
Incidentally, it was also happy to accept both "c$" and "c%24" to access
the magic C:\ share.

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