|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3262 (2002)
|
|
Title:
|
Reliability of Provisional Responses 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:
|
|
|
The document is used as a reference in Q.4014.1
|
|
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=3262
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC - Proposed Standard (IETF Stream) 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:
|
|
|
12 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] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with/
SDP", RFC 3264, June 2002./
/
13 Informative References/
/
[4] Handley, M., Schulzrinne, H., Schooler, E. and J. Rosenberg,/
"SIP: Session Initiation Protocol", RFC 2543, March 1999./
|
|
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
|
