|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Internet Standards Track specification
|
|
3.
|
Justification for the specific reference:
|
|
|
This is a normative reference in ITU-T J.484
|
|
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=8216
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
version 7 of this protocol. Last updated on 2020-01-21
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Internet Standards Track specification
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
not available
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[AC_3] Advanced Television Systems Committee, "Digital Audio/
Compression (AC-3) (E-AC-3) Standard", ATSC/
Standard A/52:2010, November 2010,
wp-content/uploads/2015/03/A52-201212-17.pdf>./
/
[AES_128] National Institute of Standards and Technology, "Advanced/
Encryption Standard (AES)", FIPS PUB 197,/
DOI 10.6028/NIST.FIPS.197, November 2001,/
./
/
[CEA608] Consumer Electronics Association, "ANSI/CEA 608-E: Line 21/
Data Services", April 2008./
/
[CEA708] Consumer Technology Association, "Digital Television (DTV)/
Closed Captioning", ANSI/CTA Standard CEA-708-E, August/
2013,
ANSI-CTA-708-E-Preview.pdf>./
/
[COMMON_ENC]/
International Organization for Standardization,/
"Information technology -- MPEG systems technologies --/
Part 7: Common encryption in ISO base media file format/
files", ISO/IEC 23001-7:2016, February 2016,/
catalogue_detail.htm?csnumber=68042>./
/
[H_264] International Telecommunications Union, "Advanced video/
coding for generic audiovisual services", January 2012,/
./
/
[HDCP] Digital Content Protection LLC, "High-bandwidth Digital/
Content Protection System - Mapping HDCP to HDMI",/
February 2013,
sites/default/files/specifications//
HDCP%20on%20HDMI%20Specification%20Rev2_2_Final1.pdf>./
/
[ISO_13818]/
International Organization for Standardization, "Generic/
coding of moving pictures and associated audio/
information", ISO/IEC International Standard 13818,/
October 2007,/
./
/
[ISO_13818_3]/
International Organization for Standardization, "ISO/IEC/
International Standard 13818-3:1998; Generic coding of/
moving pictures and associated audio information - Part 3:/
Audio", April 1998,/
catalogue_detail.htm?csnumber=26797>./
/
[ISO_13818_7]/
International Organization for Standardization, "Generic/
coding of moving pictures and associated audio information/
- Part 7: Advanced Audio Coding (AAC)", ISO/IEC/
International Standard 13818-3:2006, January 2006,/
catalogue_detail.htm?csnumber=43345>./
/
[ISO_14496]/
International Organization for Standardization,/
"Information technology -- Coding of audio-visual objects/
-- Part 3: Audio", ISO/IEC 14496-3:2009, 2009,/
./
/
[ISO_8601] International Organization for Standardization, "Data/
elements and interchange formats -- Information/
interchange -- Representation of dates and times", ISO/IEC/
International Standard 8601:2004, December 2004,/
./
/
[ISOBMFF] International Organization for Standardization,/
"Information technology -- Coding of audio-visual objects/
-- Part 12: ISO base media file format",/
ISO/IEC 14496-12:2015, December 2015,/
catalogue_detail.htm?csnumber=68960>./
/
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail/
Extensions (MIME) Part Two: Media Types", RFC 2046,/
DOI 10.17487/RFC2046, November 1996,/
./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
./
/
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,/
DOI 10.17487/RFC2818, May 2000,/
./
/
[RFC2964] Moore, K. and N. Freed, "Use of HTTP State Management",/
BCP 44, RFC 2964, DOI 10.17487/RFC2964, October 2000,/
./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November/
2003, ./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66,/
RFC 3986, DOI 10.17487/RFC3986, January 2005,/
./
/
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying/
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,/
September 2009, ./
/
[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70,/
RFC 5652, DOI 10.17487/RFC5652, September 2009,/
./
/
[RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265,/
DOI 10.17487/RFC6265, April 2011,/
./
/
[RFC6381] Gellens, R., Singer, D., and P. Frojdh, "The 'Codecs' and/
'Profiles' Parameters for "Bucket" Media Types", RFC 6381,/
DOI 10.17487/RFC6381, August 2011,/
./
/
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data/
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March/
2014, ./
/
[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer/
Protocol (HTTP/1.1): Message Syntax and Routing",/
RFC 7230, DOI 10.17487/RFC7230, June 2014,/
./
/
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC/
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,/
May 2017, ./
/
[SCTE35] Society of Cable Telecommunications Engineers, "Digital/
Program Insertion Cueing Message for Cable", ANSI/SCTE 35,/
August 2014,
ANSI_SCTE%2035%202014.pdf>./
/
[US_ASCII] American National Standard for Information Systems, "Coded/
Character Sets - 7-Bit American National Standard Code for/
Information Interchange (7-Bit ASCII)", ANSI X3.4,/
December 1986./
/
[WebVTT] World Wide Web Consortium (W3C), "WebVTT: The Web Video/
Text Tracks Format", Draft Community Group Report, June/
2017, ./
/
|
|
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
|
|
