draft-ietf-calsify-rfc2447bis-03.txt   draft-ietf-calsify-rfc2447bis-04.txt 
INTERNET-DRAFT A. Melnikov INTERNET-DRAFT A. Melnikov
Document: draft-ietf-calsify-rfc2447bis-03.txt Editor Document: draft-ietf-calsify-rfc2447bis-04.txt Editor
Intended status: Standard Track February 2007 Intended status: Standard Track May 12, 2008
Expires: August 2007 Expires: November 2008
iCalendar Message-Based Interoperability Protocol iCalendar Message-Based Interoperability Protocol
(iMIP) (iMIP)
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
A revised version of this draft document will be submitted to the RFC A revised version of this draft document will be submitted to the RFC
editor as a Draft Standard for the Internet Community. Discussion editor as a Draft Standard for the Internet Community. Discussion
and suggestions for improvement are requested, and should be sent to and suggestions for improvement are requested, and should be sent to
the CALSIFY Mailing list <ietf-calsify@osafoundation.org>. the CALSIFY Mailing list <ietf-calsify@osafoundation.org>.
Distribution of this document is unlimited. Distribution of this document is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document, iCalendar Message-Based Interoperability Protocol This document, iCalendar Message-Based Interoperability Protocol
(iMIP), specifies a binding from the iCalendar Transport-independent (iMIP), specifies a binding from the iCalendar Transport-independent
Interoperability Protocol (iTIP) to Internet email-based transports. Interoperability Protocol (iTIP) to Internet email-based transports.
Calendaring entries defined by the iCalendar Object Model (iCAL) are Calendaring entries defined by the iCalendar Object Model (iCAL) are
composed using constructs from RFC 2822, RFC 2045, RFC 2046, composed using constructs from RFC 2822, RFC 2045, RFC 2046,
RFC 2047 and RFC 2049. RFC 2047 and RFC 2049.
skipping to change at page 11, line 23 skipping to change at page 11, line 23
Content-Type: text/calendar; method=REQUEST; charset=US-ASCII Content-Type: text/calendar; method=REQUEST; charset=US-ASCII
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:mailto:foo1@example.com ORGANIZER:mailto:foo1@example.com
ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:mailto:foo1@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:mailto:foo1@example.com
ATTENDEE;RSVP=YES;TYPE=INDIVIDUAL:mailto:foo2@example.com ATTENDEE;RSVP=YES;CUTYPE=INDIVIDUAL:mailto:foo2@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970701T170000Z DTSTART:19970701T170000Z
DTEND:19970701T173000Z DTEND:19970701T173000Z
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:calsvr.example.com-8739701987387771 UID:calsvr.example.com-8739701987387771
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
skipping to change at page 12, line 14 skipping to change at page 12, line 14
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="event.vcs" Content-Disposition: attachment; filename="event.vcs"
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:mailto:foo1@example.com ORGANIZER:mailto:foo1@example.com
ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:mailto:foo1@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:mailto:foo1@example.com
ATTENDEE;RSVP=YES;TYPE=INDIVIDUAL:mailto:foo2@example.com ATTENDEE;RSVP=YES;CUTYPE=INDIVIDUAL:mailto:foo2@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970701T180000Z DTSTART:19970701T180000Z
DTEND:19970701T183000Z DTEND:19970701T183000Z
SUMMARY:Phone Conference SUMMARY:Phone Conference
UID:calsvr.example.com-8739701987387771 UID:calsvr.example.com-8739701987387771
ATTACH:cid:123456789@example.com ATTACH:cid:123456789@example.com
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
--boundary-example-1 --boundary-example-1
Content-Type: application/msword; name="FieldReport.doc" Content-Type: application/msword; name="FieldReport.doc"
Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="FieldReport.doc" Content-Disposition: inline; filename="FieldReport.doc"
Content-ID: <123456789@example.com> Content-ID: <123456789@example.com>
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAABAAAARAAAAAAA 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAABAAAARAAAAAAA
AAAAEAAAQAAAAAEAAAD+////AAAAAEUAAAD///////////////////////////////// AAAAEAAAQAAAAAEAAAD+////AAAAAEUAAAD/////////////////////////////////
... ...
--boundary-example-1-- --boundary-example-1--
4.4 Multiple Similar Components 4.4 Multiple Similar Components
skipping to change at page 14, line 11 skipping to change at page 14, line 11
Content-Type: text/calendar; method=REQUEST; charset=US-ASCII Content-Type: text/calendar; method=REQUEST; charset=US-ASCII
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="event1.vcs" Content-Disposition: attachment; filename="event1.vcs"
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
METHOD:REQUEST METHOD:REQUEST
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:mailto:foo1@example.com ORGANIZER:mailto:foo1@example.com
ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:mailto:foo1@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:mailto:foo1@example.com
ATTENDEE;RSVP=YES;TYPE=INDIVIDUAL:mailto:foo2@example.com ATTENDEE;RSVP=YES;CUTYPE=INDIVIDUAL:mailto:foo2@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970701T210000Z DTSTART:19970701T210000Z
DTEND:19970701T230000Z DTEND:19970701T230000Z
SUMMARY:Phone Conference SUMMARY:Phone Conference
DESCRIPTION:Discuss what happened at the last meeting DESCRIPTION:Discuss what happened at the last meeting
UID:calsvr.example.com-8739701987387772 UID:calsvr.example.com-8739701987387772
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
skipping to change at page 15, line 46 skipping to change at page 15, line 46
Content-Disposition: attachment; filename="event.vcs" Content-Disposition: attachment; filename="event.vcs"
BEGIN:VCALENDAR BEGIN:VCALENDAR
PRODID:-//ACME/DesktopCalendar//EN PRODID:-//ACME/DesktopCalendar//EN
PROFILE:REQUEST PROFILE:REQUEST
PROFILE-VERSION:1.0 PROFILE-VERSION:1.0
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
ORGANIZER:foo1@example.com ORGANIZER:foo1@example.com
ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:foo1@example.com ATTENDEE;ROLE=CHAIR;ATTSTAT=ACCEPTED:foo1@example.com
ATTENDEE;RSVP=YES;TYPE=INDIVIDUAL:mailto:foo2@example.com ATTENDEE;RSVP=YES;CUTYPE=INDIVIDUAL:mailto:foo2@example.com
ATTENDEE;RSVP=YES;TYPE=INDIVIDUAL:mailto:foo3@example.com ATTENDEE;RSVP=YES;CUTYPE=INDIVIDUAL:mailto:foo3@example.com
DTSTAMP:19970611T190000Z DTSTAMP:19970611T190000Z
DTSTART:19970621T170000Z DTSTART:19970621T170000Z
DTEND:199706211T173000Z DTEND:199706211T173000Z
SUMMARY:Let's discuss the attached document SUMMARY:Let's discuss the attached document
UID:calsvr.example.com-873970198738777-8aa UID:calsvr.example.com-873970198738777-8aa
ATTACH:cid:calsvr.example.com-12345aaa ATTACH:cid:calsvr.example.com-12345aaa
SEQUENCE:0 SEQUENCE:0
STATUS:CONFIRMED STATUS:CONFIRMED
END:VEVENT END:VEVENT
END:VCALENDAR END:VCALENDAR
----00FEE3790DC7E35189CA67CE2C00 ----00FEE3790DC7E35189CA67CE2C00
----FEE3790DC7E35189CA67CE2C ----FEE3790DC7E35189CA67CE2C
Content-Type: application/msword; name="FieldReport.doc" Content-Type: application/msword; name="FieldReport.doc"
Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="FieldReport.doc" Content-Disposition: inline; filename="FieldReport.doc"
Content-ID: <calsvr.example.com-12345aaa> Content-ID: <calsvr.example.com-12345aaa>
R0lGODdhTAQZAJEAAFVVVd3d3e4AAP///ywAAAAATAQZAAAC/5yPOSLhD6OctNqLs94Xq R0lGODdhTAQZAJEAAFVVVd3d3e4AAP///ywAAAAATAQZAAAC/5yPOSLhD6OctNqLs94Xq
AG4kiW5omm6sq27gvH8kzX9o1y+s73/g8MCofEovGITCoxKMbyCR16cNSq9YrNarfcrvd AG4kiW5omm6sq27gvH8kzX9o1y+s73/g8MCofEovGITCoxKMbyCR16cNSq9YrNarfcrvd
riIH5LL5jE6rxc3G+v2cguf0uv2Oz+v38L7/DxgoOKjURnjIIbe3yNjo+AgZWYVIWWl5i riIH5LL5jE6rxc3G+v2cguf0uv2Oz+v38L7/DxgoOKjURnjIIbe3yNjo+AgZWYVIWWl5i
ZnJY6J ZnJY6J
... ...
----FEE3790DC7E35189CA67CE2C ----FEE3790DC7E35189CA67CE2C
skipping to change at page 19, line 5 skipping to change at page 19, line 5
July 1994. July 1994.
[RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) - [RFC-2047] Moore, K., "Multipurpose Internet Mail Extensions (MIME) -
Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047, Part Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
November 1996. November 1996.
[RFC-2049] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC-2049] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC Extensions (MIME) Part Five: Conformance Criteria and Examples", RFC
2049, November 1996. 2049, November 1996.
8 Editor's Addresses 8 Authors' Addresses
The following address information is provided in a vCard v3.0, Alexey Melnikov (editor)
Electronic Business Card, format. Isode Ltd
5 Castle Business Village
36 Station Road
Hampton, Middlesex TW12 2BX
UK
BEGIN:VCARD Email: Alexey.Melnikov@isode.com
VERSION:3.0
N:Melnikov;Alexey
FN:Alexey Melnikov
ORG:Isode Ltd.
ADR;TYPE=WORK,POSTAL,PARCEL:;;5 Castle Business Village,
36 Station Road;Hampton;Middlesex;TW12 2BX;UK
EMAIL;TYPE=INTERNET:Alexey.Melnikov@isode.com
END:VCARD
9. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 20, line 47 skipping to change at page 20, line 47
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
Appendix A. Changes since RFC 2447. Appendix A. Changes since RFC 2447.
Updated references. Split them into Normative and Informative. Updated references. Split them into Normative and Informative.
Updated examples to use example.com/example.net domains. Updated examples to use example.com/example.net domains.
Corrected usage of RFC 2119 language. Corrected usage of RFC 2119 language.
Clarified that charset=UTF-8 is required, unless the calendar can be Clarified that charset=UTF-8 is required, unless the calendar can be
skipping to change at page 21, line 25 skipping to change at page 21, line 25
the calendar object is known to be transferred over 8-bit clean the calendar object is known to be transferred over 8-bit clean
transport. transport.
Clarified that file extension specified in the Content-Disposition Clarified that file extension specified in the Content-Disposition
header field is not to be used to override the Content-Type MIME header field is not to be used to override the Content-Type MIME
type. type.
Disallow use of "multiple/alternative" for slightly different Disallow use of "multiple/alternative" for slightly different
representations of the same calendar. representations of the same calendar.
Fixed examples with ATTENDEE property to use CUTYPE= instead of TYPE=
<<TBD>> <<TBD>>
 End of changes. 14 change blocks. 
26 lines changed or deleted 24 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/