|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards track RFC - Proposed Standard approved December 2002; Errata exist.
|
|
3.
|
Justification for the specific reference:
|
|
|
Session Initiation Protocol (SIP) Extension for Instant Messaging is used to implemant the session control applications such as PU control, information query and alarm event notification and distribution.
|
|
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=3428
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Standards track RFC - Proposed Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards track RFC - Proposed Standard. Errata exist. Updated by RFC 8591.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Updated by RFC 8591
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
15.Normative References/
/
[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,/
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:/
Session Initiation Protocol", RFC 3261, June 2002./
/
[2] Day, M., Aggarwal, S. and J. Vincent, "Instant Messaging //
Presence Protocol Requirements", RFC 2779, February 2000./
/
[3] Day, M., Rosenberg, J. and H. Sugano, "A Model for Presence and/
Instant Messaging", RFC 2778, February 2000./
/
[4] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3369,/
August 2002./
/
[5] Roach, A., "Session Initiation Protocol (SIP)-Specific Event/
Notification", RFC 3265, June 2002./
/
[6] Bradner, S., "Keywords for Use in RFC's to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
16. Informational References/
/
[7] Atkins, D. and G. Klyne, "Common Presence and Instant Messaging/
Message Format", Work in Progress./
/
[8] Crocker, D., Diacakis, A., Mazzoldi, F., Huitema, C., Klyne, G.,/
Rose, M., Rosenberg, J., Sparks, R., Sugano, H. and J. Peterson,/
"Address Resolution for Instant Messaging and Presence", Work in/
Progress./
/
[9] Rosenberg, J. and H. Schulzrinne, "SIP Caller Preferences and/
Callee Capabilities", Work in Progress./
/
[10] Schaad, J. and R. Housley, "Use of the AES Encryption Algorithm/
and RSA-OAEP Key Transport in CMS", Work in Progress./
/
[11] DellaFera, C., Eichin, M., French, R., Jedlinski, D., Kohl, J./
and W. Sommerfeld, "The Zephyr notification service", in USENIX/
Winter Conference (Dallas, Texas), Feb. 1988./
|
|
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
|
|
