Instructions on the diagrams of Radius exchange

2010-01-28

Emin Gabrielyan→

→Oussama Hammami

→Nicolas Jorand

Please follow the example shown below for representing the experiences involving multiple nodes with authentication and accounting RADIUS packets sent to the billing. The packets must be retrieved from the billing log as well as all logged actions following the reception of each packet (in the same log). These log fragments must be separated and saved into different text files numbered according to the order they are received and logged. The connections shown on the diagram are clickable and point to the corresponding text file. The numbering shown in the example below can change depending on the order of reception in your own example. Use different colors for authentication, start, and stop types of RADIUS packets.

Document all your experiences in a public domain but remove from packets sensible info (such as passwords).

A call involving three nodes shall have 3 * 5 = 15 radius messages sent to the billing server. Please document all scenarios in which we are interested in order to completely expose the behavior of the billing on complete and incomplete sets of radius packets (possibly deferred in time).

[doc]

*  *  *