1.
|
Clear description of the referenced document:
|
|
|
2.
|
Status of approval:
|
|
Standards-track RFC - Proposed Standard approved March 2016
|
3.
|
Justification for the specific reference:
|
|
In VSS, for RTP-based elementary stream packaging of video/audio data, the RTP payload format for H.265 is specified in IETF RFC 7798.
|
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=7798
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7798.
|
6.
|
The degree of stability or maturity of the document:
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state. No errata exist.
|
7.
|
Relationship with other existing or emerging documents:
|
|
N/A
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
Normative References /
[H.264] ITU-T, "Advanced video coding for generic audiovisual/
services", ITU-T Recommendation H.264, April 2013./
/
[HEVC] ITU-T, "High efficiency video coding", ITU-T Recommendation/
H.265, April 2013./
/
[ISO23008-2]/
ISO/IEC, "Information technology -- High efficiency coding/
and media delivery in heterogeneous environments -- Part 2:/
High efficiency video coding", ISO/IEC 23008-2, 2013./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
http://www.rfc-editor.org/info/rfc2119./
/
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model/
with Session Description Protocol (SDP)", RFC 3264,/
DOI 10.17487/RFC3264, June 2002,/
http://www.rfc-editor.org/info/rfc3264./
/
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V./
Jacobson, "RTP: A Transport Protocol for Real-Time/
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, July/
2003, http://www.rfc-editor.org/info/rfc3550./
/
[RFC3551] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and/
Video Conferences with Minimal Control", STD 65, RFC 3551,/
DOI 10.17487/RFC3551, July 2003,/
http://www.rfc-editor.org/info/rfc3551./
/
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K./
Norrman, "The Secure Real-time Transport Protocol (SRTP)",/
RFC 3711, DOI 10.17487/RFC3711, March 2004,/
http://www.rfc-editor.org/info/rfc3711./
/
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session/
Description Protocol", RFC 4566, DOI 10.17487/RFC4566, July/
2006, http://www.rfc-editor.org/info/rfc4566./
/
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,/
"Extended RTP Profile for Real-time Transport Control/
Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585,/
DOI 10.17487/RFC4585, July 2006,/
http://www.rfc-editor.org/info/rfc4585./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,/
http://www.rfc-editor.org/info/rfc4648./
/
[RFC5104] Wenger, S., Chandra, U., Westerlund, M., and B. Burman,/
"Codec Control Messages in the RTP Audio-Visual Profile/
with Feedback (AVPF)", RFC 5104, DOI 10.17487/RFC5104,/
February 2008, http://www.rfc-editor.org/info/rfc5104./
[RFC5124] Ott, J. and E. Carrara, "Extended Secure RTP Profile for/
Real-time Transport Control Protocol (RTCP)-Based Feedback/
(RTP/SAVPF)", RFC 5124, DOI 10.17487/RFC5124, February/
2008, http://www.rfc-editor.org/info/rfc5124./
/
[RFC5234] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax/
Specifications: ABNF", STD 68, RFC 5234,/
DOI 10.17487/RFC5234, January 2008,/
http://www.rfc-editor.org/info/rfc5234./
/
[RFC5576] Lennox, J., Ott, J., and T. Schierl, "Source-Specific Media/
Attributes in the Session Description Protocol (SDP)",/
RFC 5576, DOI 10.17487/RFC5576, June 2009,/
http://www.rfc-editor.org/info/rfc5576./
/
[RFC5583] Schierl, T. and S. Wenger, "Signaling Media Decoding/
Dependency in the Session Description Protocol (SDP)",/
RFC 5583, DOI 10.17487/RFC5583, July 2009,/
http://www.rfc-editor.org/info/rfc5583./
/
Informative References/
/
[3GPDASH] 3GPP, "Transparent end-to-end Packet-switched Streaming/
Service (PSS); Progressive Download and Dynamic Adaptive/
Streaming over HTTP (3GP-DASH)", 3GPP TS 26.247 12.1.0,/
December 2013./
/
[3GPPFF] 3GPP, "Transparent end-to-end packet switched streaming/
service (PSS); 3GPP file format (3GP)", 3GPP TS 26.244/
12.20, December 2013./
/
[CABAC] Sole, J., Joshi, R., Nguyen, N., Ji, T., Karczewicz, M.,/
Clare, G., Henry, F., and Duenas, A., "Transform/
coefficient coding in HEVC", IEEE Transactions on Circuts/
and Systems for Video Technology, Vol. 22, No. 12,/
pp. 1765-1777, DOI 10.1109/TCSVT.2012.2223055, December/
2012./
/
[Girod99] Girod, B. and Faerber, F., "Feedback-based error control/
for mobile video transmission", Proceedings of the IEEE,/
Vol. 87, No. 10, pp. 1707-1723, DOI 10.1109/5.790632,/
October 1999./
/
[H.265.1] ITU-T, "Conformance specification for ITU-T H.265 high/
efficiency video coding", ITU-T Recommendation H.265.1,/
October 2014./
[HEVCv2] Flynn, D., Naccari, M., Rosewarne, C., Sharman, K., Sole,/
J., Sullivan, G. J., and T. Suzuki, "High Efficiency Video/
Coding (HEVC) Range Extensions text specification: Draft/
7", JCT-VC document JCTVC-Q1005, 17th JCT-VC meeting,/
Valencia, Spain, March/April 2014./
/
[IS014496-12]/
IS0/IEC, "Information technology - Coding of audio-visual/
objects - Part 12: ISO base media file format", IS0/IEC/
14496-12, 2015./
/
[IS015444-12]/
IS0/IEC, "Information technology - JPEG 2000 image coding/
system - Part 12: ISO base media file format", IS0/IEC/
15444-12, 2015./
/
[JCTVC-J0107]/
Wang, Y.-K., Chen, Y., Joshi, R., and Ramasubramonian, K.,/
"AHG9: On RAP pictures", JCT-VC document JCTVC-L0107, 10th/
JCT-VC meeting, Stockholm, Sweden, July 2012./
/
[MPEG2S] ISO/IEC, "Information technology - Generic coding of moving/
pictures and associated audio information - Part 1:/
Systems", ISO International Standard 13818-1, 2013./
/
[MPEGDASH] ISO/IEC, "Information technology - Dynamic adaptive/
streaming over HTTP (DASH) -- Part 1: Media presentation/
description and segment formats", ISO International/
Standard 23009-1, 2012./
/
[RFC2326] Schulzrinne, H., Rao, A., and R. Lanphier, "Real Time/
Streaming Protocol (RTSP)", RFC 2326, DOI 10.17487/RFC2326,/
April 1998, http://www.rfc-editor.org/info/rfc2326./
/
[RFC2974] Handley, M., Perkins, C., and E. Whelan, "Session/
Announcement Protocol", RFC 2974, DOI 10.17487/RFC2974,/
October 2000, http://www.rfc-editor.org/info/rfc2974./
/
[RFC6051] Perkins, C. and T. Schierl, "Rapid Synchronisation of RTP/
Flows", RFC 6051, DOI 10.17487/RFC6051, November 2010,/
http://www.rfc-editor.org/info/rfc6051./
/
[RFC6184] Wang, Y.-K., Even, R., Kristensen, T., and R. Jesup, "RTP/
Payload Format for H.264 Video", RFC 6184,/
DOI 10.17487/RFC6184, May 2011,/
http://www.rfc-editor.org/info/rfc6184./
[RFC6190] Wenger, S., Wang, Y.-K., Schierl, T., and A. Eleftheriadis,/
"RTP Payload Format for Scalable Video Coding", RFC 6190,/
DOI 10.17487/RFC6190, May 2011,/
http://www.rfc-editor.org/info/rfc6190./
/
[RFC7201] Westerlund, M. and C. Perkins, "Options for Securing RTP/
Sessions", RFC 7201, DOI 10.17487/RFC7201, April 2014,/
http://www.rfc-editor.org/info/rfc7201./
/
[RFC7202] Perkins, C. and M. Westerlund, "Securing the RTP Framework:/
Why RTP Does Not Mandate a Single Media Security Solution",/
RFC 7202, DOI 10.17487/RFC7202, April 2014,/
http://www.rfc-editor.org/info/rfc7202./
/
[RFC7656] Lennox, J., Gross, K., Nandakumar, S., Salgueiro, G., and/
B. Burman, Ed., "A Taxonomy of Semantics and Mechanisms for/
Real-Time Transport Protocol (RTP) Sources", RFC 7656,/
DOI 10.17487/RFC7656, November 2015,/
http://www.rfc-editor.org/info/rfc7656./
/
[RFC7667] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 7667,/
DOI 10.17487/RFC7667, November 2015,/
http://www.rfc-editor.org/info/rfc7667./
/
[RTP-MULTI-STREAM]
|
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.
|
|