|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 7044 (2014)
|
|
Title:
|
An Extension to the Session Initiation Protocol (SIP) for Request History Information
|
|
|
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.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=7044
|
|
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:
|
|
|
17.1. 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./
/
[RFC3326] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason/
Header Field for the Session Initiation Protocol (SIP)",/
RFC 3326, December 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./
/
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234, January 2008./
/
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security/
(TLS) Protocol Version 1.2", RFC 5246, August 2008./
/
[RFC4244] Barnes, M., "An Extension to the Session Initiation/
Protocol (SIP) for Request History Information", RFC/
4244, November 2005./
/
17.2. Informative References/
/
[RFC5627] Rosenberg, J., "Obtaining and Using Globally Routable/
User Agent URIs (GRUUs) in the Session Initiation/
Protocol (SIP)", RFC 5627, October 2009./
/
[RFC5630] Audet, F., "The Use of the SIPS URI Scheme in the Session/
Initiation Protocol (SIP)", RFC 5630, October 2009./
/
[RFC3087] Campbell, B. and R. Sparks, "Control of Service Context/
using SIP Request-URI", RFC 3087, April 2001./
/
[RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network/
Media Services with SIP", RFC 4240, December 2005./
/
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC/
3966, December 2004./
/
[RFC4458] Jennings, C., Audet, F., and J. Elwell, "Session/
Initiation Protocol (SIP) URIs for Applications such as/
Voicemail and Interactive Voice Response (IVR)", RFC/
4458, April 2006./
/
[CALLFLOWS] Barnes, M., Audet, F., Schubert, S., Elburg, H., and C./
Holmberg, "Session Initiation Protocol (SIP) History-Info/
Header Call Flow Examples", Work in Progress, November/
2013.
|
|
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
|
|
