diff options
author | Anders Svensson <[email protected]> | 2014-05-23 11:51:25 +0200 |
---|---|---|
committer | Anders Svensson <[email protected]> | 2014-05-26 13:52:05 +0200 |
commit | df19c2724e985daed4ee56abeedca779d20bd194 (patch) | |
tree | 516a2f51b1f78e59b8a52fbb94c5bb6fb6dfe999 /lib/diameter/bin | |
parent | 0058430352420a8c0dc053900f108e7086f52fad (diff) | |
download | otp-df19c2724e985daed4ee56abeedca779d20bd194.tar.gz otp-df19c2724e985daed4ee56abeedca779d20bd194.tar.bz2 otp-df19c2724e985daed4ee56abeedca779d20bd194.zip |
Don't count messages on arbitrary keys
That is, don't use a key constructed from an incoming Diameter header
unless the message is known to the dictionary in question. Otherwise
there are 2^32 application ids, 2^24 command codes, and 2 R-bits for an
ill-willed peer to choose from, each resulting in new keys in the
counter table (diameter_stats).
The usual {ApplicationId, CommandCode, Rbit} in a key is replaced by the
atom 'unknown' if the message in question is unknown to the decoding
dictionary.
Counters for messages sent and received by a relay are (still) not
implemented.
Diffstat (limited to 'lib/diameter/bin')
0 files changed, 0 insertions, 0 deletions