Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.1912.5     
  ITU-T A.5 justification information for referenced document IETF RFC 5079 (2007) in draft Q.1912.5
1. Clear description of the referenced document:
Name: IETF RFC 5079 (2007)
Title: Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)
2. Status of approval:
3. Justification for the specific reference:
It is used as a reference in the Recommendation ITU-T Q.1912.5
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=5079
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:
None
8. Any explicit references within that referenced document should also be listed:
Normative References/
/
[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./
/
[RFC3323] Peterson, J., "A Privacy Mechanism for the Session/
Initiation Protocol (SIP)", RFC 3323, November 2002./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC4474] Peterson, J. and C. Jennings, "Enhancements for/
Authenticated Identity Management in the Session/
Initiation Protocol (SIP)", RFC 4474, August 2006./
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