|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4622 (2006)
|
|
Title:
|
Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
H.350.7 includes XMPP in the suite of protocols that is supported in H.350, so that an organization can directory-enable and manage XMPP resources in the same way that other multimedia protocols (e.g. H.320, H.323, SIP) are managed in H.350. The schema provides a method for representing XMPP URIs and user information in the directory.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=4622
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since July 2006. This text is an Internet Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 4622 was published in July, 2006. It is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4622 defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[ABNF] Crocker, D. and P. overell, “Augmented BNF for Syntax Specifications: ABNF”, RFC 4234, Octorber 2005/
[IRI] Duerst, M. and M. Suignard, “Internationalized Resource Identifiers (IRIs)”, RFC 3987, January 2005./
[TERMS] Brander, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997./
[URI] Berners-Lee, T. Fielding, R., and L. Masinter, “Uniform Resource Identifier (URI): Generic Syntax”, STD 66, RFC 3986, January 2005. /
[XMPP-CORE] Saint-Andre, P., “Extensible Messaging and Presence Protocol (XMPP): Core”, RFC 3920, October 2004./
Informative References/
[CPIM] Peterson, J., “Common Profile for Instant Messaging (CPIM)”, RFC 3860, August 2004./
[CPP] Peterson, J., “Common Profile for Presence (CPP)”, RFC 3859, August 2004./
[DNS-SRV] Gulbrandsen, A., Vixie, P., and L. Esibov, “A DNS RR for specifying the location of services (DNS SRV)”, RFC 2782, February 2000./
[HTML] Raggett, D., “HTML 4.0 Specification”, W3C REC REC-html40-19980424, April 1998./
[HTTP-AUTH] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., and L. Stewart, “HTTP Authentication: Basic and Digest Access Authentication”, RFC 2617, June 1999./
[IDNA] Faltstrom, P., Hoffman, P., and A. Costello, “Internationalizing Domain Names in Applications (IDNA)”, RFC 3490, March 2003./
[JEP-0009] Adams, D., “Jabber-RPC”, JSF JEP 0009, February 2006./
[JEP-0030] Hildebrand, J., Millard, P., Eatmon, R., and P. Saint-Andre, “Service Discovery”, JSF JEP 0030, January 2006./
[JEP-0045] Saint-Andre, P., « Multi-User Chat », JSF JEP 0045, September 2005./
[JEP-0053] Saint-Andre, P., “Jabber Registrar”, JSF JEP 0053, May 2004./
[JEP-0060] Millard, P., Saint-Andre, P., and R. Meijer, “Publish-Subscribe”, JSF JEP 0060, June 2005./
[JEP-0072] Forno, F. and P. Saint-Andre, “SOAP Over XMPP”, JSF JEP 0072, December 2005./
[JEP-0077] Saint-Andre, P., “In-Band Registration”, JSF JEP 0077, January 2006./
[JEP-0147] Saint-Andre, P., “XMPP IRI/URI Query Components”, JSF JEP 0147, March 2006./
[MAILTO] Hoffman, P., Masinter, L., and J. Zawinski, “The mailto URL scheme”, RFC 2368, July 1998./
[MIME] Freed, N. and N. Borenstein, “Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types”, RFC 2046, November 1996./
[SASL] Melnikov, A. and K. Zeilenga, “Simple Authentication and Security Layer (SASL)”, RFC 4422, June 2006./
[STRINGPREP] Hoffman, P. and M. Blanchet, “Preparation of Internationalized Strings (“STRINGPREP”)”, RFC 3454, December 2002./
[UNICODE] The Unicode Consortium, “The Unicode Standard, Version 3.2.0”, 2000. The Unicode Standard, Version 3.2.0 is defined by the Unicode Standard, Version 3.0 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), as amended by the Unicode Standard Annex #27: Unicode 3.1 (http://www.unicode.ort/reports/tr27/) and by the Unicode Standard Annex #28: Unicode 3.2 (http://www.unicode.org/reports/tr28/). /
[URI-SCHEMES] Hansen, T., Hardie, T., and L. Masinter, “Guidelines and Registration Procedures for New URI Schemes”, RFC 4395, Februrary 2006./
[US-ASCII] American National Standards Institute, “Coded Character Set – 7-bit American Standard Code for Information Interchange”, ANSI X3.4, 1986./
[UTF-8] Yergeau, F., “UTF-8, a transformation format of ISO 10646”, STD 63, RFC 3629, November 2003./
[XMPP-IM] Saint-Andre, P., “Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence”, RFC 3921, October 2004.
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
