iCalendar Transport-Independent Interoperability Protocol (iTIP
暂无分享,去创建一个
This document specifies a protocol that uses the iCalendar object
specification to provide scheduling interoperability between different
calendaring systems. This is done without reference to a specific
transport protocol so as to allow multiple methods of communication
between systems. Subsequent documents will define profiles of this
protocol that use specific, interoperable methods of communication
between systems. The iCalendar Transport-Independent Interoperability
Protocol (iTIP) complements the iCalendar object specification by
adding semantics for group scheduling methods commonly available in
current calendaring systems. These scheduling methods permit two or
more calendaring systems to perform transactions such as publishing,
scheduling, rescheduling, responding to scheduling requests,
negotiating changes, or canceling. [STANDARDS-TRACK]
[1] Scott O. Bradner,et al. Key words for use in RFCs to Indicate Requirement Levels , 1997, RFC.
[2] Peter W. Resnick,et al. Internet Message Format , 2001, RFC.
[3] Bernard Desruisseaux,et al. Internet Calendaring and Scheduling Core Object Specification (iCalendar) , 2009, RFC.
[4] Frank Dawson,et al. iCalendar Message-Based Interoperability Protocol (iMIP) , 1998, RFC.
[5] Sandy Murphy,et al. Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted , 1995, RFC.