draft-ietf-calext-extensions-01.txt   draft-ietf-calext-extensions-02.txt 
Network Working Group C. Daboo Network Working Group C. Daboo
Internet-Draft Apple Inc. Internet-Draft Apple Inc.
Intended status: Standards Track October 8, 2015 Intended status: Standards Track May 24, 2016
Expires: April 10, 2016 Expires: November 25, 2016
New Properties for iCalendar New Properties for iCalendar
draft-ietf-calext-extensions-01 draft-ietf-calext-extensions-02
Abstract Abstract
This document defines a set of new properties for iCalendar data as This document defines a set of new properties for iCalendar data as
well as extending the use of some existing properties to the entire well as extending the use of some existing properties to the entire
iCalendar object. iCalendar object.
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 32 skipping to change at page 1, line 32
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 April 10, 2016. This Internet-Draft will expire on November 25, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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
skipping to change at page 2, line 40 skipping to change at page 2, line 40
8.1. Property Registrations . . . . . . . . . . . . . . . . . 17 8.1. Property Registrations . . . . . . . . . . . . . . . . . 17
8.2. Parameter Registrations . . . . . . . . . . . . . . . . . 17 8.2. Parameter Registrations . . . . . . . . . . . . . . . . . 17
8.3. Display Types Registry . . . . . . . . . . . . . . . . . 18 8.3. Display Types Registry . . . . . . . . . . . . . . . . . 18
8.4. Feature Types Registry . . . . . . . . . . . . . . . . . 18 8.4. Feature Types Registry . . . . . . . . . . . . . . . . . 18
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative References . . . . . . . . . . . . . . . . . . 18 10.1. Normative References . . . . . . . . . . . . . . . . . . 18
10.2. Informative References . . . . . . . . . . . . . . . . . 19 10.2. Informative References . . . . . . . . . . . . . . . . . 19
Appendix A. Change History (To be removed by RFC Editor before Appendix A. Change History (To be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 19 publication) . . . . . . . . . . . . . . . . . . . . 19
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 21 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
The iCalendar [RFC5545] data format is used to represent calendar The iCalendar [RFC5545] data format is used to represent calendar
data and is used with iTIP [RFC5546] to handle scheduling operations data and is used with iTIP [RFC5546] to handle scheduling operations
between calendar users. iCalendar is in widespread use, and in between calendar users. iCalendar is in widespread use, and in
accordance with provisions in that specification, extension elements accordance with provisions in that specification, extension elements
have been added by various vendors to the data format in order to have been added by various vendors to the data format in order to
support and enhance capabilities. This specification collects a support and enhance capabilities. This specification collects a
number of these ad-hoc extensions and uses the new IANA registry number of these ad-hoc extensions and uses the new IANA registry
skipping to change at page 18, line 48 skipping to change at page 18, line 48
Thanks to the following for feedback: Bernard Desruisseaux, Mike Thanks to the following for feedback: Bernard Desruisseaux, Mike
Douglass, Lucia Fedorova, Ken Murchison, Arnaud Quillaud, and Dave Douglass, Lucia Fedorova, Ken Murchison, Arnaud Quillaud, and Dave
Thewlis. This specification came about via discussions at the Thewlis. This specification came about via discussions at the
Calendaring and Scheduling Consortium. Calendaring and Scheduling Consortium.
10. References 10. References
10.1. Normative References 10.1. Normative References
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/ Specifications: ABNF", STD 68, RFC 5234,
RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>. <http://www.rfc-editor.org/info/rfc5234>.
[RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", RFC Scheduling Core Object Specification (iCalendar)",
5545, DOI 10.17487/RFC5545, September 2009, RFC 5545, DOI 10.17487/RFC5545, September 2009,
<http://www.rfc-editor.org/info/rfc5545>. <http://www.rfc-editor.org/info/rfc5545>.
[W3C.REC-css3-color-20110607] [W3C.REC-css3-color-20110607]
A&#135;elik, T., Lilley, C., and D. Baron, "CSS Color A&#135;elik, T., Lilley, C., and D. Baron, "CSS Color
Module Level 3", World Wide Web Consortium Recommendation Module Level 3", World Wide Web Consortium Recommendation
REC-css3-color-20110607, June 2011, REC-css3-color-20110607, June 2011,
<http://www.w3.org/TR/2011/REC-css3-color-20110607>. <http://www.w3.org/TR/2011/REC-css3-color-20110607>.
10.2. Informative References 10.2. Informative References
[RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, DOI [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397,
10.17487/RFC2397, August 1998, DOI 10.17487/RFC2397, August 1998,
<http://www.rfc-editor.org/info/rfc2397>. <http://www.rfc-editor.org/info/rfc2397>.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers",
3966, DOI 10.17487/RFC3966, December 2004, RFC 3966, DOI 10.17487/RFC3966, December 2004,
<http://www.rfc-editor.org/info/rfc3966>. <http://www.rfc-editor.org/info/rfc3966>.
[RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent
Interoperability Protocol (iTIP)", RFC 5546, DOI 10.17487/ Interoperability Protocol (iTIP)", RFC 5546,
RFC5546, December 2009, DOI 10.17487/RFC5546, December 2009,
<http://www.rfc-editor.org/info/rfc5546>. <http://www.rfc-editor.org/info/rfc5546>.
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
Protocol (HTTP/1.1): Message Syntax and Routing", RFC Protocol (HTTP/1.1): Message Syntax and Routing",
7230, DOI 10.17487/RFC7230, June 2014, RFC 7230, DOI 10.17487/RFC7230, June 2014,
<http://www.rfc-editor.org/info/rfc7230>. <http://www.rfc-editor.org/info/rfc7230>.
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 draft-ietf-calext-extensions-02:
1. Refresh expired draft - no changes.
Changes in draft-ietf-calext-extensions-01: Changes in draft-ietf-calext-extensions-01:
1. Clarified difference between SOURCE and URL properties. 1. Clarified difference between SOURCE and URL properties.
2. Use labelparam not infoparam. 2. Use labelparam not infoparam.
Changes in draft-ietf-calext-extensions-00: Changes in draft-ietf-calext-extensions-00:
1. Document renamed after WG adoption. 1. Document renamed after WG adoption.
 End of changes. 13 change blocks. 
20 lines changed or deleted 24 lines changed or added

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