Internet Calendar Scheduling Protocol (iSchedule)
draft-desruisseaux-ischedule-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in app area)
Last updated 2013-01-22
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd None
IESG IESG state I-D Exists (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Peter Saint-Andre
Send notices to cyrus@daboo.name, bernard.desruisseaux@oracle.com, draft-desruisseaux-ischedule@tools.ietf.org, stpeter@stpeter.im
Network Working Group                                           C. Daboo
Internet-Draft                                                     Apple
Updates: 6376 (if approved)                              B. Desruisseaux
Intended status: Standards Track                                  Oracle
Expires: July 26, 2013                                  January 22, 2013

           Internet Calendar Scheduling Protocol (iSchedule)
                    draft-desruisseaux-ischedule-03

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 in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on July 26, 2013.

Copyright Notice

   Copyright (c) 2013 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-info) 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

Daboo & Desruisseaux      Expires July 26, 2013                 [Page 1]
Internet-Draft                  iSchedule                   January 2013

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Motivations  . . . . . . . . . . . . . . . . . . . . . . .  5
     1.2.  Related Memos  . . . . . . . . . . . . . . . . . . . . . .  6
     1.3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  6
     1.4.  Notational Conventions . . . . . . . . . . . . . . . . . .  7
   2.  iSchedule Model  . . . . . . . . . . . . . . . . . . . . . . .  7
   3.  iSchedule Overview . . . . . . . . . . . . . . . . . . . . . .  8
     3.1.  iSchedule Sender Actions . . . . . . . . . . . . . . . . .  8
     3.2.  iSchedule Receiver Actions . . . . . . . . . . . . . . . .  9
   4.  iSchedule Receiver Discovery . . . . . . . . . . . . . . . . . 10
     4.1.  Resolving Calendar User Addresses  . . . . . . . . . . . . 10
     4.2.  iSchedule SRV Service Types  . . . . . . . . . . . . . . . 11
     4.3.  iSchedule Service TXT Records  . . . . . . . . . . . . . . 12
     4.4.  iSchedule Receiver Request-URI . . . . . . . . . . . . . . 12
   5.  iSchedule Receiver Capabilities  . . . . . . . . . . . . . . . 12
     5.1.  Example: Querying iSchedule Receiver Capabilities  . . . . 13
   6.  Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     6.1.  POST Method  . . . . . . . . . . . . . . . . . . . . . . . 15
       6.1.1.  Schedule Response  . . . . . . . . . . . . . . . . . . 17
       6.1.2.  Failed Schedule Response . . . . . . . . . . . . . . . 17
   7.  iSchedule Domain-Level Authentication  . . . . . . . . . . . . 19
     7.1.  Signature Content  . . . . . . . . . . . . . . . . . . . . 20
     7.2.  Canonicalization . . . . . . . . . . . . . . . . . . . . . 21
       7.2.1.  The "ischedule-relaxed"  Header Canonicalization
               Algorithm  . . . . . . . . . . . . . . . . . . . . . . 22
     7.3.  Key Management . . . . . . . . . . . . . . . . . . . . . . 23
       7.3.1.  DNS-based Public Key Management  . . . . . . . . . . . 23
       7.3.2.  HTTP-based Public Key Management . . . . . . . . . . . 23
         7.3.2.1.  SRV Service Type . . . . . . . . . . . . . . . . . 23
         7.3.2.2.  Well-known Request-URI . . . . . . . . . . . . . . 24
         7.3.2.3.  Example Lookup Procedure . . . . . . . . . . . . . 24
       7.3.3.  Private Exchange Public Key Management . . . . . . . . 25
     7.4.  Verification Requirements  . . . . . . . . . . . . . . . . 25
     7.5.  Authorized Third-Party Signatures  . . . . . . . . . . . . 26
   8.  HTTP Headers . . . . . . . . . . . . . . . . . . . . . . . . . 26
     8.1.  DKIM-Signature Request Header  . . . . . . . . . . . . . . 26
Show full document text