Skip to main content

RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) 292M Video

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3497.
Authors Gary Goncher , Dr. Ladan Gharai , Allison J. Mankin , Colin Perkins
Last updated 2015-10-14 (Latest revision 2002-12-03)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3497 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Scott O. Bradner
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3497

        Title:      RTP Payload Format for Society of Motion Picture
                    and Television Engineers (SMPTE) 292M Video
        Author(s):  L. Gharai, C. Perkins, G. Goncher, A. Mankin
        Status:     Standards Track
        Date:       March 2003
        Pages:      12
        Characters: 26094
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-avt-smpte292-video-08.txt


This memo specifies an 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.

This document is a product of the Audio/Video Transport Working Group
of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.