Re: [Uri-review] Review Provisional registration for app URI scheme

Stian Soiland-Reyes <stain@apache.org> Tue, 23 January 2018 14:59 UTC

Return-Path: <stain@apache.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92703126C2F for <uri-review@ietfa.amsl.com>; Tue, 23 Jan 2018 06:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.93
X-Spam-Level:
X-Spam-Status: No, score=-14.93 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] 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 PfariksWfOkn for <uri-review@ietfa.amsl.com>; Tue, 23 Jan 2018 06:59:03 -0800 (PST)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by ietfa.amsl.com (Postfix) with SMTP id 30521126C23 for <uri-review@ietf.org>; Tue, 23 Jan 2018 06:59:03 -0800 (PST)
Received: (qmail 43111 invoked by uid 99); 23 Jan 2018 14:59:02 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jan 2018 14:59:02 +0000
Received: from localhost (cspool35.cs.man.ac.uk [130.88.195.135]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id F170F1A0068; Tue, 23 Jan 2018 14:59:01 +0000 (UTC)
Date: Tue, 23 Jan 2018 14:58:59 +0000
Message-ID: <20180123145859.GE6221@biggie>
From: Stian Soiland-Reyes <stain@apache.org>
To: Graham Klyne <gk@ninebynine.org>
Cc: uri-review@ietf.org
In-Reply-To: <5A6711D9.6010403@ninebynine.org>
References: <20180117144647.GC5245@biggie> <4d910f73-9ca4-c661-0ff1-f508b8ccbed2@gmx.de> <FCE36985-BDC4-419E-97AB-CC061B43A9C7@tzi.org> <CAMBJEmU2s8B8Rvz-GW=3n4Dt0c_qCQHzm1M52GpAXn+qQmHzvw@mail.gmail.com> <AFAEFB6C-CD3E-4BD1-B1B5-35E9749D45FC@tzi.org> <CAMBJEmWgTasuKMPhTXUBLgSuDKBXo+M1Eq98t-8=Ya+kKqgYXQ@mail.gmail.com> <BB6CCAEA-7604-4056-AFD4-A5FE87559973@tzi.org> <CAMBJEmUDEGz=vLQN-XGpkS7cF+TFAyc98RsYJSKDRkw5bJn7ww@mail.gmail.com> <65DA395C-3DD5-4E46-BB44-4660578F681E@gbiv.com> <5A647445.5050200@ninebynine.org> <20180122013403.GC855@biggie> <5A6711D9.6010403@ninebynine.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/BM27TawfyiaXi_ftezTk6S_e45s>
Subject: Re: [Uri-review] Review Provisional registration for app URI scheme
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 14:59:05 -0000

On Tue, 23 Jan 2018 10:43:37 +0000, Graham Klyne <gk@ninebynine.org>; wrote:
> https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Security/Security_model#Packaged_Apps
> 
> The historical use could IMO constitute a "compelling practical reason", 
> depending on the scope and nature of its deployment.  A registration of 'app' as 
> historical, or a note about it's origins in the registration template for the 
> revised scheme might be options to consider here.

Yes, perhaps such an historical registration can also point forward to
the arcp registration.  

I'll keep (but modify) the "History" section in the arcp Internet-Draft.

> I think local-use URI schemes (like app was?) create a kind of messy corner 
> case: the local-use may be fine until (a) someone wants to use the same name for 
> something else on the global network, or (b) the scheme leaks from its local 
> use.  I sometimes think of these as "URI-like strings" rather than full-on URIs, 
> but I'm sure others would have different perspectives.

Yes, this is why early specifications of widget URI scheme strongly
recommended UUID authorities, so that such URIs would be safe to leak
(although non-functioning outside the local system).  For whatever
reason this recommendation was lifted in later app-uri specs which
increased risk of collisions.

I am ambivalent if my proposed "name," prefix should be kept in "arcp"
or if we should only recommend UUID or hash.

(but at least with DNS names you will mainly collide with yourself :)  

-- 
Stian Soiland-Reyes
The University of Manchester
http://www.esciencelab.org.uk/
http://orcid.org/0000-0001-9842-9718