draft-ietf-calext-subscription-upgrade-00.txt   draft-ietf-calext-subscription-upgrade-01.txt 
Network Working Group M. Douglass Network Working Group M. Douglass
Internet-Draft Spherical Cow Group Internet-Draft Spherical Cow Group
Updates: 5988,7240 (if approved) June 7, 2019 Updates: 5988,7240 (if approved) November 3, 2019
Intended status: Standards Track Intended status: Standards Track
Expires: December 9, 2019 Expires: May 6, 2020
Calendar subscription upgrades Calendar subscription upgrades
draft-ietf-calext-subscription-upgrade-00 draft-ietf-calext-subscription-upgrade-01
Abstract Abstract
This specification introduces an approach to allow subscribers to This specification introduces an approach to allow subscribers to
calendar feeds to upgrade to a more performant protocol. calendar feeds to upgrade to a more performant protocol.
This specification updates [RFC5545] to add the value DELETED to the This specification updates [RFC5545] to add the value DELETED to the
STATUS property. STATUS property.
This specification also updates [RFC7240] to add the subscribe- This specification also updates [RFC7240] to add the subscribe-
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 December 9, 2019. This Internet-Draft will expire on May 6, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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 40 skipping to change at page 2, line 40
7.3. subscribe-caldav-auth . . . . . . . . . . . . . . . . . . 11 7.3. subscribe-caldav-auth . . . . . . . . . . . . . . . . . . 11
7.4. subscribe-webdav-sync . . . . . . . . . . . . . . . . . . 11 7.4. subscribe-webdav-sync . . . . . . . . . . . . . . . . . . 11
7.5. subscribe-enhanced-get . . . . . . . . . . . . . . . . . 11 7.5. subscribe-enhanced-get . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 11 8. Security Considerations . . . . . . . . . . . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9.1. Sync-Token HTTP Header Field Registration . . . . . . . . 12 9.1. Sync-Token HTTP Header Field Registration . . . . . . . . 12
9.2. Preference Registrations . . . . . . . . . . . . . . . . 12 9.2. Preference Registrations . . . . . . . . . . . . . . . . 12
9.3. Link Relation Registrations . . . . . . . . . . . . . . . 13 9.3. Link Relation Registrations . . . . . . . . . . . . . . . 13
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
11. Normative References . . . . . . . . . . . . . . . . . . . . 13 11. Normative References . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 14 Appendix A. Open issues . . . . . . . . . . . . . . . . . . . . 15
Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 15 Appendix B. Change log . . . . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
Currently clients subscribe to calendar feeds as an iCalendar file Currently clients subscribe to calendar feeds as an iCalendar file
which is often published as a resource accessible using the which is often published as a resource accessible using the
unofficial 'webcal' scheme. unofficial 'webcal' scheme.
The only available option for updating that resource is the usual The only available option for updating that resource is the usual
skipping to change at page 3, line 16 skipping to change at page 3, line 16
response to changes and servers not wishing to be overloaded by response to changes and servers not wishing to be overloaded by
frequent requests for possibly large amounts of data. frequent requests for possibly large amounts of data.
This specification introduces an approach whereby clients can This specification introduces an approach whereby clients can
discover a more performant access method. Given the location of the discover a more performant access method. Given the location of the
resource as an iCalendar file, the client can perfom a HEAD request resource as an iCalendar file, the client can perfom a HEAD request
on the resource and inspect the returned headers which will offer a on the resource and inspect the returned headers which will offer a
number of alternative access methods. number of alternative access methods.
Given that many clients and servers already support CalDAV this Given that many clients and servers already support CalDAV this
provides an easy upgrade path for those clients. CalDAV and DAV provides an easy upgrade path for those clients. Additionally an
subsets are specified here to allow lighter weight implementations. enhanced GEt protocol is specified here to allow a light weight
implementation.
The use of subscription upgtafe may help reduce load on servers, but
perhaps more inportantly it allows mobile devices to use a more
efficient update mechanism reducing data tranferred and presumably
improving battery life.
1.1. Terms and Definitions 1.1. Terms and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Additionally, the rule for URI is included from [RFC3986]. Additionally, the rule for URI is included from [RFC3986].
skipping to change at page 13, line 10 skipping to change at page 13, line 10
Provide a limit on the number of components in the response. Provide a limit on the number of components in the response.
Reference Reference
this document this document
9.3. Link Relation Registrations 9.3. Link Relation Registrations
This document defines the following new iCalendar properties to be This document defines the following new iCalendar properties to be
added to the registry defined in section=8.2.3 [RFC5545]: added to the registry defined in section=8.2.3 [RFC5545]:
+------------------------+-------------+--------------+ +------------------------+-------------+-------------+
| Relation Name | Description | Reference | | Relation Name | Description | Reference |
+------------------------+-------------+--------------+ +------------------------+-------------+-------------+
| subscribe-caldav | Current | Section 7.2 | | subscribe-caldav | Current | Section 7.2 |
| subscribe-caldav_auth | Current | Section 7.3 | | subscribe-caldav_auth | Current | Section 7.3 |
| subscribe-webdav-sync | Current | Section 7.4 | | subscribe-webdav-sync | Current | Section 7.4 |
| subscribe-enhanced_get | Current | Section 7.5 | | subscribe-enhanced_get | Current | Section 7.5 |
+------------------------+-------------+--------------+ +------------------------+-------------+-------------+
10. Acknowledgements 10. Acknowledgements
The author would also like to thank the members of the CalConnect The author would also like to thank the members of the CalConnect
Calendar Sharing technical committee and the following individuals Calendar Sharing technical committee and the following individuals
for contributing their ideas and support: for contributing their ideas and support:
Marten Gajda, Ken Murchison, Garry Shutler Marten Gajda, Ken Murchison, Garry Shutler
The authors would also like to thank CalConnect, the Calendaring and The authors would also like to thank CalConnect, the Calendaring and
Scheduling Consortium, for advice with this specification. Scheduling Consortium, for advice with this specification.
11. Normative References 11. Normative References
[I-D.ietf-calext-extensions]
Daboo, C., "New Properties for iCalendar", draft-ietf-
calext-extensions-05 (work in progress), August 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 2434, IANA Considerations Section in RFCs", RFC 2434,
DOI 10.17487/RFC2434, October 1998, DOI 10.17487/RFC2434, October 1998,
<https://www.rfc-editor.org/info/rfc2434>. <https://www.rfc-editor.org/info/rfc2434>.
skipping to change at page 14, line 45 skipping to change at page 15, line 5
<https://www.rfc-editor.org/info/rfc7240>. <https://www.rfc-editor.org/info/rfc7240>.
[RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", [RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary",
RFC 7991, DOI 10.17487/RFC7991, December 2016, RFC 7991, DOI 10.17487/RFC7991, December 2016,
<https://www.rfc-editor.org/info/rfc7991>. <https://www.rfc-editor.org/info/rfc7991>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[W3C.REC-xml-20060816]
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth
Edition)", World Wide Web Consortium Recommendation REC-
xml-20060816, August 2006,
<http://www.w3.org/TR/2006/REC-xml-20060816>.
Appendix A. Open issues Appendix A. Open issues
Vary Vary
Ensure we get that right. Ensure we get that right.
Appendix B. Change log Appendix B. Change log
calext00 2019-06-05 MD calext00 2019-06-05 MD
o First calext version o First calext version
 End of changes. 9 change blocks. 
15 lines changed or deleted 32 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/