Message-Id: <200301202006.PAA29291@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , avt@ietf.org From: The IESG Subject: CORRECTION W/ RFC EDITOR NOTE: Protocol Action: RTP Payload Format for SMPTE 292M Video to Proposed Standard Date: Mon, 20 Jan 2003 15:06:49 -0500 Sender: owner-ietf-announce@ietf.org Precedence: bulk **PLEASE NOTE RFC EDITOR NOTE.** The IESG has approved the Internet-Draft 'RTP Payload Format for SMPTE 292M Video' as a Proposed Standard. This document is the product of the Audio/Video Transport Working Group. The IESG contact persons are Scott Bradner and Allison Mankin. Technical Summary This document specifies a RTP payload format for encapsulating uncompressed High Definition Television (HDTV) as defined by the Society of Motion Picture and Television Engineers (SMPTE) standard, SMPTE 292M. SMPTE is the main standardizing body in the motion imaging industry and the SMPTE 292M standard defines a bit-serial digital interface for local area HDTV transport and defines a universal medium of interchange for uncompressed High Definition Television (HDTV) between various types of video equipment (cameras, encoders, VTRs, etc.). SMPTE 292M stipulates that the source data be in 10 bit words and the total data rate be either 1.485 Gbps or 1.485/1.001 Gbps. The use of a dedicated serial interconnect is appropriate in a studio environment, but it is desirable to leverage the widespread availability of high bandwidth IP connectivity to allow efficient wide area delivery of area delivery of SMPTE 292M format content. This memo defines a way to do so. Working Group Summary The AVT working group supported publication of this document on the standards track. Protocol Quality This document was reviewed for the IESG by Scott Bradner. RFC Editor: please make the following changes before publishing this ID Section 6, 1st paragraph OLD: RFC1889 recommends transmission of RTCP packets every 5 seconds or at a reduced minimum in seconds of 360 divided by the session bandwidth in kilobits/second. At 1.485 Gbps the reduced minimum interval computes to 0.2ms or 4028 packets per second. NEW: RTCP SHOULD be used as specified in RFC1889[3], which specifies two limits on the RTCP packet rate: RTCP bandwidth should be limited to 5% of the data rate, and the minimum for the average of the randomized intervals between RTCP packets should be 5 seconds. Considering the high data rate of this payload format, the minimum interval is the governing factor in this case. Section 13, 3rd and 4th paragraphs: OLD: [3] H. Schulzrinne, S. Casner, R. Frederick and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", IETF, Work in Progress (draft-ietf-avt-rtp-new-11.txt) [4] H. Schulzrinee and S. Casner, "RTP Profile for Audio and Video Conferences with Minimal Control", IETF, Work in progress, (draft-ietf-avt-profile-new-12.txt). NEW: [3] H. Schulzrinne, S. Casner, R. Frederick and V. Jacobson, "RTP: A Transport Protocol for Real-Time Applications", IETF, January 1996, RFC1889. [4] H. Schulzrinne and S. Casner, "RTP Profile for Audio and Video Conferences with Minimal Control", IETF, January 1996, RFC1890.