|
1.
|
Clear description of the referenced document:
|
|
|
|
|
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.30xx_VoLTE_Interconnection_FW
|
|
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=4028
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard. RFC - Proposed Standard (IETF Stream)
Was draft-ietf-sip-session-timer
Errata exist.
|
|
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:
|
|
|
15.1. Normative References/
/
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[2] 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./
/
[3] Rosenberg, J., "The Session Initiation Protocol (SIP) UPDATE/
Method", RFC 3311, October 2002./
/
[4] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with/
Session Description Protocol (SDP)", RFC 3264, June 2002./
/
15.2. Informative References/
/
[5] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,/
"RTP: A Transport Protocol for Real-Time Applications", STD 64,/
RFC 3550, July 2003./
/
[6] Srisuresh, P. and M. Holdrege, "IP Network Address Translator/
(NAT) Terminology and Considerations", RFC 2663, August 1999./
/
[7] Rosenberg, J. and H. Schulzrinne, "Reliability of Provisional/
Responses in Session Initiation Protocol (SIP)", RFC 3262, June/
2002./
/
[8] Roach, A., "Session Initiation Protocol (SIP)-Specific Event/
Notification", RFC 3265, June 2002./
|
|
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
|
|
