|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3556 (2003)
|
|
Title:
|
Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth.
|
|
|
2.
|
Status of approval:
|
|
|
Approved as a standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
H.248.1 Annex C uses a bandwidth modifier that is defined in this RFC.
|
|
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=3556
|
|
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:
|
|
|
Normative References/
/
[1] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:/
A Transport Protocol for Real-Time Applications," RFC 3550, July/
2003./
/
[2] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video/
Conferences with Minimal Control", RFC 3551, July 2003./
/
[3] Handley, M. and V. Jacobson, "SDP: Session Description Protocol",/
RFC 2327, April 1998./
/
/
Informative References/
/
[4] Handley, M., Jacobson, V. and C. Perkins, "SDP: Session/
Description Protocol", 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):
|
|
|
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.
|
