The WebFinger Protocol
draft-hammer-webfinger-00

Status of this Memo

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

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

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.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on April 23, 2010.

Copyright Notice

Copyright (c) 2009 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 in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.

Abstract

This memo specifies the WebFinger, a protocol for obtaining account metadata, as well as the 'acct' URI scheme. 'acct' URIs are used to identify user accounts at a given host which are typically used for the purpose of resource management and establishing identity. User accounts include a local identifier (username, screenname, or handle), and a host which can resolve and usually authenticate the local identifier.

Table of Contents

1.  Introduction
2.  Notational Conventions
3.  Security Considerations
4.  IANA Considerations
Appendix A.  Acknowledgments
Appendix B.  Document History
5.  Normative References
§  Authors' Addresses

1.  Introduction

[[ TBD ]]

2.  Notational Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

This document uses the Augmented Backus-Naur Form (ABNF) notation of [RFC5234] (Crocker, D. and P. Overell, “Augmented BNF for Syntax Specifications: ABNF,” January 2008.). Additionally, the following rules are included from [RFC3986] (Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax,” January 2005.): reserved and unreserved.

3.  Security Considerations

[[ TBD ]]

4.  IANA Considerations

This memo includes no request to IANA.

Appendix A.  Acknowledgments

[[ TBD ]]

Appendix B.  Document History

[[ to be removed by the RFC editor before publication as an RFC ]]

-00

• Initial (empty) draft.

5. Normative References

Authors' Addresses