DOCSLIB.ORG

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

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
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
Load more

Recommended publications
  • WS-Calendar Version 1.0
    1 2 WS-Calendar Version 1.0 3 Working Draft 04 4 20100509 5 Specification URIs: 6 This Version: 7 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-04.pdf 8 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-04.html 9 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-04.doc 10 Previous Version: 11 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-03.pdf 12 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-03.html 13 http://docs.oasis-open.org/ws-calendar/v1.0/wd04/ws-calendar-1.0-spec-wd-03.doc 14 Latest Version: 15 http://docs.oasis-open.org/ws-calendar/v1.0/ws-calendar-1.0-spec.pdf 16 http://docs.oasis-open.org/ws-calendar/v1.0/ws-calendar-1.0-spec.html 17 http://docs.oasis-open.org/ws-calendar/v1.0/ws-calendar-1.0-spec.doc 18 Technical Committee: 19 OASIS WS-Calendar TC 20 Chair(s): 21 Toby Considine 22 23 Editor(s): 24 Toby Considine 25 Paul Tischhauser 26 27 Related work: 28 This specification replaces or supersedes: 29 N/A 30 This specification is related to: 31 IETF RFC 5545, ICalendar 32 IETF RFC 5546, ICalendar Transport 33 IETF RFC 2447, ICalendar Message Based Interoperability 34 IETF XCal in process 35 36 Declared XML Namespace(s): 37 http://docs.oasis-open.org/ns/ws-calendar/ws-calendar-201001 38 Abstract: 39 WS-Calendar describes a common set of message components for specifying schedules and intervals to 40 coordinate activities between services.
    [Show full text]
  • Scheduling Standards Resources
    Memorandum To: Oasis-Open LegalXML ECF TC From: James McMillan, National Center for State Courts Re: Scheduling standards resources Per request from the TC, I have prepared the following resource list from our discussion with the experts from the CalConnect, The Calendaring and Scheduling Consortium: http://www.calconnect.org/ Pertinent to our efforts is that this group is participating in the OASIS-Open Web Services Calendar group (WS-Calendar) TC https://www.oasis-open.org/apps/org/workgroup/ws-calendar/ And one of the ideas that the expert group suggested is that ECF send a representative to the upcoming CalConnect XXXII conference scheduled for San Jose, CA, January 26-30, 2015 (http://www.calconnect.org/calconnect32.shtml ). Also please note that as part of the conference they hold their their CalConnect Interoperability Test Event: http://www.calconnect.org/iop1501.shtml Standards The following are a list of scheduling and calendar related standards that the experts recommended that ECF study and consider for guidance for our possible scheduling extension. iCalendar (http://en.wikipedia.org/wiki/ICalendar ) is a computer file format which allows Internet users to send meeting requests and tasks to other Internet users, via email, or sharing files with an extension of .ics. Recipients of the iCalendar data file (with supporting software, such as an email client or calendar application) can respond to the sender easily or counter- propose another meeting date/time. There is an excellent properties chart shown here for the standard: http://en.wikipedia.org/wiki/ICalendar#mediaviewer/File:ICalendarSpecification.png iTip Standard (https://www.ietf.org/rfc/rfc2446.txt )- defines a protocol for exchanging iCalendar objects for the purposes of group calendaring and scheduling between "Calendar Users" (CUs); whoever initiates the exchange of data takes on the role of the "Organizer".
    [Show full text]
  • Reference Guide
    Reference Guide Mulberry Internet Email and Calendar Client Version 4.0 Cyrus Daboo mailto:[email protected] Pittsburgh PA http://www.mulberrymail.com USA 2Information in this document is subject to change without notice. You are free to use this document in any way you wish provided full attribution of the original author is given. Document Revision 405.000 © 2006 Cyrus Daboo. All Rights Reserved. Pittsburgh PA USA Mulberry is a registered trademark. All other companies and product names are trademarks or registered trademarks of their respective holders. Contents 1. INTRODUCTION................................................................................. 15 2. GETTING STARTED............................................................................ 16 2.1 SYSTEM REQUIREMENTS .......................................................................................................... 16 2.2 INSTALLING MULBERRY........................................................................................................... 17 2.3 GETTING HELP......................................................................................................................... 18 2.4 STARTING MULBERRY .............................................................................................................. 18 2.5 DRAG AND DROP ...................................................................................................................... 20 2.6 CONTEXTUAL MENUS.............................................................................................................
    [Show full text]
  • How to Subscribe to the VCS Online Calendar
    How to subscribe to VCS calendars 1. Select the calendar you would like to subscribe to. 2. Click subscribe link. 3. Clicking the link opens the subscribe page where you are presented with a list of subscription options and a subscribe button. Select how you want to subscribe to automatically receive calendar updates. Each selected option is described briefly. By clicking More, you will have access to a more detailed description as well as help about how to subscribe. 4. Select an option, and then click Subscribe. Subscription options explained We invite you to learn about each of the ways visitors can subscribe. iCalendar feeds and files In the subscribe window, you are given two iCalendar options. You can subscribe to an iCalendar feed or download an iCalendar file. iCalendar subscribe (recommended) When you subscribe to an iCalendar feed, you should see a URL or link in your Internet browser. In most cases, the browser will automatically send the iCalendar feed to your calendar program. If the calendar program supports the iCalendar format, it will download the event information into a new or existing calendar and establish a connection with the online calendar so new events will automatically be added. For more details about iCalendar subscriptions with specific calendars or devices, see Subscribe to iCalendar feed. iCalendar download While you will be able to download an iCalendar (.ics) file, it would not be automatically updated so we encourage you to use the iCalendar subscription option. RSS and Atom feeds You can subscribe to feeds of VCS events in either RSS or Atom (XML) format.
    [Show full text]
  • Caldav on a Mobile Device
    Master Thesis CalDAV on a Mobile Device Martin Hellaeus April 4, 2007 Department of Computer Science Lund Institute of Technology Supervisor: Lennart Ohlsson Abstract There are today many solutions for exchanging calendar information. How- ever, there is no open standard for this yet. This has resulted in many different solutions that are not able to fully communicate and exchange cal- endar data. A proposal to solve this is CalDAV that is intended to be a standard protocol for transport of calendar data over HTTP. This thesis presents the calendaring situation of today and, if and what CalDAV can improve. Another topic that is dealt with is if CalDAV is suited also for mobile devices. During the work an application has been developed. It is a calendar client that uses the CalDAV protocol to connect to servers and fetch calendar data from it. The application is intended for use in a mobile device. Contents 1 Introduction 3 1.1 Previous work . 4 1.2 Objectives . 5 1.3 Approach . 7 1.4 Note . 8 2 Calendaring solutions 9 2.1 Mobile solutions . 11 3 CalDAV 12 3.1 WebDAV . 15 3.2 iCalendar . 17 3.3 The CalDAV Protocol . 17 3.3.1 Authentication . 21 3.3.2 Scheduling Extensions to CalDAV . 22 4 Interoperability 24 4.1 Clients . 25 4.2 Servers . 27 5 Design of a Demo client 30 5.1 Environment . 30 5.2 Requirements . 31 5.3 Design . 31 5.4 Result . 33 6 Summary 36 A Requirements 41 1 B Protocol examples 43 B.1 CalDAV request example .
    [Show full text]
  • North Carolina Statewide Technical Architecture Collaboration Domain
    North Carolina Statewide Technical Architecture Collaboration Domain © 2005 State of North Carolina Office of the State Chief Information Officer Enterprise Technology Strategies PO Box 17209 Raleigh, North Carolina 27699-7209 http://www.ncsta.gov [email protected] All rights reserved. No part of the material protected by this copyright notice may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording or by any informational storage system without written permission from the copyright owner. North Carolina Statewide Technical Architecture Collaboration Domain Table of Contents 1. PRINCIPLES:..................................................................................................................................... 4 1.1. EFFECTIVE USES OF COLLABORATION TECHNOLOGIES CONNECT PEOPLE, PROCESSES, AND INFORMATION TO MEET BUSINESS REQUIREMENTS. .................................................................................... 4 1.2. COLLABORATION TECHNOLOGIES LINK PEOPLE, PROCESSES, AND INFORMATION WITHIN AND ACROSS ORGANIZATION BOUNDARIES AND ARE MOST EFFECTIVE WHEN IMPLEMENTED USING AN ENTERPRISE APPROACH TEXT ..................................................................................................................... 4 1.3. COLLABORATIVE TECHNOLOGIES ARE SUPPORTED AND COMPLEMENTED BY ENTERPRISE-CLASS SERVICES. ................................................................................................................................................... 4 1.4. COLLABORATIVE
    [Show full text]
  • Notes/Domino 10.X へのアップグレード
    Notes/Domino 10.x へのアップグレード 2019 年 4 月 15 日 初版 2020 年 2 月 5 日 軽微な修正 フィードバックは [email protected] または [email protected] にお寄せくだ さい(英語)。 日本語版注: 一部日本語コンテンツへのリンクの差し替え、追加、その他日本語版独自の注意事項 を掲載していますが、英語のコンテンツへのリンクが多数含まれます。予めご了承ください。 目次 第 1 章: Notes および Domino 10 の紹介 ................................................. 1-1 管理者のための新機能 ................................................................. 1-1 ユーザーのための新機能 ............................................................... 1-2 開発者のための新機能 ................................................................. 1-4 Domino AppDev Pack ................................................................. 1-4 新しい LotusScript および Java クラス .............................................. 1-4 削除された機能 ....................................................................... 1-5 第 2 章: Domino 10 サーバーのデプロイメントの計画 ...................................... 2-6 既存環境の評価とモニター ............................................................. 2-6 評価 ............................................................................... 2-6 モニター ........................................................................... 2-6 リリース 10 の OS とハードウェア要件の評価 ........................................... 2-7 システム要件 ....................................................................... 2-7 32 ビットの OS から 64 ビット OS への移行の場合 ..................................... 2-7 バージョン間の機能の共存の評価 ....................................................... 2-7 Notes Auto Update .................................................................. 2-7 新しい ODS レベル: ODS
    [Show full text]
  • Calendering Extensions C. Daboo Internet-Draft Apple Intended Status: Informational A
    Calendering Extensions C. Daboo Internet-Draft Apple Intended status: Informational A. Quillaud Expires: January 24, 2018 Oracle K. Murchison, Ed. FastMail July 23, 2017 CalDAV Managed Attachments draft-ietf-calext-caldav-attachments-03 Abstract This specification defines an extension to the calendar access protocol (CalDAV) to allow attachments associated with iCalendar data to be stored and managed on the server. This specification documents existing code deployed by multiple vendors. It is published as an Informational specification rather than Standards-Track due to its non-standard method of updating an existing resource via HTTP. 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 January 24, 2018. Copyright Notice Copyright (c) 2017 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 Daboo, et al. Expires January 24, 2018 [Page 1] Internet-Draft CalDAV Managed Attachments July 2017 publication of this document.
    [Show full text]
  • Feeding the Bird a Quick Start Into Calendar Development
    Welcome, Bienvenue, Welkom … ® Feeding the Bird A quick start into calendar development Duration: 30 Minutes by Philipp Kewisch mozilla @ kewis.ch ® Provider Basics Functionality › What does a Provider do? › Show and manipulate events from a custom source › Provide access to calendar servers › Changes to items are “live” mozilla @ kewis.ch ® Provider Basics Examples › Existing providers › Internal storage (sqlite) › iCalendar / ICS › CalDAV › Sun Java Calendar Server (WCAP) › Provider for Google Calendar › ThunderBirthDay › Ideas for new providers ® › Microsoft Exchange Server › Lotus Notes / Domino › Zimbra Collaboration Suite › X10 / Home control mozilla @ kewis.ch ® Provider Basics Advanced Capabilities › Advanced Features › Freebusy querying › Searching for calendars / Subscriptions › Invitation handling (iMIP/iTIP) › Advanced synchronization (caching) › Controlling the UI › Disable unsupported features (i.e tasks) › Specify possible values (i.e privacy) mozilla @ kewis.ch ® Implementing a Provider The real work... › Implement calICalendar › Most methods and attributes can be inherited from calProviderBase › type attribute (Short name for the provider) › getItems (Retrive Items) › getItem (Retrieve a specific Item) › add, delete, modifyItem (Write Items) › canRefresh, refresh (Action when calendar is reloaded) mozilla @ kewis.ch ® Implementing a Provider Adding UI To allow calendar creation using the calendar wizard, calendarCreation.xul needs to be overlaid. <!DOCTYPE overlay SYSTEM "chrome://gdata-provider/locale/gdata.dtd"> <overlay
    [Show full text]
  • [MS-OXREF]: Exchange Server Protocols Master Reference
    [MS-OXREF]: Exchange Server Protocols Master Reference Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights.
    [Show full text]
  • Calws-SOAP SOAP Web Services Protocol for Calendaring Version: 1.0 Date: 2013-01-10 Status: Published Source: TC XML
    CALCONNECT DOCUMENT CD1301 Type: Proposal Title: CalWS-SOAP SOAP Web Services Protocol for Calendaring Version: 1.0 Date: 2013-01-10 Status: Published Source: TC XML This document was subject to public review at the same time as the OASIS WS- Calendar publication of CalWS-SOAP and contains the same content.. This document is copyright ©2013 by The Calendaring and Scheduling Consortium and is licensed under the Creative Commons 3.0 Unported LIcense: http://creativecommons.org/licenses/by/3.0/. CalWS-SOAP Version 1.0 09 November 2012 Technical Committee: CalConnect TC-XML Chair: Michael Douglass ([email protected]), Rensselaer Polytechnic Institute Editor: Michael Douglass ([email protected]), Rensselaer Polytechnic Institute Related work: This specification is related to: • RFC 6321 – xCal: iCalendar in XML. http://www.ietf.org/rfc/rfc6321.txt • WS-Calendar Version 1.0. Latest version. http://docs.oasis-open.org/ws-calendar/ws-calendar/v1.0/ws-calendar-1.0-spec.html Abstract: This document describes standard messages and interactions for service interactions with a system that hosts calendar-based information using SOAP. Hosted information can be either traditional personal and enterprise calendar information or services that support XML payloads developed in conformance with the WS-Calendar specification. CalWS-SOAP Version 1.0 09 November 2012 Copyright (c) 2012 The Calendaring and Scheduling Consortium. All Rights Reserved. Page 1 of 43 Table of Contents 1 Introduction.........................................................................................................................................
    [Show full text]
  • [MS-STANOICAL]: Outlook Icalendar Standards Support
    [MS-STANOICAL]: Outlook iCalendar Standards Support Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights.
    [Show full text]