ignatberesnev/kdiameter

Open-source Java-compatible Diameter (RFC 6733) mappers

kdiameter's Issues

Diameter packet parser

Decode and encode diameter packets. Full packet format MUST be supported.

DiameterMessage class must not contain any business logic and should be responsible solely for encoding/decoding diameter messages.

Write unit tests using a real tcp dump

Expand AvpData mappings

AvpData consists of multiple methods that convert received raw bytes to a predefined type, such as int, String, etc.

Right now it supports only String and Int, but we should support AT LEAST the types defined in Base Protocol

• Integer32
• Integer64 (?)
• Unsigned32 (Long)
• Unsigned64 (?)
• Float32 (Float)
• Float64 (Double)

As well as common derived avp formats

• Address (InetAddress)
• Time (Java 8 time API)
• DiameterIdentity
• Enumerated
• IPFilterRule

Each one MUST have at least one test that checks the validity of mapping. Also, we'll need tests for existing methods: asString, asInt and asGroupedAvps.

Implement avp dictionary.xml parser

• Supported format should be the same as provided by wireshark
• Extendable
• Allow adding custom AVPs (both from code and from multiple xmls)
• Support for same avpCode but with different vendors. Think it through

Better real diameter dump for unit tests

At the moment tests for message encoding/decoding use a a real CER dump

A good start, but it's too simple to cover all of the encoding/decoding functionality. It lacks grouped AVPs, most flags are set to false, has very basic avp data (int and string), etc.

Unfortunately, that was the only real diameter dump at hand. We need to get a dump with a more complicated (diverse) message, and use it in the tests instead.

If anyone can provide such a dump, that'd be half the issue solved :) Just make sure it contains no private information (i.e your company name, clients, etc)