draft-ietf-calext-extensions-00.txt   draft-ietf-calext-extensions-01.txt 
Network Working Group C. Daboo Network Working Group C. Daboo
Internet-Draft Apple Inc. Internet-Draft Apple Inc.
Updates: 5545 (if approved) April 6, 2015 Intended status: Standards Track October 8, 2015
Intended status: Standards Track Expires: April 10, 2016
Expires: October 8, 2015
New Properties for iCalendar New Properties for iCalendar
draft-ietf-calext-extensions-00 draft-ietf-calext-extensions-01
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 33 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 October 8, 2015. This Internet-Draft will expire on April 10, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 9, line 18 skipping to change at page 9, line 18
Property Parameters: IANA and non-standard property parameters can Property Parameters: IANA and non-standard property parameters can
be specified on this property. be specified on this property.
Conformance: This property can be specified once in an iCalendar Conformance: This property can be specified once in an iCalendar
object. object.
Description: This property identifies a location where a client can Description: This property identifies a location where a client can
retrieve updated data for the calendar. Clients SHOULD honor any retrieve updated data for the calendar. Clients SHOULD honor any
specified "REFRESH-INTERVAL" value when periodically retrieving specified "REFRESH-INTERVAL" value when periodically retrieving
data. data. Note that this property differs from the "URL" property in
that "URL" is meant to provide an alternative representation of
the calendar data, rather than the original location of the data.
Format Definition: This property is defined by the following Format Definition: This property is defined by the following
notation: notation:
source = "SOURCE" sourceparam ":" uri CRLF source = "SOURCE" sourceparam ":" uri CRLF
sourceparam = *(";" other-param) sourceparam = *(";" other-param)
Example: The following is an example of this property: Example: The following is an example of this property:
skipping to change at page 16, line 23 skipping to change at page 16, line 23
6.4. LABEL Property Parameter 6.4. LABEL Property Parameter
Parameter Name: LABEL Parameter Name: LABEL
Purpose: To provide a human readable label. Purpose: To provide a human readable label.
Format Definition: This property parameter is defined by the Format Definition: This property parameter is defined by the
following notation: following notation:
infoparam = "LABEL" "=" param-value labelparam = "LABEL" "=" param-value
Description: This property parameter MAY be specified on the Description: This property parameter MAY be specified on the
"CONFERENCE" property. It is anticipated that other extensions to "CONFERENCE" property. It is anticipated that other extensions to
iCalendar will re-use this property parameter on new properties iCalendar will re-use this property parameter on new properties
that they define. As a result, clients SHOULD expect to find this that they define. As a result, clients SHOULD expect to find this
property parameter present on many different properties. It property parameter present on many different properties. It
provides a human readable label that can be presented to calendar provides a human readable label that can be presented to calendar
users to allow them to discriminate between properties which might users to allow them to discriminate between properties which might
be similar, or provide additional information for properties that be similar, or provide additional information for properties that
are not self-describing. are not self-describing.
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, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/
RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
[RFC5545] Desruisseaux, B., "Internet Calendaring and Scheduling [RFC5545] Desruisseaux, B., Ed., "Internet Calendaring and
Core Object Specification (iCalendar)", RFC 5545, Scheduling Core Object Specification (iCalendar)", RFC
September 2009. 5545, DOI 10.17487/RFC5545, September 2009,
<http://www.rfc-editor.org/info/rfc5545>.
[W3C.REC-css3-color-20110607] [W3C.REC-css3-color-20110607]
Celik, T., Lilley, C., and D. Baron, "CSS Color Module A&#135;elik, T., Lilley, C., and D. Baron, "CSS Color
Level 3", World Wide Web Consortium Recommendation REC- Module Level 3", World Wide Web Consortium Recommendation
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, August [RFC2397] Masinter, L., "The "data" URL scheme", RFC 2397, DOI
1998. 10.17487/RFC2397, August 1998,
<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", RFC
3966, December 2004. 3966, DOI 10.17487/RFC3966, December 2004,
<http://www.rfc-editor.org/info/rfc3966>.
[RFC5546] Daboo, C., "iCalendar Transport-Independent [RFC5546] Daboo, C., Ed., "iCalendar Transport-Independent
Interoperability Protocol (iTIP)", RFC 5546, December Interoperability Protocol (iTIP)", RFC 5546, DOI 10.17487/
2009. RFC5546, December 2009,
<http://www.rfc-editor.org/info/rfc5546>.
[RFC7230] Fielding, R. and J. Reschke, "Hypertext Transfer Protocol [RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
(HTTP/1.1): Message Syntax and Routing", RFC 7230, June Protocol (HTTP/1.1): Message Syntax and Routing", RFC
2014. 7230, DOI 10.17487/RFC7230, June 2014,
<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-01:
1. Clarified difference between SOURCE and URL properties.
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.
2. Fixed tel: URI reference. 2. Fixed tel: URI reference.
Changes in draft-daboo-icalendar-extensions-09: Changes in draft-daboo-icalendar-extensions-09:
1. Re-instated a trimmed down version of the CONFERENCE property 1. Re-instated a trimmed down version of the CONFERENCE property
after serious interest expressed by implementors. after serious interest expressed by implementors.
 End of changes. 14 change blocks. 
25 lines changed or deleted 41 lines changed or added

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