CalDAV Extension for scheduling controls
draft-ietf-calext-caldav-scheduling-controls-00

Document Type Active Internet-Draft (calext WG)
Last updated 2019-03-26
Replaces draft-calext-caldav-scheduling-controls
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
calext                                                  B. Gondwana, Ed.
Internet-Draft                                                  FastMail
Updates: 6638 (if approved)                               March 26, 2019
Intended status: Standards Track
Expires: September 27, 2019

                CalDAV Extension for scheduling controls
            draft-ietf-calext-caldav-scheduling-controls-00

Abstract

   This document adds headers to control and restrict the scheduling
   behaviour of CalDAV servers when updating calendaring resources.

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 https://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 September 27, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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
   described in the Simplified BSD License.

Gondwana               Expires September 27, 2019               [Page 1]
Internet-Draft             CalDAV SchedControl                March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used In This Document . . . . . . . . . . . . . .   3
   3.  Extending the CalDAV OPTIONS response . . . . . . . . . . . .   3
     3.1.  Example: Using OPTIONS for the Discovery of Scheduling
           Controls Support  . . . . . . . . . . . . . . . . . . . .   3
   4.  New headers . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Scheduling header . . . . . . . . . . . . . . . . . . . .   4
     4.2.  Schedule-User-Address header  . . . . . . . . . . . . . .   4
   5.  Implementation considerations . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Version History . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  ietf-calext-v00, 2019-03-26 . . . . . . . . . . . . . . .   5
     9.2.  gondwana-v01, 2019-03-08  . . . . . . . . . . . . . . . .   6
     9.3.  gondwana-v00, 2019-02-08  . . . . . . . . . . . . . . . .   6
   10. Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   [RFC6638] defines automatic scheduling operations for resources
   stored on [!@RFC4791] CalDAV servers.

   [RFC6638] defines the "Schedule-Reply" header in Section 8.1, however
   this header is not sufficient for controlling scheduling in all
   cases.

   Cases where it might be necessary to update the data store on a
   server without causing scheduling messages to be sent include backup
   after a data loss event on the server, or importing calendar events
   from another system.

   Calendar server operators deal with these other needs by either using
   a different method than CalDAV to update their server, or by adding a
   custom method to suppress scheduling.  This document defines a
   standard method to suppress scheduling, allowing CalDAV to be
   directly used for restores and imports.

   Complex sites can have users who have multiple aliases, and in the
   most complex cases, a user may have multiple identities who are
   present on a scheduling event as organizer and/or attendee.  When an
   event is updated over CalDAV, the server must calculate or guess
   which of those addresses the current user is acting as.  This
   document defines a header which allows the client to inform the

Gondwana               Expires September 27, 2019               [Page 2]
Internet-Draft             CalDAV SchedControl                March 2019

   server precisely which address they are acting as when adding,
   modifying or removing a resource.

2.  Conventions Used In This Document

   In examples, "C:" indicates data sent by a client that is connected
Show full document text