The 'acct' URI Scheme
draft-ietf-appsawg-acct-uri-03

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Last updated 2013-03-28 (latest revision 2013-02-18)
Replaces draft-saintandre-acct-uri
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Salvatore Loreto
Shepherd write-up Show (last changed 2013-02-20)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 4 more YES or NO OBJECTION positions to pass.
Responsible AD Barry Leiba
IESG note Salvatore Loreto (salvatore.loreto@ericsson.com) is the document shepherd.
Send notices to appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-acct-uri@tools.ietf.org
IANA IANA review state IANA - Review Needed
IANA action state None
Network Working Group                                     P. Saint-Andre
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                       February 18, 2013
Expires: August 22, 2013

                         The 'acct' URI Scheme
                     draft-ietf-appsawg-acct-uri-03

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 August 22, 2013.

Copyright Notice

   Copyright (c) 2013 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.

Table of Contents

Saint-Andre             Expires August 22, 2013                 [Page 1]
Internet-Draft           The 'acct' URI Scheme             February 2013

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Definition  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

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 without
   specifying a particular protocol to use when interacting with the
   account.  This specification fills that gap.

2.  Rationale

   During formalization of the WebFinger protocol
   [I-D.ietf-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' [RFC6068] and
   'http' [RFC2616] schemes were proposed, not all service providers
   offer email services or web interfaces on behalf of user accounts
   (e.g., a microblogging or instant messaging provider might not offer
   email services, or an enterprise might not offer 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 application protocols 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 "user@host", the
   scheme is designed for the purpose of identification instead of
   interaction (regarding this distinction, see Section 1.2.2 of
Show full document text