idnits 2.17.1 draft-ietf-avt-smpte292-video-08.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3497 5 Title: RTP Payload Format for Society of Motion Picture 6 and Television Engineers (SMPTE) 292M Video 7 Author(s): L. Gharai, C. Perkins, G. Goncher, A. Mankin 8 Status: Standards Track 9 Date: March 2003 10 Mailbox: ladan@isi.edu, csp@isi.edu, mankin@psg.com, 11 Gary.Goncher@tek.com 12 Pages: 12 13 Characters: 26094 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-avt-smpte292-video-08.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3497.txt 20 This memo specifies an RTP payload format for encapsulating 21 uncompressed High Definition Television (HDTV) as defined by the 22 Society of Motion Picture and Television Engineers (SMPTE) standard, 23 SMPTE 292M. SMPTE is the main standardizing body in the motion 24 imaging industry and the SMPTE 292M standard defines a bit-serial 25 digital interface for local area HDTV transport. 27 This document is a product of the Audio/Video Transport Working Group 28 of the IETF. 30 This is now a Proposed Standard Protocol. 32 This document specifies an Internet standards track protocol for 33 the Internet community, and requests discussion and suggestions 34 for improvements. Please refer to the current edition of the 35 "Internet Official Protocol Standards" (STD 1) for the 36 standardization state and status of this protocol. Distribution 37 of this memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.