W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1999

FW: RFC 2518 on WEBDAV

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Fri, 12 Feb 1999 13:06:09 -0800
To: WEBDAV WG <w3c-dist-auth@w3.org>
Cc: dav-announce@lyra.org
Message-ID: <006701be56cb$8342de60$d115c380@galileo.ics.uci.edu>
RFC 2518 has officially been released!

- Jim

-----Original Message-----
From: RFC Editor [mailto:rfc-ed@isi.edu] 
Sent: Wednesday, February 10, 1999 4:15 PM
To: IETF-Announce: ;
Cc: rfc-ed@isi.edu
Subject: RFC 2518 on WEBDAV

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

        RFC 2518: 

        Title:	    HTTP Extensions for Distributed Authoring --
	Author(s):  Y. Goland, E. Whitehead, A. Faizi, S. Carter,
		    D. Jensen
	Status:     Proposed Standard
	Date:       February 1999
        Mailbox:    yarong@microsoft.com, ejw@ics.uci.edu,
		    asad@netscape.com, srcarter@novell.com,
	Pages:      94
        Characters: 202829
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-ietf-webdav-protocol-10.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2518.txt

This document specifies a set of methods, headers, and content-types
ancillary to HTTP/1.1 for the management of resource properties,
creation and management of resource collections, namespace
manipulation, and resource locking (collision avoidance).

This document is a product of the WWW Distributed Authoring and
Versioning Working Group of the	IETF.	

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
Received on Friday, 12 February 1999 16:09:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:16 UTC