RFC 2445:Internet Calendaring and Scheduling Core ...
RFC-Ref

transport


Click on the red underlined text to get to the source

... applications or systems. The format is defined in terms of a MIME content type. This will enable the object to be exchanged using several transports, including but not limited to SMTP, HTTP, a file system ...
... asynchronous communication, wired-network transport, or some form of unwired transport such as infrared might also be used. ...
... network transport, or some form of unwired transport such as infrared might also be used. ...
... other calendaring and scheduling operations such a requesting for and replying with free/busy time data. Such a scheduling protocol is defined in the iCalendar Transport-independent Interoperability Protocol (iTIP) defined in [ITIP ...


... use as a calendaring and scheduling exchange format in file-, memory- or network-based transport mechanisms. ...
... charset" Content-Type parameter can be used in MIME transports to specify any other IANA registered character set ...
... RFC1766]. For transport in a MIME entity, the Content-Language ...
... URI. When used to address an Internet email transport address for a calendar user, the value MUST be a MAILTO ...
... methods are defined by this specification. This is the subject of other specifications, such as the iCalendar Transport-independent Interoperability Protocol (iTIP) defined by [ITIP ...
... transaction MUST NOT be assumed. In such cases, the iCalendar object is merely being used to transport a snapshot of some calendar information; without the intention of conveying a scheduling ...


... Silverberg, S., Mansour, S., Dawson, F. and R. Hopson, "iCalendar Transport-Independent Interoperability Protocol (iTIP) : Scheduling Events, Busy Time, To-dos ...



Google
Web
RFC-Ref