Wireshark-bugs: [Wireshark-bugs] [Bug 1494] Diameter dissector : the applicationID isn' t taken
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1494
LEGO <luis.ontanon@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Wireshark |TShark
OS/Version|Windows XP |All
Platform|PC |All
Version|0.99.5 |0.99.8
--- Comment #2 from LEGO <luis.ontanon@xxxxxxxxx> 2008-01-31 22:34:47 GMT ---
When I read the RFCs I did not find any explicit citation about if the same AVP
id can be treated differently by different applications. Then I read an IETF
draft [1] for the diameter dictionary API and the application-Id was not taken
into account when resolving an AVP. So I took it as good and (lazily) did not
take that into account.
What can be done is to add an 'application-id' attribute to the 'avp' entities
for the AVP dictionary so that conflicting avp-ids for different appIds can be
uniquely resolved.
But I wonder if it is realy worthwhile?
On the end I wrote a C (lex) parser to read the dictionary in run-time instead
of a compile-time perl parser that generates (much faster) C code from the
dictionary exactly to allow users to edit the dictionaries themselves.
[1] http://www.wireshark.org/lists/wireshark-dev/200707/msg00186.html
Luis
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
