One document matched: draft-hammer-webfinger-00.xml

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>

<rfc category="exp" ipr="trust200902" docName="draft-hammer-webfinger-00">

  <?rfc strict="yes" ?>
  <?rfc toc="yes" ?>
  <?rfc tocdepth="2" ?>
  <?rfc symrefs="yes" ?>
  <?rfc sortrefs="yes" ?>
  <?rfc compact="yes" ?>
  <?rfc subcompact="no" ?>

  <front>
    
    <title>The WebFinger Protocol</title>

    <author initials="E" surname="Hammer-Lahav" fullname="Eran Hammer-Lahav" role="editor">
      <organization>
        Yahoo!
      </organization>
      <address>
        <email>eran@hueniverse.com</email>
        <uri>http://hueniverse.com</uri>
      </address>
    </author>

    <author initials="B" surname="Fitzpartick" fullname="Brad Fitzpatrick">
      <organization>
        Google
      </organization>
      <address>
        <email>brad@fitzpat.com</email>
        <uri>http://www.bradfitz.com</uri>
      </address>
    </author>
    
    <author initials="B" surname="Cook" fullname="Blaine Cook">
      <organization>
        BT
      </organization>
      <address>
        <email>romeda@gmail.com</email>
        <uri>http://romeda.org/</uri>
      </address>
    </author>

    <date year="2009"/>

    <abstract>
      <t>
        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.
      </t>
    </abstract>
  
  </front>

  <middle>
    <section title="Introduction">
      <t>
        [[ TBD ]]
      </t>
    </section>

    <section title="Notational Conventions">
      <t>
        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
        <xref target="RFC2119" />.
      </t>
      <t>
        This document uses the Augmented Backus-Naur Form (ABNF) notation of <xref target="RFC5234" />.
        Additionally, the following rules are included from <xref target="RFC3986" />: reserved and
        unreserved.
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>
        [[ TBD ]]
      </t>
    </section>

    <section title="IANA Considerations">
      <t>
        This memo includes no request to IANA.
      </t>
    </section>

    <appendix title="Acknowledgments">
      <t>
        [[ TBD ]]
      </t>
    </appendix>

    <appendix title="Document History">
      <t>
        [[ to be removed by the RFC editor before publication as an RFC ]]
      </t>
      <t>
        -00

        <list style="symbols">
          <t>
            Initial (empty) draft.
          </t>
        </list>
      </t>
    </appendix>
  
  </middle>

  <back>

    <references title="Normative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5234.xml"?>
    </references>
    
  </back>

</rfc>