|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3840 (2004)
|
|
Title:
|
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
It is used as a reference in the Recommendation ITU-T Q.1912.5
|
|
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=3840
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
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:
|
|
|
14.1. 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] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[3] Holtman, K., Mutz, A., and T. Hardie, "Media Feature Tag/
Registration Procedure", BCP 31, RFC 2506, March 1999./
/
[4] Klyne, G., "A Syntax for Describing Media Feature Sets", RFC/
2533, March 1999./
/
[5] Klyne, G., "Corrections to "A Syntax for Describing Media/
Feature Sets"", RFC 2738, December 1999./
/
[6] Hoffman, P., "Registration of Charset and Languages Media/
Features Tags", RFC 2987, November 2000./
/
[7] Klyne, G., "MIME Content Types in Media Feature Expressions",/
RFC 2913, September 2000./
/
[8] Handley, M. and V. Jacobson, "SDP: Session Description/
Protocol", RFC 2327, April 1998./
/
[9] Roach, A.B., "Session Initiation Protocol (SIP)-Specific Event/
Notification", RFC 3265, June 2002./
/
[10] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifiers (URI): Generic Syntax", RFC 2396, August/
1998./
/
14.2. Informative References/
/
[11] Rosenberg, J., Schulzrinne, H. and P. Kyzivat, "Caller/
Preferences for the Session Initiation Protocol (SIP)", RFC/
3841, August 2004./
/
[12] Mahy, R., "A Message Summary and Message Waiting Indication/
Event Package for the Session Initiation Protocol (SIP)", RFC/
3842, August 2004./
/
[13] Rosenberg, J., "A Framework for Conferencing with the Session/
Initiation Protocol", Work in Progress, May 2003./
/
[14] Howes, T. and M. Smith, "LDAP: String Representation of Search/
Filters", Work in Progress, March 2003./
/
[15] Peterson, J., "Enhancements for Authenticated Identity/
Management in the Session Initiation Protocol (SIP)", Work in/
Progress, March 2003./
/
[16] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., and/
D. Gurle, "Session Initiation Protocol (SIP) Extension for/
Instant Messaging", RFC 3428, December 2002./
/
[17] Klyne, G., "Protocol-independent Content Negotiation/
Framework", RFC 2703, September 1999./
/
[18] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA/
Considerations Section in RFCs", BCP 26, RFC 2434, October/
1998./
/
|
|
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
|
|
