idnits 2.17.1 draft-ietf-calsch-inetcal-guide-02.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 3283 5 Title: Guide to Internet Calendaring 6 Author(s): B. Mahoney, G. Babics, A. Taler 7 Status: Informational 8 Date: June 2002 9 Mailbox: bobmah@mit.edu, georgeb@steltor.com, 10 alex@0--0.org 11 Pages: 16 12 Characters: 31768 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-calsch-inetcal-guide-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3283.txt 19 This document describes the various Internet calendaring and 20 scheduling standards and works in progress, and the relationships 21 between them. Its intent is to provide a context for these 22 documents, assist in their understanding, and potentially aid in the 23 design of standards-based calendaring and scheduling systems. The 24 standards addressed are RFC 2445 (iCalendar), RFC 2446 (iTIP), and 25 RFC 2447 (iMIP). The work in progress addressed is "Calendar Access 26 Protocol" (CAP). This document also describes issues and problems 27 that are not solved by these protocols, and that could be targets for 28 future work. 30 This document is a product of the Calendaring and Scheduling Working 31 Group of the IETF. 33 This memo provides information for the Internet community. It does 34 not specify an Internet standard of any kind. Distribution of this 35 memo is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.