|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3920 (2004)
|
|
Title:
|
Extensible Messaging and Presence Protocol (XMPP): Core, October 2004.
|
|
|
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=3920
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since October 2004. This text is an Internet Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 3920 was published in October, 2004. It is 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 3920 defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints.
|
|
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 2234, November 1997./
[BASE64] Josefsson, S., “The Base16, Base32, and Base64 Data Encodings”, RFC 3548, July 2003./
[CHARSET] Alvestrand, H., "IETF Policy on Character Sets and Languages”, BCP 18, RFC 2277, January 1998./
[DIGEST-MD5] Leach, P. and C. Newman, "Using Digest Authentication as a SASL Mechanism”, RFC 2831, May 2000./
[DNS] Mockapetris, P., “Domain names - implementation and specification”, STD 13,RFC 1035, November 1987./
[GSS-API] Linn, J., “Generic Security Service Application Program Interface Version 2, Update 1”, RFC 2743, January 2000./
[HTTP-TLS] Rescorla, E., “HTTP Over TLS”, RFC 2818, May 2000./
[IDNA] Faltstrom, P., Hoffman, P., and A. Costello, “Internationalizing Domain Names in Applications (IDNA)”, RFC 3490, March 2003./
[IPv6] Hinden, R. and S. Deering, “Internet Protocol Version 6 (IPv6) Addressing Architecture”, RFC 3513, April 2003./
[LANGTAGS] Alvestrand, H., “Tags for the Identification of Languages”, BCP 47, RFC 3066, January 2001./
[NAMEPREP] Hoffman, P. and M. Blanchet, “Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)”, RFC 3491, March 2003./
[RANDOM] Eastlake 3rd, D., Crocker, S., and J. Schiller, “Randomness Recommendations for Security”, RFC 1750, December 1994./
[SASL] Myers, J., “Simple Authentication and Security Layer (SASL)”, RFC 2222, October 1997./
[SRV] Gulbrandsen, A., Vixie, P., and L. Esibov, “A DNS RR for specifying the location of services (DNS SRV)”, RFC 2782, February 2000./
[STRINGPREP] Hoffman, P. and M. Blanchet, “Preparation of Internationalized Strings (“stringprep”)”, RFC 3454, December 2002./
[TCP] Postel, J., “Transmission Control Protocol”, STD 7, RFC 793, September 1981./
[TERMS] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997./
[TLS] Dierks, T. and C. Allen, “The TLS Protocol Version 1.0”, RFC 2246, January 1999./
[UCS2] International Organization for Standardization, “Information Technology – Universal Multiple-octet coded Character Set (UCS) – Amendment 2: UCS Transformation Format 8 (UTF-8)”, ISO Standard 10646-1 Addendum 2, October 1996./
[UTF-8] Yergeau, F., “UTF-8, a transformation format of ISO 10646”, STD 63, RFC 3629, November 2003./
[X509] Housley, R., Polk, W., Ford, W., and D. Solo, “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile”, RFC 3280, April 2002./
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, “Extensible Markup Language (XML) 1.0 (2nd ed)”, W3C REC-xml, October 2000, http://www.w3.org/TR/REC-xml./
[XML-NAMES] Bray, T., Hollander, D., and A. Layman, “Namespaces in XML”, W3C REC-xml-names, January 1999, http://www.w3.org/TR/REC-xml-names./
Informative References/
[ACAP] Newman, C. and J. Myers, “ACAP – Application Configuration Access Protocol”, RFC 2244, November 1997./
[ASN.1] CCITT, “Recommendation X.208: Specification of Abstract Syntax Notation One (ASN.1)”, 1988./
[DNSSEC] Eastlake 3rd, D., “Domain Name System Security Extensions”, RFC 2535, March 1999./
[HTTP] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol – HTTP/1.1”,RFC 2616, June 1999./
[IMAP] Crispin, M., “INTERNET MESSAGE ACCESS PROTOCOL – VERSION 4rev1”,RFC 3501, March 2003./
[IMP-REQS] Day, M., Aggarwal, S., Mohr, G., and J. Vincent, “Instant Messaging / Presence Protocol Requirements”, RFC 2779, February 2000./
[IRC] Oikarinen, J. and D. Reed, “Internet Relay Chat Protocol”, RFC 1459, May 1993./
[JEP-0029] Kaes, C., “Definition of Jabber Identifiers (JIDs)", JSF JEP 0029, October 2003./
[JEP-0078] Saint-Andre, P., “Non-SASL Authentication”, JSF JEP 0078, July 2004./
[JEP-0086] Norris, R. and P. Saint-Andre, “Error Condition Mappings”, JSF JEP 0086, February 2004./
[JSF] Jabber Software Foundation, “Jabber Software Foundation”, http://www.jabber.org/./
[POP3] Myers, J. and M. Rose, “Post Office Protocol – Version 3”, STD 53, RFC 1939, May 1996./
[SIMPLE] SIMPLE Working Group, “SIMPLE WG”, http://www.ietf.org/html.charters/simple-charter.html./
[SMTP] Klensin, J., “Simple Mail Transfer Protocol”, RFC 2821, April 2001./
[URI] Berners-Lee, T., Fielding, R., and L. Masinter, “Uniform Resource Identifiers (URI): Generic Syntax”, RFC 2396, August 1998./
[USINGTLS] Newman, C., “Using TLS with IMAP, POP3 and ACAP”, RFC 2595, June 1999./
[XML-REG] Mealling, M., “The IETF XML Registry”, BCP 81, RFC 3688, January 2004./
[XMPP-IM] Saint-Andre, P., Ed., “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.
|
|
