idnits 2.17.1 draft-hammer-webfinger-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 20, 2009) is 5300 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Hammer-Lahav, Ed. 3 Internet-Draft Yahoo! 4 Intended status: Experimental B. Fitzpartick 5 Expires: April 23, 2010 Google 6 B. Cook 7 BT 8 October 20, 2009 10 The WebFinger Protocol 11 draft-hammer-webfinger-00 13 Status of this Memo 15 This Internet-Draft is submitted to IETF in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on April 23, 2010. 36 Copyright Notice 38 Copyright (c) 2009 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents in effect on the date of 43 publication of this document (http://trustee.ietf.org/license-info). 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. 47 Abstract 49 This memo specifies the WebFinger, a protocol for obtaining account 50 metadata, as well as the 'acct' URI scheme. 'acct' URIs are used to 51 identify user accounts at a given host which are typically used for 52 the purpose of resource management and establishing identity. User 53 accounts include a local identifier (username, screenname, or 54 handle), and a host which can resolve and usually authenticate the 55 local identifier. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 61 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 62 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 63 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 3 64 Appendix B. Document History . . . . . . . . . . . . . . . . . . . 3 65 5. Normative References . . . . . . . . . . . . . . . . . . . . . 3 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1. Introduction 70 [[ TBD ]] 72 2. Notational Conventions 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 76 document are to be interpreted as described in [RFC2119]. 78 This document uses the Augmented Backus-Naur Form (ABNF) notation of 79 [RFC5234]. Additionally, the following rules are included from 80 [RFC3986]: reserved and unreserved. 82 3. Security Considerations 84 [[ TBD ]] 86 4. IANA Considerations 88 This memo includes no request to IANA. 90 Appendix A. Acknowledgments 92 [[ TBD ]] 94 Appendix B. Document History 96 [[ to be removed by the RFC editor before publication as an RFC ]] 98 -00 100 o Initial (empty) draft. 102 5. Normative References 104 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 105 Requirement Levels", BCP 14, RFC 2119, March 1997. 107 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 108 Resource Identifier (URI): Generic Syntax", STD 66, 109 RFC 3986, January 2005. 111 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 112 Specifications: ABNF", STD 68, RFC 5234, January 2008. 114 Authors' Addresses 116 Eran Hammer-Lahav (editor) 117 Yahoo! 119 Email: eran@hueniverse.com 120 URI: http://hueniverse.com 122 Brad Fitzpatrick 123 Google 125 Email: brad@fitzpat.com 126 URI: http://www.bradfitz.com 128 Blaine Cook 129 BT 131 Email: romeda@gmail.com 132 URI: http://romeda.org/