|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC approved in 2011-08.
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 6321 (2011) defines "xCal", an XML format for iCalendar data, which defined as a straightforward mapping into XML from iCalendar, so that iCalendar data can be converted to XML, and then back to iCalendar, without losing any semantic meaning in the data. Anyone creating xCal calendar data according to this specification will know that their data can be converted to a valid iCalendar representation as well. ITU-T F.746.2 refers to this specification for the calendar data XML 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:
|
|
|
Updated by RFC 6868. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of IETF RFC 6321 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 6321 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:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001./
[RFC3470] Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols", BCP 70, RFC 3470, January 2003./
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004./
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data. /
|
|
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
|
