|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5009 (2007)
|
|
Title:
|
Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC - Proposed Standard approved September 2007
|
|
3.
|
Justification for the specific reference:
|
|
|
It is used as a reference in 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/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since June 2007.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
