|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5545 (2009)
|
|
Title:
|
Internet Calendaring and Scheduling Core Object Specification (iCalendar).
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC Published in 2009-09.
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 5545 (2009) contains the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to-dos, journal entries, and free/busy information, independent of any particular calendar service or protocol. ITU-T F.746.2 refers to this specification for the calendar data formats definition.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Current information about IPR issues can be found at https://datatracker.ietf.org/public/ipr_search.cgi.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC obsoletes RFC 2445, and updated by RFC5546, RFC6868. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of IETF RFC 5545 is "Proposed Standard". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
The status of IETF RFC 5545 is "Proposed Standard". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] [ISO.8601.2004] International Organization for Standardization, "Data elements and interchange formats -- Information interchange -- Representation of dates and times", 2004./
[2] [ISO.9070.1991] International Organization for Standardization, "Information Technology_SGML Support Facilities -- Registration Procedures for Public Text Owner Identifiers, Second Edition", April 1991./
[3] [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996./
[4] [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996. /
[5] [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[6] [RFC2368] Hoffman, P., Masinter, L., and J. Zawinski, "The mailto URL scheme", RFC 2368, July 1998./
[7] [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003./
[8] [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005./
[9] [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", BCP 13, RFC 4288, December 2005./
[10] [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006./
[11] [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008./
[12] [RFC5646] Phillips, A., Ed., and M. Davis, Ed., "Tags for Identifying Languages", BCP 47, RFC 5646, September 2009./
[13] [US-ASCII] American National Standards Institute, "Coded Character Set - 7-bit American Standard Code for Information Interchange", ANSI X3.4, 1986. /
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
