| 1 | == Features == |
| 2 | |
| 3 | The freeDiameter implementation supports the following features: |
| 4 | * Full support for the '''Diameter Base Protocol''' defined in RFC3588 and [http://tools.ietf.org/html/draft-ietf-dime-rfc3588bis-21 draft-ietf-dime-rfc3588bis-21], including: |
| 5 | * Native IPv6 and SCTP support. |
| 6 | * TLS support (mixed port or separate port), even for SCTP (RFC3436) |
| 7 | * Failover and failback mechanisms |
| 8 | * Diameter routing loops detection and avoidance |
| 9 | * Base Accounting support is provided by the [wiki:app_acct.fdx] extension. |
| 10 | * '''Diameter EAP server''' (RFC4072) support is provided by the [wiki:app_diameap.fdx] extension. |
| 11 | * '''Diameter SIP''' (RFC4740) support is provided by the [wiki:app_sip.fdx] extension. |
| 12 | * '''RADIUS/Diameter translation''' for NASREQ (RFC4005), EAP (RFC4072), and SIP (RFC4740) is provided by the [wiki:app_radgw.fdx] extension. |
| 13 | |
| 14 | Since the implementation supports '''extensions''', it is quite easy to implement support for other Diameter applications or behavior (dynamic peer discovery, ...) |
| 15 | |