On Tue, Feb 06, 2001 at 11:39:55PM -0700, Warren Young wrote:
> 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)
>
> 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.
Well, one of my colleagues has already written code to
parse an MPEG-I stream and break it up into MPEG frames.
RFC 2250 defines a RTP extension header format to precede each MPEG
frame, so I just want to use that header format.
Apart from remembering to create the RTP extension header in
network byte order, it's not too bad.
Where is the best place to stick a hook in the Ethereal code
for adding an RTP MPEG dissector?
Do I need to make a heuristic, or non-heuristic dissector?
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@xxxxxxxxxxxx
