idnits 2.17.1 draft-ietf-deltav-versioning-20.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3253 5 Title: Versioning Extensions to WebDAV 6 (Web Distributed Authoring and Versioning) 7 Author(s): G. Clemm, J. Amsden, T. Ellison, C. Kaler, 8 J. Whitehead 9 Status: Standards Track 10 Date: March 2002 11 Mailbox: geoffrey.clemm@rational.com, jamsden@us.ibm.com, 12 tim_ellison@uk.ibm.com, ckaler@microsoft.com, 13 ejw@cse.ucsc.edu 14 Pages: 118 15 Characters: 245514 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-deltav-versioning-20.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3253.txt 22 This document specifies a set of methods, headers, and resource types 23 that define the WebDAV (Web Distributed Authoring and Versioning) 24 versioning extensions to the HTTP/1.1 protocol. WebDAV versioning 25 will minimize the complexity of clients that are capable of 26 interoperating with a variety of versioning repository managers, to 27 facilitate widespread deployment of applications capable of utilizing 28 the WebDAV Versioning services. WebDAV versioning includes automatic 29 versioning for versioning-unaware clients, version history management, 30 workspace management, baseline management, activity management, and 31 URL namespace versioning. 33 This document is a product of the Web Versioning and Configuration 34 Management Working Group of the IETF. 36 This is now a Proposed Standard Protocol. 38 This document specifies an Internet standards track protocol for 39 the Internet community, and requests discussion and suggestions 40 for improvements. Please refer to the current edition of the 41 "Internet Official Protocol Standards" (STD 1) for the 42 standardization state and status of this protocol. Distribution 43 of this memo is unlimited. 45 This announcement is sent to the IETF list and the RFC-DIST list. 46 Requests to be added to or deleted from the IETF distribution list 47 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 48 added to or deleted from the RFC-DIST distribution list should 49 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 51 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 52 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 53 help: ways_to_get_rfcs. For example: 55 To: rfc-info@RFC-EDITOR.ORG 56 Subject: getting rfcs 58 help: ways_to_get_rfcs 60 Requests for special distribution should be addressed to either the 61 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 62 specifically noted otherwise on the RFC itself, all RFCs are for 63 unlimited distribution.echo 64 Submissions for Requests for Comments should be sent to 65 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 66 Authors, for further information.