One document matched: draft-sanchez-webdav-current-principal-00.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY rfc2616 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2616.xml">
<!ENTITY rfc3744 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3744.xml">
<!ENTITY rfc4918 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4918.xml">
]> 

<?rfc rfcedstyle="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?><!-- default = 3 -->
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<!-- <?rfc strict="yes"?> -->
<!-- <?rfc comments="yes"?> -->
<!-- <?rfc inline="yes"?> -->

<rfc ipr="full3978" docName="draft-sanchez-webdav-current-principal-00">
  <front>
    <title abbrev="WebDAV Current Principal">WebDAV Current Principal Extension</title>
    <author initials="W." surname="Sanchez" fullname="Wilfredo Sanchez">
      <organization abbrev="Apple Inc.">
        Apple Inc. 
      </organization>
      <address>
        <postal>
          <street>
            1 Infinite Loop 
          </street>
          <city>
            Cupertino
          </city>
          <region>
            CA 
          </region>
          <code>
            95014
          </code> 
          <country>
            USA 
          </country>
        </postal>
        <email>
          wsanchez@wsanchez.net
        </email>
        <uri>
          http://www.apple.com/ 
        </uri>
      </address>
    </author>
    <author initials="C." surname="Daboo" fullname="Cyrus Daboo">
      <organization abbrev="Apple Inc.">
        Apple Inc. 
      </organization>
      <address>
        <postal>
          <street>
            1 Infinite Loop 
          </street>
          <city>
            Cupertino
          </city>
          <region>
            CA 
          </region>
          <code>
            95014
          </code> 
          <country>
            USA 
          </country>
        </postal>
        <email>
          cyrus@daboo.name 
        </email>
        <uri>
          http://www.apple.com/ 
        </uri>
      </address>
    </author>
    <date year="2008" />
    <area>
      Applications 
    </area>
    <abstract>
      <t>
        This specification defines a new WebDAV property that allows clients to quickly determine the principal corresponding to the current authenticated user.
      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction">
      <t>
        WebDAV <xref target="RFC4918"/> is an extension to HTTP <xref target="RFC2616" /> to support improved document authoring capabilities. The WebDAV ACL <xref target="RFC3744"/> extension adds access control capabilities to WebDAV. It introduces the concept of a "principal resource" which is used to represent information about authenticated entities on the system.
      </t>
      <t>
        Some clients have a need to determine the <xref target="RFC3744"/> principal that a server is associating with the currently authenticated HTTP user.  While <xref target="RFC3744"/> defines a DAV:current-user-privilege-set property for retrieving the privileges granted to that principal, there is no recommended way to do identify the principal in question, which is necessary to perform other useful operations.  For example, a client may wish to determine which groups the current user is a member of, or modify a property of the principal resource associated with the current user.
      </t>
      <t>
        The DAV:principal-match REPORT provides some useful functionality, but there are common situations where the results from that query can be ambiguous (e.g. not only is an individual user principal returned, but also every group principal that the user is a member of, and there is no clear way to distinguish which is which).
      </t>
      <t>
        This specification proposes an extension to WebDAV ACL that adds a DAV:current-user-principal-resource property to all resources under access control on the server. This property contains a single DAV:href element whose value is a URL to the principal resource corresponding to the currently authenticated user.
      </t>
    </section>
    <section title="Conventions Used in This Document">
      <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>
        When XML element types in the namespace "DAV:" are referenced in this document outside of the context of an XML fragment, the string "DAV:" will be prefixed to the element type names. 
      </t>
    </section>
    <section title="DAV:current-user-principal-resource">
      <t>
<?rfc compact="no" ?>
          <list style="hanging">
            <t hangText="Name:">  
              current-user-principal-resource
            </t>
            <t hangText="Namespace:">
              DAV:
            </t>
            <t hangText="Purpose:">
              Indicates a URL for the current authenticated user's principal resource on the server.
            </t>
            <t hangText="Value:">
              Single DAV:href element.
            </t>
            <t hangText="Protected:">
              This property is computed on a per-request basis, and therefore is protected.
            </t>
            <t hangText="Description:">
              The DAV:current-user-principal-resource property contains either a DAV:href or DAV:unauthenticed XML element. The DAV:href element contains a URL to a principal resource corresponding to the currently authenticated user. That URL MUST be one of the URLs in the DAV:principal-URL or DAV:alternate-URI-set properties defined on the principal resource and MUST be an http(s) scheme URL. When authentication has not been done or has failed, this property MUST contain the DAV:unauthenticated pseudo-principal.
            </t>
            <t>
              In some cases there may be multiple principal resources corresponding to the same authenticated principal. In that case the server is free to choose any one of the principal resource URIs for the value of the DAV:current-user-principal-resource property. However, servers SHOULD be consistent and use the same principal resource URI for each authenticated principal.
            </t>
            <t hangText="COPY/MOVE behavior:">
              This property is computed on a per-request basis, and is thus never copied or moved.
            </t>
            <t hangText="Definition:">
              <figure>
                <artwork><![CDATA[
   <!ELEMENT current-user-principal-resource (DAV:unauthenticated |
                                              DAV:href)>
   DAV:href value: a URL to a principal resource
                ]]></artwork>
              </figure>
            </t>
            <t hangText="Example:">
              <figure>
                <artwork><![CDATA[
   <D:current-user-principal-resource xmlns:D="DAV:">
     <D:href>/principals/users/cdaboo</D:href>
   </D:current-user-principal-resource>
                ]]></artwork>
              </figure>
            </t>
          </list>
<?rfc compact="yes" ?>
      </t>
    </section>

      <section title="Security Considerations">
      <t>
        This specification does not introduce any additional security issues beyond those defined in HTTP <xref target="RFC2616"/>, WebDAV <xref target="RFC4918"/> and WebDAV ACL <xref target="RFC3744"/>.
      </t>
    </section>
    <section title="IANA Considerations">
      <t>
        This document does not require any actions on the part of IANA. 
      </t>
    </section>
    <section title="Acknowledgments">
      <t>
        This specification was suggested by discussion that took place within the Calendaring and Scheduling Consortium's CalDAV Technical Committee. The authors thank the participants of that group for their input.
      </t>
    </section>
  </middle>
  <back>
    <references title="Normative References">
      &rfc2119; 
      &rfc2616;
      &rfc3744;
      &rfc4918;
    </references>
<!--
    <references title="Informative References">
    </references>
 -->
<!--
<section title="Change History (to be removed prior to publication as an RFC)">

<t>Changes from -00:</t>
<list style="numbers">
<t></t>
</list>

</section>
-->
  </back>
</rfc>