VALARM Extensions for iCalendar
draft-ietf-calext-valarm-extensions-01

Document Type Active Internet-Draft (calext WG)
Last updated 2020-04-22 (latest revision 2020-01-17)
Replaces draft-daboo-valarm-extensions
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state In WG Last Call (wg milestone: Jul 2020 - Submit valarm docume... )
Document shepherd Bron Gondwana
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Bron Gondwana <brong@fastmailteam.com>
Network Working Group                                           C. Daboo
Internet-Draft                                                     Apple
Updates: 5545 (if approved)                            K. Murchison, Ed.
Intended status: Standards Track                                FastMail
Expires: July 20, 2020                                  January 17, 2020

                    VALARM Extensions for iCalendar
                 draft-ietf-calext-valarm-extensions-01

Abstract

   This document defines a set of extensions to the iCalendar VALARM
   component to enhance use of alarms and improve interoperability
   between clients and servers.

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 July 20, 2020.

Copyright Notice

   Copyright (c) 2020 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.

Daboo & Murchison         Expires July 20, 2020                 [Page 1]
Internet-Draft              VALARM Extensions               January 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   3
   3.  Extensible syntax for VALARM  . . . . . . . . . . . . . . . .   3
   4.  Alarm Unique Identifier . . . . . . . . . . . . . . . . . . .   5
   5.  Alarm Related To  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  Alarm Acknowledgement . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Acknowledged Property . . . . . . . . . . . . . . . . . .   7
   7.  Snoozing Alarms . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Relationship Type Property Parameter  . . . . . . . . . .   8
   8.  Alarm Proximity Trigger . . . . . . . . . . . . . . . . . . .   9
     8.1.  Proximity Property  . . . . . . . . . . . . . . . . . . .  10
     8.2.  Example . . . . . . . . . . . . . . . . . . . . . . . . .  11
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   10. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  11
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
     11.1.  Property Registrations . . . . . . . . . . . . . . . . .  12
     11.2.  Relationship Types Registry  . . . . . . . . . . . . . .  12
     11.3.  Proximity Value Registry . . . . . . . . . . . . . . . .  12
   12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     13.2.  Informative References . . . . . . . . . . . . . . . . .  13
     13.3.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Appendix A.  Change History (To be removed by RFC Editor before
                publication) . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   The iCalendar [RFC5545] specification defines a set of components
   used to describe calendar data.  One of those is the "VALARM"
   component which appears as a sub-component of "VEVENT" and "VTODO"
   components.  The "VALARM" component is used to specify a reminder for
   an event or task.  Different alarm actions are possible, as are
   different ways to specify how the alarm is triggered.

   As iCalendar has become more widely used and as client-server
   protocols such as CalDAV [RFC4791] have become more popular, several
   issues with "VALARM" components have arisen.  Most of these relate to
   the need to extend the existing "VALARM" component with new
   properties and behaviors to allow clients and servers to accomplish
   specific tasks in an interoperable manner.  For example, clients
   typically need a way to specify that an alarm has been dismissed by a
Show full document text