Internet Calendar Scheduling Protocol (Ischedule) Draft-Desruisseaux-Ischedule-01

Internet Calendar Scheduling Protocol (Ischedule) Draft-Desruisseaux-Ischedule-01

Network Working Group C. Daboo Internet Draft Apple <draft-desruisseaux-ischedule-01> B. Desruisseaux Updates: 4871 (if approved) Oracle Intended status: Standards Track March 8, 2010 Expires: September 9, 2010 Internet Calendar Scheduling Protocol (iSchedule) draft-desruisseaux-ischedule-01 Abstract This document defines the Internet Calendar Scheduling Protocol (iSchedule), which is a binding from the iCalendar Transport-independent Interoperability Protocol (iTIP) to the Hypertext Transfer Protocol (HTTP) to enable interoperability between calendaring and scheduling systems over the Internet. Status of This Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”. The list of current Internet-Drafts can be accessed at <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of Internet-Draft Shadow Directories can be accessed at <http://www.ietf.org/shadow.html>. This Internet-Draft will expire in September 9, 2010. Copyright Notice Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info1) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License. 1 http://trustee.ietf.org/license-info INTERNET DRAFT iSchedule March 2010 Table of Contents 1 Introduction...............................................................................................................................................................5 1.1 Motivations............................................................................................................................................................ 5 1.2 Related Memos...................................................................................................................................................... 5 1.3 Notational Conventions......................................................................................................................................... 6 2 iSchedule Model........................................................................................................................................................7 3 iSchedule Intermediaries..........................................................................................................................................8 4 iSchedule Receiver Discovery..................................................................................................................................9 4.1 iSchedule SRV Service Types.............................................................................................................................. 9 4.2 iSchedule Receiver Request-URI..........................................................................................................................9 4.3 Resolving Calendar User Addresses..................................................................................................................... 9 4.4 Using the SRV Record Result............................................................................................................................ 10 5 iSchedule Receiver Capabilities............................................................................................................................ 11 5.1 Example: Querying iSchedule Receiver Capabilities......................................................................................... 11 6 Scheduling................................................................................................................................................................13 6.1 POST Method...................................................................................................................................................... 13 6.1.1 Schedule Response......................................................................................................................................... 13 6.1.2 Status Codes for use with the POST method................................................................................................ 14 7 iSchedule Domain-Level Authentication..............................................................................................................15 7.1 Signature Content................................................................................................................................................ 15 7.2 Canonicalization...................................................................................................................................................15 7.2.1 The "simple-http" Header Canonicalization Algorithm.................................................................................15 7.2.2 The "simple-http" Body Canonicalization Algorithm....................................................................................15 7.3 Key Management.................................................................................................................................................15 7.4 Delegation of Signing Authority.........................................................................................................................16 7.4.1 Publication of Procuration Record................................................................................................................. 16 7.4.2 Procuration Lookup Procedure.......................................................................................................................16 8 HTTP Headers........................................................................................................................................................ 17 8.1 DKIM-Signature Request Header....................................................................................................................... 17 8.2 iSchedule-Version General Header..................................................................................................................... 17 8.3 iSchedule-Via General Header............................................................................................................................17 8.4 Originator Request Header..................................................................................................................................17 8.5 Recipient Request Header................................................................................................................................... 18 9 XML Element Definitions......................................................................................................................................19 9.1 schedule-response XML Element........................................................................................................................19 9.1.1 response XML Element..................................................................................................................................19 9.1.1.1 recipient XML Element...............................................................................................................................19 9.1.1.2 request-status XML Element.......................................................................................................................19 Daboo & Desruisseaux Standards Track [Page 2] INTERNET DRAFT iSchedule March 2010 9.1.1.3 calendar-data XML Element....................................................................................................................... 20 9.1.1.4 error XML Element.....................................................................................................................................20 9.1.1.5 responsedescription XML Element............................................................................................................. 20 9.2 query-result XML Element................................................................................................................................. 20 9.2.1 capability-set XML Element.......................................................................................................................... 20 9.2.1.1 supported-version-set XML Element.......................................................................................................... 21 9.2.1.2 supported-scheduling-message-set XML Element......................................................................................21 9.2.1.3 supported-calendar-data-type XML Element.............................................................................................. 22 9.2.1.4 supported-attachment-values XML Element...............................................................................................23 9.2.1.5 supported-recipient-uri-scheme-set

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    38 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us