Re: [Uri-review] New URI scheme for review

Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com> Tue, 11 October 2011 06:01 UTC

Return-Path: <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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 4ED9421F8D1B for <uri-review@ietfa.amsl.com>; Mon, 10 Oct 2011 23:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.87
X-Spam-Level:
X-Spam-Status: No, score=-100.87 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, FROM_LOCAL_NOVOWEL=0.5, 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 XvltJOzPufiP for <uri-review@ietfa.amsl.com>; Mon, 10 Oct 2011 23:01:09 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 465D521F8D18 for <uri-review@ietf.org>; Mon, 10 Oct 2011 23:01:09 -0700 (PDT)
Received: by wwf22 with SMTP id 22so6771510wwf.13 for <uri-review@ietf.org>; Mon, 10 Oct 2011 23:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=mbrzCi0G9Bpjyr4riJpZkvEsmbNJkkzMP3do9NrrRjw=; b=BgU3QQoj+8+c7d3tknUsbmJQwWzlRJQceGF4MivZjmYvj4sIjuUiMZnOSHWlTk/YfI 4VziAyTadlA6W/SCatUF8bX2NU6WElRZBfR2bn/UFT1W/W99mQ2hjmJ2kYBx1Ex/0wBJ unTwiBbTxDQVW2txc/p0TTgNXue+U4K37yKTg=
Received: by 10.227.12.15 with SMTP id v15mr7300791wbv.77.1318312868348; Mon, 10 Oct 2011 23:01:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.80.134 with HTTP; Mon, 10 Oct 2011 23:00:09 -0700 (PDT)
In-Reply-To: <CAHcUcOGgv8deMk3yw0FH8HrHee5Hi0pXcFCRwYDfaO_ta_nuGA@mail.gmail.com>
References: <CAHcUcOGgv8deMk3yw0FH8HrHee5Hi0pXcFCRwYDfaO_ta_nuGA@mail.gmail.com>
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Date: Tue, 11 Oct 2011 08:00:09 +0200
Message-ID: <CAHhFybrUH3TA5_pUkNi-5j82HZHhyt_Z4xibnQ8=JZ_dCXidDQ@mail.gmail.com>
To: Bob Van Zant <bob@eventbrite.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: uri-review@ietf.org
Subject: Re: [Uri-review] New URI scheme for review
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 Oct 2011 06:01:10 -0000

On 11 October 2011 01:30, Bob Van Zant <bob@eventbrite.com> wrote:

> It looks like most URI schemes like this one are never registered
> with IANA. It seems like The Right Thing to do and so I present to
> the list the URI scheme com-eventbrite-attendee.

Yeah.  I'd be tempted to reject it as "vanity URI scheme in conflict
with RFC 4395 2.1 Demonstratable, New, Long-Lived Utility", but that
might be not "the right thing", and besides only the expert reviewer
(= not me) could say so.

Disclaimer, I have not yet read the 4395bis drafts, maybe 4395bis
will drop the "long-lived utility" blurb in favour of a new "above
all let's have it registered" approach.

With that out of the way, are you sure that you want an OPTIONAL
query part in the syntax?  If the query part is actually REQUIRED
for this scheme maybe remove the square brackets in the syntax:

> URI scheme syntax.
>    uri = "com-eventbrite-attendee:" method [ "?" query ]
>    method = "resetpassword" / "tickets"

If you happen to have a web page with more technical details please
add it to the references.  If that is not (yet) the case it is no
problem, your explanation in the registration template is clear.

-Frank