Comment # 9
on bug 9569
from Alex Rodikov
(In reply to comment #7)
> Hm, I if understand correctly you don't plan to contribute newer version of
> TPNCP protocol dissector source to wireshark.
> If my understanding is correctly, could you explain why not?
>
> Thanks,
> Jakub.
It's correct. Audiocodes is not going to deliver any changes/updates of TPNCP
dissector source.
Why? - The TPNCP is not supported by Audiocodes as its "official" protocol
anymore. So, continue to maintenance of the wirishark source code is pointless.
On other hand, Audiocodes continue to use the protocol internally for debugging
and developing purpose (as dynamically loaded plugin dissector, or privet
compilations). Because backward/forward and product compatibility is not a
issue anymore there are many incompatible versions. Under this condition it
looks very hard to deliver new versions update into wireshark source.
You may say taking new protocol name is solution, it really might be, but it
is somewhat confusing to see two TPNCP protocols - we prefer to remove "legacy"
TPNCP.
I agree it looks like pure Audiocodes interest but there are some benefits for
wireshark users also - the startup time and memory consumption will improve
(remember we are speaking about non-supported proprietary protocol which is not
used by 99.9% of wireshark users) , you eliminate potential problems when
"legacy" TPNCP will try to dissect incompatible "new" TPNCP or an other
protocol that takes default TPNCP port.
Besides, the solution we propose doesn't remove the dissector completely -
enough simple file name change to restore the dissector functionality.
You are receiving this mail because:
- You are watching all bug changes.
