WebFinger
draft-jones-appsawg-webfinger-04

The information below is for an old version of the document
Document Type Active Internet-Draft (candidate for appsawg WG)
Last updated 2012-05-04
Replaced by draft-ietf-appsawg-webfinger
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state Call For Adoption By WG Issued
Awaiting Merge with Other Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      Paul E. Jones
Internet Draft                                         Gonzalo Salgueiro
Intended status: Standards Track                           Cisco Systems
Expires: November 4, 2012                                   Joseph Smarr
                                                                  Google
                                                             May 4, 2012

                                 WebFinger
                   draft-jones-appsawg-webfinger-04.txt

Abstract

   This specification defines the WebFinger protocol.  WebFinger may be
   used to discover information about people on the Internet, such as a
   person's personal profile address, identity service, telephone
   number, or preferred avatar.  WebFinger may also be used to learn
   information about objects on the network, such as the amount of toner
   in a printer or the physical location of a server.

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 November 4, 2012.

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

Jones, et al.          Expires November 4, 2012                 [Page 1]
Internet-Draft                WebFinger                         May 2012

   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

   1. Introduction...................................................2
   2. Terminology....................................................3
   3. Example Uses of WebFinger......................................3
      3.1. Locating a User's Blog....................................3
      3.2. Retrieving a Person's Contact Information.................5
      3.3. Simplifying the Login Process.............................6
      3.4. Retrieving Device Information.............................7
   4. WebFinger Protocol.............................................8
      4.1. Performing a WebFinger Query..............................8
      4.2. The Web Host Metadata "resource" Parameter................9
      4.3. The Web Host Metadata "rel" Parameter....................11
   5. The "acct" URI................................................12
      5.1. Using the "acct" URI.....................................12
      5.2. Syntax of "acct" URI.....................................13
   6. The "acct" Link Relation......................................13
      6.1. Purpose for the "acct" Link Relation.....................13
      6.2. Example Message Exchange Using the "acct" Link Relation..14
   7. Cross-Origin Resource Sharing (CORS)..........................15
   8. Controlling Access to Information.............................15
   9. Security Considerations.......................................16
   10. IANA Considerations..........................................17
      10.1. Registration of the "acct" URI scheme name..............17
      10.2. Registration of the "acct" Link Relation Type...........17
   11. Acknowledgments..............................................18
   12. References...................................................18
      12.1. Normative References....................................18
      12.2. Informative References..................................19
   Author's Addresses...............................................20

1. Introduction

   There is a utility found on UNIX systems called "finger" [14] that
   allows a person to access information about another person.  The
Show full document text