This page will soon be deactivated—explore our new, faster, mobile-friendly site, now centralized in MyWorkspace!

Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : F.746.2     
  ITU-T A.5 justification information for referenced document IETF RFC 6351 (2011) in draft F.746.2
1. Clear description of the referenced document:
Name: IETF RFC 6351 (2011)
Title: xCard: vCard XML Representation.
2. Status of approval:
Standards track RFC Published in 2011.
3. Justification for the specific reference:
IETF RFC 6351 (2011) defines xCard,an XML representation for vCard. The underlying data structure is exactly the same, enabling a 1-to-1 mapping between the original vCard format and the XML representation. The XML formatting may be preferred in some contexts where an XML engine is readily available and may be reused instead of writing a standalone vCard parser. ITU-T F.746.2 refers to this specification for the contacts 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:
RFC - Proposed Standard (August 2011; Errata exist). Updated by RFC 6868.
6. The degree of stability or maturity of the document:
The status of IETF RFC 6351 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 6351 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:
[ISO.19757-2.2008] International Organization for Standardization, "Information technology -- Document Schema Definition Language (DSDL) -- Part 2: Regular-grammar-based validation -- RELAX NG", ISO International Standard 19757-2, October 2008./
[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./
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, August 2011./
[W3C.REC-xml-20081126] Paoli, J., Yergeau, F., Maler, E., Bray, T., and C. Sperberg-McQueen, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", World Wide Web Consortium Recommendation REC-xml-20081126, November 2008, http://www.w3.org/TR/2008/REC-xml-20081126./
[W3C.REC-xml-names-20091208] Bray, T., Hollander, D., Layman, A., Tobin, R., and H. Thompson, "Namespaces in XML 1.0 (Third Edition)", World Wide Web Consortium Recommendation REC-xml-names-20091208, December 2009, http://www.w3.org/TR/2009/REC-xml-names-20091208. /
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):
N/A.
Note: This form is based on Recommendation ITU-T A.5