Re: Dissector plug-in for Pro-MPEG CoP 3 r2 (2dparityfec)

Is there any information that is specific to pro-MPEG payload? if there is,
then you can check this information in your dissector and ignore the packet
if it doesn't match that.

On 6/20/06, Mark Lewis <[email protected]> wrote:
>
>  Hello,
>
> I have developed a dissector plug-in for Pro-MPEG Code of Practice #3
> release 2 FEC data (
> http://www.pro-mpeg.org/publications/pdf/Vid-on-IP-CoP3-r2.pdf). This
> protocol is for sending FEC data over RTP.
>
> The protocol defines that this data is always sent with RTP payload type
> 96 (0x60). My plug-in currently recognizes all RTP traffic with payload type
> 96 as belonging to this protocol. However, payload type 96 is specified by
> RTP as dynamic and may be used for other purposes within other protocols. I
> don't want to issue my plug-in and then find that data of type 96 that is
> not Pro-MPEG FEC is then dissected as such.
>
> Please could somebody suggest the a mechanism for dealing with this
> problem?
>
> Thanks,
>
> Mark
>
>
>
> _______________________________________________
> Ethereal-dev mailing list
> [email protected]
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
>

_______________________________________________
Ethereal-dev mailing list
[email protected]
http://www.ethereal.com/mailman/listinfo/ethereal-dev