Recently I was trying to analyze some PIM traffic and noticed some
deficiencies with the PIM dissector. Most fields are non-filterable
because they've either been added using proto_tree_add_text() instead of
proto_tree_add_item(), or they haven't been added at all. A count
reveals 98 such instances of proto_tree_add_text(), so you have an idea
of some of the limitations of the dissector. Anyway, I am currently in
the process of modifying/enhancing this dissector as time permits, but
there will likely be quite a lot of changes made by the time I'm done.
So ...
Is it OK to submit one big patch once I'm done, or would the core
developers prefer smaller, more incremental patches? One patch would be
easier for me. Assuming that's OK, I would like to regression test it
as much as possible before submitting it. I have some PIM captures, but
could use some more. Ideally, I could get captures depicting all
message types and with all the different options, but I'll take what I
can get. If you have capture file(s) of PIM traffic, especially ones
that include lots of options, I would appreciate it if you could post
them for my testing.
Lastly, I am currently working off RFC's 4601 and 3973, but these RFC's
describe only PIMv2. I don't have any information whatsoever on PIMv1.
The PIM dissector gives the following link as a source of information
for PIMv1; however, the link no longer works:
http://www.mbone.de/training/Module3.pdf. Does anyone have information
on PIMv1? It looks to be very similar to PIMv2 except implemented under
IGMP; however none of the IGMP RFC's describe it. As indicated by
http://www.juniper.net/techpubs/software/junos/junos72/swconfig72-multic
ast/download/pim-intro.pdf, "In fact, no current RFC describes PIMv1 at
all: The drafts have all expired, and PIMv1 was never issued as an
official RFC."
Thanks,
Chris
CONFIDENTIALITY NOTICE: The contents of this email are confidential
and for the exclusive use of the intended recipient. If you receive this
email in error, please delete it from your system immediately and
notify us either by email, telephone or fax. You should not copy,
forward, or otherwise disclose the content of the email.
