Re: [apps-discuss] FW: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt

Dave Thaler <dthaler@microsoft.com> Fri, 11 October 2013 17:50 UTC

Return-Path: <dthaler@microsoft.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 01A0321E81EC for <apps-discuss@ietfa.amsl.com>; Fri, 11 Oct 2013 10:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.546
X-Spam-Level:
X-Spam-Status: No, score=-103.546 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LjtHcQx8ImGo for <apps-discuss@ietfa.amsl.com>; Fri, 11 Oct 2013 10:50:05 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0154.outbound.protection.outlook.com [207.46.163.154]) by ietfa.amsl.com (Postfix) with ESMTP id 3E6AF21E81E4 for <apps-discuss@ietf.org>; Fri, 11 Oct 2013 10:50:04 -0700 (PDT)
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) with Microsoft SMTP Server (TLS) id 15.0.800.7; Fri, 11 Oct 2013 17:50:00 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.163]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.163]) with mapi id 15.00.0800.005; Fri, 11 Oct 2013 17:50:00 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Tony Hansen <tony@att.com>
Thread-Topic: [apps-discuss] FW: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt
Thread-Index: AQHOxce7UfreuZ9+VUWiXUx23KuGZ5nuBJaQgAAD1gCAAAIscIAACccAgAAHs5CAAAbYgIABpRPQ
Date: Fri, 11 Oct 2013 17:49:59 +0000
Message-ID: <787b0d38ce9d43d2a93cd5a89b0855c6@BY2PR03MB269.namprd03.prod.outlook.com>
References: <20131010144721.30339.98848.idtracker@ietfa.amsl.com> <7e12b97cac364127b5ab56574eecf627@BY2PR03MB269.namprd03.prod.outlook.com> <c4gd591k17rvsrcn0prrafkudknqsbaahl@hive.bjoern.hoehrmann.de> <23c10ed0337840bd91fb413e9160a4d0@BY2PR03MB269.namprd03.prod.outlook.com> <7mid59tid3u4apv460egn4an94h1mre6a6@hive.bjoern.hoehrmann.de> <1fdc5b0c5ef043d4884aabd31a3d8c81@BY2PR03MB269.namprd03.prod.outlook.com> <5256D82B.2060602@att.com>
In-Reply-To: <5256D82B.2060602@att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e8:ee31::3]
x-forefront-prvs: 0996D1900D
x-forefront-antispam-report: SFV:NSPM; SFS:(189002)(479174003)(377454003)(199002)(24454002)(46102001)(80022001)(81542001)(65816001)(56776001)(80976001)(54316002)(74366001)(56816003)(81342001)(74502001)(81816001)(47446002)(53806001)(54356001)(15975445006)(19580395003)(15202345003)(33646001)(74706001)(74662001)(81686001)(74876001)(19580405001)(83322001)(69226001)(85306002)(76786001)(4396001)(59766001)(77982001)(74316001)(19300405004)(76796001)(83072001)(63696002)(77096001)(51856001)(16236675002)(47736001)(49866001)(50986001)(47976001)(31966008)(79102001)(76482001)(76576001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR03MB269; H:BY2PR03MB269.namprd03.prod.outlook.com; CLIP:2001:4898:80e8:ee31::3; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_787b0d38ce9d43d2a93cd5a89b0855c6BY2PR03MB269namprd03pro_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] FW: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 11 Oct 2013 17:50:11 -0000

Yes, I know, I've reviewed that document many times.   I considered referencing it in my draft
but ended up deleting references to it because it didn't really change the problem statement.
I could add the reference back in in a -01 if it would help.

So in short: no the latest version does not address the issues or I would have just been arguing
for publishing it as is.  However, that is the doc that I would expect the solution to the problems
to be done in, but as I'm not currently a co-author (about the time IRI WG was closed, I did
volunteer to help edit the document as I do think it's important) and because I want to focus
discussion on the problem without presuming a particular solution, I wrote a separate draft
for now that I would expect to go away once we decide on an appropriate direction.

-Dave

From: Tony Hansen [mailto:tony@att.com]
Sent: Thursday, October 10, 2013 9:39 AM
To: Dave Thaler
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] FW: New Version Notification for draft-thaler-uri-scheme-reg-ps-00.txt

On 10/10/2013 12:16 PM, Dave Thaler wrote:

Ok, let me try to answer that.  RFC 4395 defines a set of goals which are

quoted in section 1.  The current mechanism does not meet those goals.

To really meet the stated goals would require the majority of schemes to

be registered.  The current process cannot scale to do so, given current

practice.  Hence we either need to change the process or change the goals

or both.

Dave, please take a look at draft-ietf-iri-4395bis-irireg. This was an effort to update 4395 for many of the issues you raise as well as updating 4395 for IRIs. Work on it paused when the IRI WG imploded.

If you ignore the changes oriented around IRIs, does what is documented there solve the problems that you bring up? (I admit I have not taken your document and done a side-by-side check.)

The editors of that draft have discussed resurrecting work on that draft without the IRI working group, but haven't received the kick in the pants needed to do so.

    Tony Hansen