--- 1/draft-ietf-calext-valarm-extensions-01.txt 2020-07-13 12:14:28.971291114 -0700 +++ 2/draft-ietf-calext-valarm-extensions-02.txt 2020-07-13 12:14:29.007292024 -0700 @@ -1,19 +1,19 @@ 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 +Intended status: Standards Track Fastmail +Expires: January 14, 2021 July 13, 2020 VALARM Extensions for iCalendar - draft-ietf-calext-valarm-extensions-01 + draft-ietf-calext-valarm-extensions-02 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 @@ -22,21 +22,21 @@ 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. + This Internet-Draft will expire on January 14, 2021. 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 @@ -45,25 +45,25 @@ 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. 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 + 5. Alarm Related To . . . . . . . . . . . . . . . . . . . . . . 6 6. Alarm Acknowledgement . . . . . . . . . . . . . . . . . . . . 6 6.1. Acknowledged Property . . . . . . . . . . . . . . . . . . 7 7. Snoozing Alarms . . . . . . . . . . . . . . . . . . . . . . . 8 - 7.1. Relationship Type Property Parameter . . . . . . . . . . 8 + 7.1. Relationship Type Property Parameter . . . . . . . . . . 9 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 @@ -78,23 +78,23 @@ 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 + protocols such as CalDAV [RFC4791] have become more prevalent, + 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 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 specific to each client implementation, leading to poor interoperability. This specification defines a set of extensions to "VALARM" components to cover common requirements for alarms not currently addressed in @@ -196,26 +196,31 @@ ; and MAY occur more than once attendee / ; 'duration' and 'repeat' are both OPTIONAL, ; and MUST NOT occur more than once each, ; but if one occurs, so MUST the other duration / repeat + ; the following is OPTIONAL, + ; and MAY occur more than once + + attach + ) 4. Alarm Unique Identifier 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. The "UID" property defined here follows the definition 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 identifier that does not contain any security- or privacy-sensitive information. The "VALARM" component defined in Section 3 is extended here as: @@ -611,20 +616,24 @@ DOI 10.17487/RFC5546, December 2009, . 13.3. URIs [1] https://tools.ietf.org/html/bcp14 Appendix A. Change History (To be removed by RFC Editor before publication) + Changes in ietf-02: + + 1. Addressed some WGLC comments from Daniel Migault. + Changes in ietf-01: 1. Reintroduced the RELATED-TO property for VALARMs and the SNOOZE value for the RELTYPE property parameter. 2. Add Privacy Considerations section. Changes in ietf-00: 1. Submitted as CALEXT draft. @@ -711,17 +720,17 @@ Cyrus Daboo Apple Inc. 1 Infinite Loop Cupertino, CA 95014 USA Email: cyrus@daboo.name URI: http://www.apple.com/ Kenneth Murchison (editor) - FastMail US LLC + Fastmail US LLC 1429 Walnut St, Suite 1201 Philadephia, PA 19102 USA Email: murch@fastmailteam.com URI: http://www.fastmail.com/