|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Standards Track RFC.
|
|
3.
|
Justification for the specific reference:
|
|
|
This Recommendation describes the usage of the Flow identifier (FID) SDP semantic with H.248. It references a use case from RFC 4588 that cannot be emulated by the existing H.248 ReserveGroup/Value constructs.
|
|
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=4588
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 4588 has been in existence since 2006. This document has been reviewed extensively in the IETF. Errata exist.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 4588 belongs to the suite of RFC related to protocol "RTP".
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,/
"Extended RTP profile for Real-time Transport Control Protocol/
(RTCP)-Based feedback", RFC 4585, July 2006./
/
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[3] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,/
"RTP: A Transport Protocol for Real-Time Applications", STD 64,/
RFC 3550, July 2003./
/
[4] Casner, S., "Session Description Protocol (SDP) Bandwidth/
Modifiers for RTP Control Protocol (RTCP) Bandwidth", RFC 3556,/
July 2003./
/
[5] Handley, M. and V. Jacobson, "SDP: Session Description/
Protocol", RFC 2327, April 1998./
/
[6] Camarillo, G., Eriksson, G., Holler, J., and H. Schulzrinne,/
"Grouping of Media Lines in the Session Description Protocol/
(SDP)", RFC 3388, December 2002./
/
[7] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time Streaming/
Protocol (RTSP)", RFC 2326, April 1998.
|
|
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.
|
|
