RFC 5995 on Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections

rfc-editor@rfc-editor.org Tue, 07 September 2010 16:24 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 778413A67D0 for <ietf-announce@core3.amsl.com>; Tue, 7 Sep 2010 09:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.037
X-Spam-Status: No, score=-102.037 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ydU6t9JKtAoF for <ietf-announce@core3.amsl.com>; Tue, 7 Sep 2010 09:24:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CA90B3A6AA0 for <ietf-announce@ietf.org>; Tue, 7 Sep 2010 09:24:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 67948E06EA; Tue, 7 Sep 2010 09:24:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5995 on Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections
From: rfc-editor@rfc-editor.org
Message-Id: <20100907162437.67948E06EA@rfc-editor.org>
Date: Tue, 7 Sep 2010 09:24:37 -0700 (PDT)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Sep 2010 16:24:23 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 5995

        Title:      Using POST to Add Members 
                    to Web Distributed Authoring and Versioning 
                    (WebDAV) Collections 
        Author:     J. Reschke
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2010
        Mailbox:    julian.reschke@greenbytes.de
        Pages:      12
        Characters: 21591
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-reschke-webdav-post-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5995.txt

The Hypertext Transfer Protocol (HTTP) Extensions for the Web
Distributed Authoring and Versioning (WebDAV) do not define the
behavior for the "POST" method when applied to collections, as the
base specification (HTTP) leaves implementers lots of freedom for the
semantics of "POST".

This has led to a situation where many WebDAV servers do not
implement POST for collections at all, although it is well suited to
be used for the purpose of adding new members to a collection, where
the server remains in control of the newly assigned URL.  In fact,
the Atom Publishing Protocol (AtomPub) uses POST exactly for that
purpose.  On the other hand, WebDAV-based protocols, such as the
Calendaring Extensions to WebDAV (CalDAV), frequently require clients
to pick a unique URL, although the server could easily perform that

This specification defines a discovery mechanism through which
servers can advertise support for POST requests with the
aforementioned "add collection member" semantics.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC