Wireshark-bugs: [Wireshark-bugs] [Bug 8691] Adding support of BGP flow spec RFC 5575
Comment # 32
on bug 8691
from Matt Texier
Hi Michael,
I concur on your two comments:
- I will change the "tag" stuff to make it cleaner,
- I was very balanced between adding info to the parent tree vs let the user
open child tree. I tried to find the best compromise. RFC 5575 allows to
propagate ACL via BGP, as such, there is quiet a lot of information to be
displayed to make it readable for the user. Over the time, MP BGP has become a
transport for many things (a bit too much things maybe). RFC 5575 allows to
propagate filters at L3/4 via a dynamic protocol. L4 informations could be a
port or ranges of ports associated with an operator (equal, greater than, lower
then, ...). I did append to parent tree a short coding of the filter using "<="
"=" or ">=" and the decimal value. It could happen that there is more than one
operator and decimal value. The good thing is that, in practice, operational
people are not using complex filters via BGP flow spec and as such we should
not have large amount of data in the parent tree.
I can change those "append's" ; it doesn't fundamentally change the dissector
... My intention was just to make it more easy to read for the end user. I will
follow you advices on this.
Just let me know.
Thanks Matt.
You are receiving this mail because:
- You are watching all bug changes.
