Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.3616     
  ITU-T A.5 justification information for referenced document IETF RFC 3515 (2003) in draft Q.3616
1. Clear description of the referenced document:
Name: IETF RFC 3515 (2003)
Title: The Session Initiation Protocol (SIP) Refer Method
2. Status of approval:
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
3. Justification for the specific reference:
Q.CDIV refers to overall specification of IETF RFC 3515 (2003) 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=3515
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:
9.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] Roach, A. B., "Session Initiation Protocol (SIP)-Specific Event/
Notification", RFC 3265, June 2002./
/
[3] Sparks, R., "Internet Media Type message/sipfrag", RFC 3420,/
November 2002./
/
9.2 Informative References/
/
[4] Sparks, R. and A. Johnston, "Session Initiation Protocol Call/
Control - Transfer", Work in Progress./
/
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
Note: This form is based on Recommendation ITU-T A.5