Ethereal-dev: [Ethereal-dev] Re: [Ethereal-users] Adding MPEG payload type to packet-rtp.c?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Warren Young <warren@xxxxxxxxxxx>
Date: Tue, 06 Feb 2001 23:39:55 -0700
Craig Rodrigues wrote:
> 
> On Tue, Feb 06, 2001 at 04:20:33PM -0800, Guy Harris wrote:
> >
> > I checked in all the RTP payload types from RFC 1890.
> 
> Now, can someone give me an idea of how hard it would be
> to write a dissector to dissect the RTP extension header for MPEG I/II
> video in RFC 2250? (http://www.rfc-editor.org/rfc/rfc2250.txt)

Ugh...it's clear that the people who wrote this RFC enjoy standards like
MPEG.  I remember when it was possible to be given an RFC and know in
advance that it would be straightforward reading.

Okay, whining aside, implementing a dissector for this shouldn't be hard
at all if all you want to do is to parse the RTP extension headers and
report the state of the various flags and fields within.  This is about
all any Ethereal dissector does.  

The relevant info is in section 3, starting at section 3.3.  Most useful
are the ASCII art packet diagrams and the field descriptions that follow
each.  Try to ignore the jargon.  

Unless you have to implement the protocol, it should be safe to
completely ignore sections 1, 2, 4 and the appendices.  If you _are_
unlucky enough to have to implement it, my prayers go out to you, and I
say that as one who has written a program to scan MPEG 2 Program
streams.  Fully implementing RFC 2250 would be harder than that.  Much
harder.
-- 
= Warren -- ICBM Address: 36.8274040 N, 108.0204086 W, alt. 1714m