The 'acct' URI Scheme
draft-saintandre-acct-uri-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-06-30
Replaced by rfc7565, draft-ietf-appsawg-acct-uri
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     P. Saint-Andre
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                           June 30, 2012
Expires: January 1, 2013

                         The 'acct' URI Scheme
                      draft-saintandre-acct-uri-00

Abstract

   This document defines the 'acct' URI scheme as a way to identify a
   user's account at a service provider, irrespective of the particular
   protocols that can be used to interact with the account.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 1, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Saint-Andre              Expires January 1, 2013                [Page 1]
Internet-Draft            The 'acct' URI Scheme                June 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Definition  . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 7

Saint-Andre              Expires January 1, 2013                [Page 2]
Internet-Draft            The 'acct' URI Scheme                June 2012

1.  Introduction

   Existing URI schemes that enable interaction with, or that identify
   resources associated with, a user's account at a service provider are
   tied to particular services or application protocols.  Two examples
   are the 'mailto' scheme (which enables interaction with a user's
   email account) and the 'http' scheme (which enables retrieval of web
   files controlled by a user or interaction with interfaces providing
   information about a user).  However, there exists no URI scheme that
   generically identifies a user's account at a service provider, in the
   absence of interaction with the account using a particular
   application protocol.  This specification fills that gap.

2.  Rationale

   During formalization of the WebFinger protocol
   [I-D.jones-appsawg-webfinger], much discussion occurred regarding the
   appropriate URI scheme to include when specifying a user's account as
   a web link [RFC5988].  Although both the 'mailto' and 'http' schemes
   were proposed, not all service providers support email services or
   web interfaces on behalf of user accounts (e.g., a microblogging or
   instant messaging provider might not provide email services, or an
   enterprise might not provide HTTP interfaces to information about its
   employees).  Therefore, the discussants recognized that it would be
   helpful to define a URI scheme that could be used to generically
   identify a user's account at a service provider, irrespective of the
   particular services or application protocols that could be used to
   interact with the account.  The result was the 'acct' URI scheme
   defined in this document.

3.  Definition

   The syntax of the 'acct' URI scheme is defined under Section 4 of
   this document.  Although 'acct' URIs take the form
   userpart@domainpart, the scheme is designed for the purpose of
   identification instead of interaction (regarding this distinction,
Show full document text