Re: [apps-discuss] Fwd: FW: New Version Notification for draft-kerwin-file-scheme-13.txt

Larry Masinter <masinter@adobe.com> Sat, 10 January 2015 17:33 UTC

Return-Path: <masinter@adobe.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B12741A0231 for <apps-discuss@ietfa.amsl.com>; Sat, 10 Jan 2015 09:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 E_BmmWeG9IGD for <apps-discuss@ietfa.amsl.com>; Sat, 10 Jan 2015 09:33:21 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0084.outbound.protection.outlook.com [207.46.100.84]) (using TLSv1.2 with cipher AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D4731A0197 for <apps-discuss@ietf.org>; Sat, 10 Jan 2015 09:33:20 -0800 (PST)
Received: from DM2PR0201MB0960.namprd02.prod.outlook.com (25.160.216.28) by DM2PR0201MB0960.namprd02.prod.outlook.com (25.160.216.28) with Microsoft SMTP Server (TLS) id 15.1.53.17; Sat, 10 Jan 2015 17:33:19 +0000
Received: from DM2PR0201MB0960.namprd02.prod.outlook.com ([25.160.216.28]) by DM2PR0201MB0960.namprd02.prod.outlook.com ([25.160.216.28]) with mapi id 15.01.0053.000; Sat, 10 Jan 2015 17:33:19 +0000
From: Larry Masinter <masinter@adobe.com>
To: "t.petch" <ietfc@btconnect.com>, Sam Ruby <rubys@intertwingly.net>, Matthew Kerwin <matthew@kerwin.net.au>
Thread-Topic: [apps-discuss] Fwd: FW: New Version Notification for draft-kerwin-file-scheme-13.txt
Thread-Index: AQHP2Sc1jlL4BTpaWESzwAi/oPo9Z5yIE6gAgCO64gCAABuVgIAEleyAgAATjYCACUoxz4AAT/cA
Date: Sat, 10 Jan 2015 17:33:18 +0000
Message-ID: <DM2PR0201MB096038C48CC4F6B87AF39807C3450@DM2PR0201MB0960.namprd02.prod.outlook.com>
References: <20140926010029.26660.82167.idtracker@ietfa.amsl.com><EAACE200D9B0224D94BF52CF2DD166A425A68A90@ex10mb6.qut.edu.au><CACweHNBEYRFAuw9-vfeyd_wf703cvM3ykZoRMqAokRFYG_O7hQ@mail.gmail.com><DM2PR0201MB09602B351692D424A49C6B0DC3650@DM2PR0201MB0960.namprd02.prod.outlook.com><CACweHNBN_Bv=jeXQ_VwXi2HzHKNEwZJ1NiF-BJJo_9-mhO60gQ@mail.gmail.com><54A557E1.6050502@intertwingly.net> <CACweHNCQZg1U1u8U=-f6h0+BPnp6Wr_T=r_wGiPAbhTbuMCGWQ@mail.gmail.com> <54A94109.5010901@intertwingly.net> <00cf01d02cc7$d5dba4c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <00cf01d02cc7$d5dba4c0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2601:9:8380:992::644]
authentication-results: spf=none (sender IP is ) smtp.mailfrom=masinter@adobe.com;
x-dmarcaction-test: None
x-microsoft-antispam: BCL:0;PCL:0;RULEID:(3005003);SRVR:DM2PR0201MB0960;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:DM2PR0201MB0960;
x-forefront-prvs: 0452022BE1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(189002)(51704005)(377454003)(87936001)(76576001)(54206007)(97736003)(2656002)(77156002)(62966003)(122556002)(40100003)(99286002)(105586002)(106356001)(106116001)(74316001)(561944003)(101416001)(102836002)(54606007)(2420400003)(15975445007)(46102003)(19580395003)(33656002)(64706001)(76176999)(50986999)(54356999)(86362001)(93886004)(92566002)(2950100001)(230783001)(2900100001)(68736005)(7059030)(3826002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0201MB0960; H:DM2PR0201MB0960.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: adobe.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2015 17:33:19.0127 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fa7b1b5a-7b34-4387-94ae-d2c178decee1
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0201MB0960
Archived-At: <http://mailarchive.ietf.org/arch/msg/apps-discuss/H23zeRI_JxZV6zC4SLQOdw4446U>
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Fwd: FW: New Version Notification for draft-kerwin-file-scheme-13.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 10 Jan 2015 17:33:23 -0000

t.petch Sent: Saturday, January 10, 2015 3:23 AM

> I part company with you here.  IDNA processing can be avoided - don't
> do it!
> 
> Many of the IETF standards have no i18n in general, or IDNA in
> particular, just as the early standards' views of security would have
> hackers licking their lips with glee.
> 
> Retrospectively, security has been added to most protocols, i18n has
> been added to many.  The lack of security is a show stopper for most,
> but the lack of i18n limits the scope but still renders it useful for
> many so Matthew's I-D I see as a good step forward, all it needs to say
> is on this is that i18n (or IDNA) is for further study and we would
> still have a valuable RFC.

I'm not sure, but I think you're arguing that the "file:" URL scheme not specify the behavior of dealing with non-ASCII filenames. I don't think a document that didn't spec something would meet the criteria for Proposed Standard. 

There is a serious proposal to make some of the options of handling "file:" into "implementation dependent", but with leaving some kinds of relative path names interoperable, and  a discussion about how to structure the document so that implementations can be considered, registered, or described independently. About whether some of the specifications needed for normative reference are proprietary.

We actually have data about how implementations respond. There is an opportunity to make this corner of the web more openly specified so application writers can build platform-independent code using an interoperable subset, and platform builders and maintainers can know what to code to.

"for further study" is not generally found in IETF standards, although it is a technique used in academic papers and seen in other SDOs. We've studied. We're making progress. Keep going.

Larry
--
http://larry.masinter.net