[Uri-review] request for review: 'acct' scheme

Peter Saint-Andre <stpeter@stpeter.im> Thu, 10 January 2013 03:32 UTC

Return-Path: <stpeter@stpeter.im>
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 DFC051F0D06 for <uri-review@ietfa.amsl.com>; Wed, 9 Jan 2013 19:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level:
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOaxcwebIDZy for <uri-review@ietfa.amsl.com>; Wed, 9 Jan 2013 19:32:47 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 24CCC1F0D03 for <uri-review@ietf.org>; Wed, 9 Jan 2013 19:32:47 -0800 (PST)
Received: from [192.168.1.200] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6FE0D40564; Wed, 9 Jan 2013 20:37:58 -0700 (MST)
Message-ID: <50EE365E.80302@stpeter.im>
Date: Wed, 09 Jan 2013 20:32:46 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "uri-review@ietf.org" <uri-review@ietf.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [Uri-review] request for review: 'acct' scheme
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: Thu, 10 Jan 2013 03:32:48 -0000

This message constitutes a request for review of the proposed 'acct' URI
scheme, specified in draft-ietf-appsawg-acct-uri-02. The completed
registration template follows (copied from the IANA Considerations of
the aforementioned I-D).

Peter

###

4. IANA Considerations

   In accordance with the guidelines and registration procedures for new
   URI schemes [RFC4395], this section provides the information needed
   to register the 'acct' URI scheme.

4.1. URI Scheme Name

   acct

4.2. Status

   permanent

4.3. URI Scheme Syntax

   The 'acct' URI syntax is defined here in Augmented Backus-Naur Form
   (ABNF) [RFC5234], borrowing the 'host', 'pct-encoded', 'sub-delims',
   'unreserved' rules from [RFC3986]:

   acctURI      =  "acct" ":" userpart "@" host
   userpart     =  1*( unreserved / pct-encoded / sub-delims )

4.4. URI Scheme Semantics

   The 'acct' URI scheme identifies accounts hosted at service
   providers.  It is used only for identification, not interaction.  A
   protocol that employs the 'acct' URI scheme is responsible for
   specifying how an 'acct' URI is dereferenced in the context of that
   protocol.  There is no media type associated with the 'acct' URI
   scheme.

4.5. Encoding Considerations

   The 'acct' URI scheme allows any character from the Unicode
   repertoire [UNICODE] encoded as UTF-8 [RFC3629] and then percent-
   encoded into valid ASCII [RFC20] as specified in [RFC3986].  Note
   that domain labels need to be encoded as A-labels (see [RFC5890]) in
   order to support internationalized domain names (IDNs).

4.6. Applications/Protocols That Use This URI Scheme Name

   At the time of this writing, only the WebFinger protocol uses the
   'acct' URI scheme.  However, use is not restricted to the WebFinger
   protocol, and the scheme might be considered for use in other
   protocols, such as Simple Web Discovery.

4.7. Interoperability Considerations

   There are no known interoperability concerns related to use of the
   'acct' URI scheme.

4.8. Security Considerations

   See Section 5 of RFCXXXX.  [Note to RFC Editor: please replace XXXX
   with the number issued to this document.]

4.9. Contact

   Peter Saint-Andre, psaintan@cisco.com

4.10. Author/Change Controller

   This scheme is registered under the IETF tree.  As such, the IETF
   maintains change control.

4.11. References

   None.

###