[AVT] Application of RFC3497 in pro-MPEG work

Greetings,

FYI - RFC3497, RTP Payload Format for SMPTE 292M Video - has been
cited in a commercial Code of Practice issued by the Pro-MPEG forum.

Pro-MPEG Code of Practice #4 release 1, July 2004, Transmission of
High Bit Rate Studio Streams over IP Networks is available at
http://www.pro-mpeg.org/publications/pdf/HBRSS-on-IP-CoP4-r1.pdf .

This application deviates somewhat from what we envisioned when the
RFC was written here. For example, its main application is for
270Mbit/sec standard definition video rather than 1.485Gbit/sec
high definition video. These two video standards are structured
so similarly that this works.

---- begin included text ----

The RTP format proposed is that from RFC3497 with the following 
extensions:
 For Standard Definition, the RTP timestamps shall be derived
   from a 27MHz clock locked to the input, not from the 148.5MHz
   clock required by RFC3497.
 For other video systems the RTP timestamp shall be the word
   clock rate of the video system.
 To assist with picture concealment in the event of lost packets,
   the data in a packet shall only come from one line1 of video.
   As an implication of this the EAV field will always occur
   at the start of a packet.
 In addition to this, there shall be a custom RTP header
   extension to assist with defining where in a line a particular
   packet starts which equipment which complies with this code
   of practice shall adopt.
---- end included text ----

The 4th bullet specifies an RFC3550 header extension.

Persons implementing RFC3497 may wish to test to be sure that
packets carrying this header extension don't break their
applications.

Peace,
  Chuck Harrison

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt