Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)
RFC 8144

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, julian.reschke@gmx.de, " julian.reschke@gmx.de" <julian.reschke@gmx.de>, draft-murchison-webdav-prefer@ietf.org, alexey.melnikov@isode.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)' to Proposed Standard (draft-murchison-webdav-prefer-14.txt)

The IESG has approved the following document:
- 'Use of the Prefer Header Field in Web Distributed Authoring and
   Versioning (WebDAV)'
  (draft-murchison-webdav-prefer-14.txt) as Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Alexey Melnikov.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-murchison-webdav-prefer/


Technical Summary

This document defines an update to the HTTP Prefer header field to specify how it can be used by a WebDAV client to request that certain behaviors be employed by a server while constructing a response to a request. Furthermore, it defines the new "depth-noroot" preference.

Working Group Summary

This document was briefly discussed in the HTTPbis WG and AFAIK the CALEXT WG. For HTTPbis, it was felt to be too specific to WebDAV. For CALEXT, it's not really suited because it applies to many non-calendaring use cases (all authoring over HTTP/WebDAV, essentially).

Document Quality

Are there existing implementations of the protocol?

Yes, as described in the document.

Have a significant number of vendors indicated their plan to implement the specification?

See above.

If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted?

I personally reviewed the document from an HTTP, WebDAV and XML angle. IANA reviews were requested on the HTTPBIS WG mailing list.

Personnel Who is the Document Shepherd? Who is the Responsible Area Director?

Julian Reschke. Alexey Melnikov.