draft-ietf-calext-valarm-extensions-01.txt   draft-ietf-calext-valarm-extensions-02.txt 
Network Working Group C. Daboo Network Working Group C. Daboo
Internet-Draft Apple Internet-Draft Apple
Updates: 5545 (if approved) K. Murchison, Ed. Updates: 5545 (if approved) K. Murchison, Ed.
Intended status: Standards Track FastMail Intended status: Standards Track Fastmail
Expires: July 20, 2020 January 17, 2020 Expires: January 14, 2021 July 13, 2020
VALARM Extensions for iCalendar VALARM Extensions for iCalendar
draft-ietf-calext-valarm-extensions-01 draft-ietf-calext-valarm-extensions-02
Abstract Abstract
This document defines a set of extensions to the iCalendar VALARM This document defines a set of extensions to the iCalendar VALARM
component to enhance use of alarms and improve interoperability component to enhance use of alarms and improve interoperability
between clients and servers. between clients and servers.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 20, 2020. This Internet-Draft will expire on January 14, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 11 skipping to change at page 2, line 11
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Extensible syntax for VALARM . . . . . . . . . . . . . . . . 3 3. Extensible syntax for VALARM . . . . . . . . . . . . . . . . 3
4. Alarm Unique Identifier . . . . . . . . . . . . . . . . . . . 5 4. Alarm Unique Identifier . . . . . . . . . . . . . . . . . . . 5
5. Alarm Related To . . . . . . . . . . . . . . . . . . . . . . 5 5. Alarm Related To . . . . . . . . . . . . . . . . . . . . . . 6
6. Alarm Acknowledgement . . . . . . . . . . . . . . . . . . . . 6 6. Alarm Acknowledgement . . . . . . . . . . . . . . . . . . . . 6
6.1. Acknowledged Property . . . . . . . . . . . . . . . . . . 7 6.1. Acknowledged Property . . . . . . . . . . . . . . . . . . 7
7. Snoozing Alarms . . . . . . . . . . . . . . . . . . . . . . . 8 7. Snoozing Alarms . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Relationship Type Property Parameter . . . . . . . . . . 8 7.1. Relationship Type Property Parameter . . . . . . . . . . 9
8. Alarm Proximity Trigger . . . . . . . . . . . . . . . . . . . 9 8. Alarm Proximity Trigger . . . . . . . . . . . . . . . . . . . 9
8.1. Proximity Property . . . . . . . . . . . . . . . . . . . 10 8.1. Proximity Property . . . . . . . . . . . . . . . . . . . 10
8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 11 8.2. Example . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. Security Considerations . . . . . . . . . . . . . . . . . . . 11 9. Security Considerations . . . . . . . . . . . . . . . . . . . 11
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 11 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 11
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
11.1. Property Registrations . . . . . . . . . . . . . . . . . 12 11.1. Property Registrations . . . . . . . . . . . . . . . . . 12
11.2. Relationship Types Registry . . . . . . . . . . . . . . 12 11.2. Relationship Types Registry . . . . . . . . . . . . . . 12
11.3. Proximity Value Registry . . . . . . . . . . . . . . . . 12 11.3. Proximity Value Registry . . . . . . . . . . . . . . . . 12
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
skipping to change at page 2, line 44 skipping to change at page 2, line 44
1. Introduction 1. Introduction
The iCalendar [RFC5545] specification defines a set of components The iCalendar [RFC5545] specification defines a set of components
used to describe calendar data. One of those is the "VALARM" used to describe calendar data. One of those is the "VALARM"
component which appears as a sub-component of "VEVENT" and "VTODO" component which appears as a sub-component of "VEVENT" and "VTODO"
components. The "VALARM" component is used to specify a reminder for components. The "VALARM" component is used to specify a reminder for
an event or task. Different alarm actions are possible, as are an event or task. Different alarm actions are possible, as are
different ways to specify how the alarm is triggered. different ways to specify how the alarm is triggered.
As iCalendar has become more widely used and as client-server As iCalendar has become more widely used and as client-server
protocols such as CalDAV [RFC4791] have become more popular, several protocols such as CalDAV [RFC4791] have become more prevalent,
issues with "VALARM" components have arisen. Most of these relate to several issues with "VALARM" components have arisen. Most of these
the need to extend the existing "VALARM" component with new relate to the need to extend the existing "VALARM" component with new
properties and behaviors to allow clients and servers to accomplish properties and behaviors to allow clients and servers to accomplish
specific tasks in an interoperable manner. For example, clients specific tasks in an interoperable manner. For example, clients
typically need a way to specify that an alarm has been dismissed by a typically need a way to specify that an alarm has been dismissed by a
calendar user, or has been "snoozed" by a set amount of time. To calendar user, or has been "snoozed" by a set amount of time. To
date, this has been done through the use of custom "X-" properties date, this has been done through the use of custom "X-" properties
specific to each client implementation, leading to poor specific to each client implementation, leading to poor
interoperability. interoperability.
This specification defines a set of extensions to "VALARM" components This specification defines a set of extensions to "VALARM" components
to cover common requirements for alarms not currently addressed in to cover common requirements for alarms not currently addressed in
skipping to change at page 5, line 19 skipping to change at page 5, line 19
; and MAY occur more than once ; and MAY occur more than once
attendee / attendee /
; 'duration' and 'repeat' are both OPTIONAL, ; 'duration' and 'repeat' are both OPTIONAL,
; and MUST NOT occur more than once each, ; and MUST NOT occur more than once each,
; but if one occurs, so MUST the other ; but if one occurs, so MUST the other
duration / repeat duration / repeat
; the following is OPTIONAL,
; and MAY occur more than once
attach
) )
4. Alarm Unique Identifier 4. Alarm Unique Identifier
This extension adds a "UID" property to "VALARM" components to allow This extension adds a "UID" property to "VALARM" components to allow
a unique identifier to specified. The value of this property can a unique identifier to be specified. The value of this property can
then be used to refer uniquely to the "VALARM" component. then be used to refer uniquely to the "VALARM" component.
The "UID" property defined here follows the definition in The "UID" property defined here follows the definition in
Section 3.8.4.7 of [RFC5545] with the security and privacy updates in Section 3.8.4.7 of [RFC5545] with the security and privacy updates in
Section 5.3 of [RFC7986]. In particular it MUST be a globally unique Section 5.3 of [RFC7986]. In particular it MUST be a globally unique
identifier that does not contain any security- or privacy-sensitive identifier that does not contain any security- or privacy-sensitive
information. information.
The "VALARM" component defined in Section 3 is extended here as: The "VALARM" component defined in Section 3 is extended here as:
skipping to change at page 14, line 12 skipping to change at page 14, line 12
DOI 10.17487/RFC5546, December 2009, DOI 10.17487/RFC5546, December 2009,
<https://www.rfc-editor.org/info/rfc5546>. <https://www.rfc-editor.org/info/rfc5546>.
13.3. URIs 13.3. URIs
[1] https://tools.ietf.org/html/bcp14 [1] https://tools.ietf.org/html/bcp14
Appendix A. Change History (To be removed by RFC Editor before Appendix A. Change History (To be removed by RFC Editor before
publication) publication)
Changes in ietf-02:
1. Addressed some WGLC comments from Daniel Migault.
Changes in ietf-01: Changes in ietf-01:
1. Reintroduced the RELATED-TO property for VALARMs and the SNOOZE 1. Reintroduced the RELATED-TO property for VALARMs and the SNOOZE
value for the RELTYPE property parameter. value for the RELTYPE property parameter.
2. Add Privacy Considerations section. 2. Add Privacy Considerations section.
Changes in ietf-00: Changes in ietf-00:
1. Submitted as CALEXT draft. 1. Submitted as CALEXT draft.
skipping to change at page 16, line 17 skipping to change at page 16, line 19
Cyrus Daboo Cyrus Daboo
Apple Inc. Apple Inc.
1 Infinite Loop 1 Infinite Loop
Cupertino, CA 95014 Cupertino, CA 95014
USA USA
Email: cyrus@daboo.name Email: cyrus@daboo.name
URI: http://www.apple.com/ URI: http://www.apple.com/
Kenneth Murchison (editor) Kenneth Murchison (editor)
FastMail US LLC Fastmail US LLC
1429 Walnut St, Suite 1201 1429 Walnut St, Suite 1201
Philadephia, PA 19102 Philadephia, PA 19102
USA USA
Email: murch@fastmailteam.com Email: murch@fastmailteam.com
URI: http://www.fastmail.com/ URI: http://www.fastmail.com/
 End of changes. 10 change blocks. 
11 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/