|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5627 (2009)
|
|
Title:
|
Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
Q.CDIV refers to overall specification of IETF RFC 5627 (2009) for CDIV requirements.
|
|
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=5627
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
None known
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 5627 was approved in October 2009 and is stable.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[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] Rosenberg, J. and H. Schulzrinne, "Session Initiation Protocol/
(SIP): Locating SIP Servers", RFC 3263, June 2002./
/
[3] Willis, D. and B. Hoeneisen, "Session Initiation Protocol (SIP)/
Extension Header Field for Registering Non-Adjacent Contacts",/
RFC 3327, December 2002./
/
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[5] Roach, A., "Session Initiation Protocol (SIP)-Specific Event/
Notification", RFC 3265, June 2002./
/
[6] Sparks, R., "The Session Initiation Protocol (SIP) Refer/
Method", RFC 3515, April 2003./
/
[7] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating/
User Agent Capabilities in the Session Initiation Protocol/
(SIP)", RFC 3840, August 2004./
/
[8] Camarillo, G., "The Internet Assigned Number Authority (IANA)/
Header Field Parameter Registry for the Session Initiation/
Protocol (SIP)", BCP 98, RFC 3968, December 2004./
/
[9] Camarillo, G., "The Internet Assigned Number Authority (IANA)/
Uniform Resource Identifier (URI) Parameter Registry for the/
Session Initiation Protocol (SIP)", BCP 99, RFC 3969,/
December 2004./
/
[10] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session/
Description Protocol", RFC 4566, July 2006./
/
[11] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966,/
December 2004./
/
[12] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller/
Preferences for the Session Initiation Protocol (SIP)",/
RFC 3841, August 2004./
/
[13] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
/
[14] Jennings, C., Ed. and R. Mahy, Ed., "Managing Client-Initiated/
Connections in the Session Initiation Protocol (SIP)",/
RFC 5626, October 2009./
|
|
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
|
|
