|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5626 (2009)
|
|
Title:
|
Managing Client-Initiated Connection in the Session Initiation Protocol (SIP)
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
References are necessary to support Transport Level Security, which is required by IPCablecom2.
|
|
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=5626
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997./
/
[RFC2506] Holtman, K., Mutz, A., and T. Hardie, "Media Feature/
Tag Registration Procedure", BCP 31, RFC 2506,/
March 1999./
/
[RFC3261] 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./
/
[RFC3263] Rosenberg, J. and H. Schulzrinne, "Session Initiation/
Protocol (SIP): Locating SIP Servers", RFC 3263,/
June 2002./
/
[RFC3327] Willis, D. and B. Hoeneisen, "Session Initiation/
Protocol (SIP) Extension Header Field for Registering/
Non-Adjacent Contacts", RFC 3327, December 2002./
/
[RFC3581] Rosenberg, J. and H. Schulzrinne, "An Extension to the/
Session Initiation Protocol (SIP) for Symmetric/
Response Routing", RFC 3581, August 2003./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, November 2003./
/
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,/
"Indicating User Agent Capabilities in the Session/
Initiation Protocol (SIP)", RFC 3840, August 2004./
/
[RFC3841] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,/
"Caller Preferences for the Session Initiation/
Protocol (SIP)", RFC 3841, August 2004./
/
[RFC3968] Camarillo, G., "The Internet Assigned Number Authority/
(IANA) Header Field Parameter Registry for the Session/
Initiation Protocol (SIP)", BCP 98, RFC 3968,/
December 2004./
/
[RFC3969] 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./
/
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally/
Unique IDentifier (UUID) URN Namespace", RFC 4122,/
July 2005./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
/
[RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,/
"Session Traversal Utilities for NAT (STUN)",/
RFC 5389, October 2008./
/
/
/
|
|
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
|
|
