Hi,
1)
I have checked in the file any one who uses CC AVP:s could add the missing
ones.
2) Not sure, but if it causes problems it can always be removed.
Brg
Anders
P:S If you do find the time we'd appreciate a complete list of the AVP:s
-----Ursprungligt meddelande-----
Från: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] För Thomas Steffen
Skickat: den 30 november 2005 14:11
Till: Ethereal development
Ämne: [Ethereal-dev] Dissection of Diameter Credit Control Application
Dear Ethereal developers and users
I am working with the Diameter Credit Control Application (RFC4006 and
several 3GPP standards). Due to the data driver structure of the
Diameter dissector, I was able to add this (sub-)protocol without any
coding (good job!).
I assume that this would be useful for other users, too, so I would
like to get it into subversion, but I have two questions:
1. I have not defined all AVPs given in the protocol, but only the
ones that I need. I am not sure whether I will have time to complete
it, and I don't have any opportunity to test the missing AVPs. Is that
a problem? Maybe someone could help out here.
2. The Service-Parameter-Info AVP is defined for vendor specific
applications. I such a vendor specific extension. Would it be
acceptable to include the enum values based on this extension? There
is basically no chance of a conflict, so it should not hurt any other
application.
I have attached my XML definition below. If you want to use it, you
have to copy it into /usr/share/ethereal/diameter/, and included it
from the main XML document diameter.xml using an entity.
If the definition is ok, I can send a patch for integration.
Thomas