Re: [APPS-REVIEW] Review of draft-merrick-jms-uri-05

Mark Baker <distobj@acm.org> Wed, 25 March 2009 00:46 UTC

Return-Path: <mark@coactus.com>
X-Original-To: apps-review@core3.amsl.com
Delivered-To: apps-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB36E3A69E1 for <apps-review@core3.amsl.com>; Tue, 24 Mar 2009 17:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hGYRbzONpFZW for <apps-review@core3.amsl.com>; Tue, 24 Mar 2009 17:46:43 -0700 (PDT)
Received: from mail-gx0-f208.google.com (mail-gx0-f208.google.com [209.85.217.208]) by core3.amsl.com (Postfix) with ESMTP id CC8973A6A31 for <apps-review@ietf.org>; Tue, 24 Mar 2009 17:46:43 -0700 (PDT)
Received: by gxk4 with SMTP id 4so7121548gxk.13 for <apps-review@ietf.org>; Tue, 24 Mar 2009 17:47:35 -0700 (PDT)
MIME-Version: 1.0
Sender: mark@coactus.com
Received: by 10.150.189.9 with SMTP id m9mr16071790ybf.18.1237942055144; Tue, 24 Mar 2009 17:47:35 -0700 (PDT)
In-Reply-To: <49C483AD.2000700@alvestrand.no>
References: <498B7309.5080006@alvestrand.no> <49C43146.1070100@tibco.com> <49C483AD.2000700@alvestrand.no>
Date: Tue, 24 Mar 2009 17:47:35 -0700
X-Google-Sender-Auth: e3f69200ef5d1b06
Message-ID: <e9dffd640903241747tdb75fb9ne450594d0cf38dc9@mail.gmail.com>
From: Mark Baker <distobj@acm.org>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: derek.rokicki@softwareag.com, apps-review@ietf.org, Lisa Dusseault <lisa@osafoundation.org>, peaston@progress.com, Eric Johnson <eric@tibco.com>, roland@uk.ibm.com
Subject: Re: [APPS-REVIEW] Review of draft-merrick-jms-uri-05
X-BeenThere: apps-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Applications Review List <apps-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-review>
List-Post: <mailto:apps-review@ietf.org>
List-Help: <mailto:apps-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-review>, <mailto:apps-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2009 00:46:44 -0000

On Fri, Mar 20, 2009 at 11:05 PM, Harald Alvestrand
<harald@alvestrand.no> wrote:
> Thanks - those words help.
> The important point is that use of the URI depends on a shared context, and
> that context cannot be identified from the URI. Indeed, there may be valid
> cases where the same URI is resolvable in two different contexts, with two
> different results.
>
> That leaves me sad, because it is exactly opposite to what the "U" in "URI"
> sometimes stood for,

Me too 8-(

IMO this registration should be provisional, not permanent, because it
doesn't meet the requirements of sec 2.1 of RFC 4395;

   The use and deployment of new URI schemes in the Internet
   infrastructure is costly; some parts of URI processing may be
   scheme-dependent, and deployed software already processes URIs of
   well-known schemes.  Introducing a new URI scheme may require
   additional software, not only for client software and user agents but
   also in additional parts of the network infrastructure (gateways,
   proxies, caches) [11].  URI schemes constitute a single, global
   namespace; it is desirable to avoid contention over use of short,
   mnemonic scheme names.  For these reasons, the unbounded registration
   of new schemes is harmful.  New URI schemes SHOULD have clear utility
   to the broad Internet community, beyond that available with already
   registered URI schemes.

Mark.