RFC 2446 on iTIP

RFC Editor <rfc-ed@ISI.EDU> Mon, 16 November 1998 20:45 UTC

Message-Id: <199811162029.MAA05602@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2446 on iTIP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 16 Nov 1998 12:29:30 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2446:

        Title:	    iCalendar Transport-Independent Interoperability
		    Protocol (iTIP) Scheduling Events, BusyTime, 
		    To-dos and Journal Entries
	Author(s):  S. Silverberg, S. Mansour, F. Dawson, R. Hopson
	Status:     Proposed Standard
	Date:       November 1998
        Mailbox:    stevesil@Microsoft.com, sman@netscape.com,
		    Frank_Dawson@Lotus.com, rhopson@on.com
	Pages:      109
        Characters: 225964
        Updates/Obsoletes/See Also: None
        I-D Tag:    draft-ietf-calsch-itip-07.txt


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


This document specifies how calendaring systems use iCalendar objects
to interoperate with other calendar systems. It does so in a general
way so as to allow multiple methods of communication between systems.
Subsequent documents specify interoperable methods of communications
between systems that use this protocol.

This document is a product of the Calendaring and Scheduling 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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.

ftp://ftp.isi.edu/in-notes/rfc2446.txt"><ftp://ftp.isi.edu/in-notes/rfc2446.txt>

RFC 2446 on iTIP RFC Editor