|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3923 (2004)
|
|
Title:
|
End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP), IETF RFC, 2004.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-1 uses End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) discussed in [28] for securing messages.
|
|
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=3923
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[CERT] Ramsdell, B., Ed., "Secure/Multipurpose Internet Mail/
Extensions (S/MIME) Version 3.1 Certificate Handling",/
RFC 3850, July 2004./
/
[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC/
3852, July 2004./
/
[CMS-AES] Schaad, J., "Use of the Advanced Encryption Standard/
(AES) Encryption Algorithm in Cryptographic Message/
Syntax (CMS)", RFC 3565, July 2003./
/
[CMS-ALG] Housley, R., "Cryptographic Message Syntax (CMS)/
Algorithms", RFC 3370, August 2002./
/
[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./
/
[DATETIME] Klyne, G. and C. Newman, "Date and Time on the/
Internet: Timestamps", RFC 3339, July 2002./
/
[DISP] Troost, R., Dorner, S., and K. Moore, Ed.,/
"Communicating Presentation Information in Internet/
Messages: The Content-Disposition Header Field", RFC/
2183, August 1997./
/
[IMP-MODEL] Day, M., Rosenberg, J., and H. Sugano, "A Model for/
Presence and Instant Messaging", RFC 2778, February/
2000./
/
[IMP-REQS] Day, M., Aggarwal, S., Mohr, G., and J. Vincent,/
"Instant Messaging/Presence Protocol Requirements", RFC/
2779, February 2000./
/
[MSGFMT] Klyne, G. and D. Atkins, "Common Presence and Instant/
Messaging (CPIM): Message Format", RFC 3862, August/
2004./
/
[MULTI] Galvin, J., Murphy, S., Crocker, S., and N. Freed,/
"Security Multiparts for MIME: Multipart/Signed and/
Multipart/Encrypted", RFC 1847, October 1995./
/
[PIDF] Sugano, H., Fujimoto, S., Klyne, G., Bateman, A., Carr,/
W., and J. Peterson, "Presence Information Data Format/
(PIDF)", RFC 3863, August 2004./
/
[SMIME] Ramsdell, B., Ed., "Secure/Multipurpose Internet Mail/
Extensions (S/MIME) Version 3.1 Message Specification",/
RFC 3851, July 2004./
/
[TERMS] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[XML-MEDIA] Murata, M., St. Laurent, S. and D. Kohn, "XML Media/
Types", RFC 3023, January 2001./
/
[XMPP-CORE] Saint-Andre, P., Ed., "Extensible Messaging and/
Presence Protocol (XMPP): Core", RFC 3920, October/
2004./
/
[XMPP-IM] Saint-Andre, P., Ed., "Extensible Messaging and/
Presence Protocol (XMPP) Instant Messaging and/
Presence", RFC 3921, October 2004./
/
Informative References/
/
[CAPS] Hildebrand, J. and P. Saint-Andre, "Entity/
Capabilities", JSF JEP 0115, August 2004./
/
[CMC] Myers, M., Liu, X., Schaad, J. and J. Weinstein,/
"Certificate Management Messages over CMS", RFC 2797,/
April 2000./
/
[CMP] Adams, C. and S. Farrell, "Internet X.509 Public Key/
Infrastructure Certificate Management Protocols", RFC/
2510, March 1999./
/
[DISCO] Hildebrand, J., Millard, P., Eatmon, R. and P. Saint-/
Andre, "Service Discovery", JSF JEP 0030, July 2004./
/
[MUC] Saint-Andre, P., "Multi-User Chat", JSF JEP 0045, June/
2004./
/
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,/
"Extensible Markup Language (XML) 1.0 (3rd ed)", W3C/
REC-xml, February 2004, http://www.w3.org/TR/REC-xml./
/
[XML-REG] Mealling, M., "The IETF XML Registry", BCP 81, RFC/
3688, January 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):
|
|
|
None
|
|
