[Uri-review] New URI scheme for review
Bob Van Zant <bob@eventbrite.com> Mon, 10 October 2011 23:30 UTC
Return-Path: <bob@eventbrite.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 A519321F8509 for <uri-review@ietfa.amsl.com>; Mon, 10 Oct 2011 16:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.75
X-Spam-Level:
X-Spam-Status: No, score=-0.75 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, URI_HEX=0.368]
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 SKeTiGLsVjRl for <uri-review@ietfa.amsl.com>; Mon, 10 Oct 2011 16:30:53 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2042121F84FB for <uri-review@ietf.org>; Mon, 10 Oct 2011 16:30:52 -0700 (PDT)
Received: by qyk32 with SMTP id 32so2402840qyk.10 for <uri-review@ietf.org>; Mon, 10 Oct 2011 16:30:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.8 with SMTP id l8mr4173201qci.168.1318289452499; Mon, 10 Oct 2011 16:30:52 -0700 (PDT)
Received: by 10.229.53.197 with HTTP; Mon, 10 Oct 2011 16:30:52 -0700 (PDT)
Date: Mon, 10 Oct 2011 16:30:52 -0700
Message-ID: <CAHcUcOGgv8deMk3yw0FH8HrHee5Hi0pXcFCRwYDfaO_ta_nuGA@mail.gmail.com>
From: Bob Van Zant <bob@eventbrite.com>
To: uri-review@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailman-Approved-At: Mon, 10 Oct 2011 19:44:05 -0700
Subject: [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: Mon, 10 Oct 2011 23:31:47 -0000
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. URI scheme name. com-eventbrite-attendee Status. provisional URI scheme syntax. uri = "com-eventbrite-attendee:" method [ "?" query ] method = "resetpassword" / "tickets" Example: com-eventbrite-attendee:resetpassword?email=user%40domain.com&token=DEADBEEF URI scheme semantics. This scheme is intended to be used by operating systems that have the Eventbrite Attendee application installed. When a URI with this scheme is encountered it is expected that the operating system launches the Eventbrite Attendee application with the method and query parameters specified in the URI. The exact semantics for how URL information is communicated to the Eventbrite Attendee app may vary on an operating system basis. The expectation is simply that the operating system follows its own conventions for passing the method and query parameters into the application. Encoding considerations. The scheme and method portions of this proposed URI avoid encoding issues by limiting itself to a subset of ASCII. The query portion of a com-eventbrite-attendee URI shall be encoded according to the rules in RFC 3986. Applications/protocols that use this URI scheme name. - Eventbrite Attendee for iOS - Eventbrite Attendee for Android Interoperability considerations. none. Security considerations. Against recommendations in RFC 3986 section 7.5 a com-eventbrite-attendee: URI may be used to transmit sensitive information. For example, it may be used to communicate a password reset token in email for a user following a "Forgot your password" flow. Though this token may have transmitted over insecure channels on its way to the application care must still be taken by application developers to not divulge this secret. RFC 3986 sections 7.2 and 7.5 apply Contact. Bob Van Zant Eventbrite 651 Brannan St San Francisco, CA 94103 USA EMail: bob@eventbrite.com Author/Change controller. Bob Van Zant References. Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
- [Uri-review] New URI scheme for review Bob Van Zant
- Re: [Uri-review] New URI scheme for review Frank Ellermann
- Re: [Uri-review] New URI scheme for review Bob Van Zant
- Re: [Uri-review] New URI scheme for review Mark Baker
- Re: [Uri-review] New URI scheme for review Frank Ellermann
- Re: [Uri-review] New URI scheme for review Martin J. Dürst
- Re: [Uri-review] New URI scheme for review Bob Van Zant
- Re: [Uri-review] New URI scheme for review Frank Ellermann
- Re: [Uri-review] New URI scheme for review Graham Klyne
- Re: [Uri-review] New URI scheme for review Mykyta Yevstifeyev
- Re: [Uri-review] New URI scheme for review Martin J. Dürst
- Re: [Uri-review] New URI scheme for review Mykyta Yevstifeyev
- Re: [Uri-review] New URI scheme for review Bob Van Zant
- Re: [Uri-review] New URI scheme for review Mykyta Yevstifeyev
- Re: [Uri-review] New URI scheme for review Bob Van Zant
- Re: [Uri-review] New URI scheme for review Frank Ellermann
- Re: [Uri-review] New URI scheme for review Martin J. Dürst
- Re: [Uri-review] New URI scheme for review Bob Van Zant
- Re: [Uri-review] New URI scheme for review Martin J. Dürst