- The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter is also intended to work in
both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations.
XXX - add a brief description of PROTO history
- ["TCP"]: Typically, DIAMETER uses ["TCP"] as its transport protocol. The well known TCP port for DIAMETER traffic is 3868.
- ["SCTP"]: Typically, DIAMETER uses ["SCTP"] as its transport protocol. The well known SCTP port for DIAMETER traffic is 3868.
XXX - Add example traffic here (as plain text or Ethereal screenshot).
The DIAMETER dissector is fully functional, DIAMETER uses internal value strings to display AVP names etc or if LIBXML is present on the system a XML dictionary which is located in the Diameter folder, the XML library is out of date.
(XXX add links to preference settings affecting how PROTO is dissected).
Example capture file
XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically.
A complete list of PROTO display filter fields can be found in the [http://www.ethereal.com/docs/dfref/PROTO/PROTO.html display filter reference]
Show only the PROTO based traffic:
You cannot directly filter PROTO protocols while capturing. However, if you know the ["TCP"] port used (see above), you can filter on that one.
[http://www.ietf.org/rfc/rfc3588.txt?number=3588 Diameter Base Protocol RFC3588]