Changes between Version 3 and Version 4 of Features
- Timestamp:
- Feb 25, 2011, 5:10:33 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Features
v3 v4 1 1 == Features == 2 2 3 The freeDiameter implementationsupports 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:3 The freeDiameter framework 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 rfc3588bis], including: 5 5 * Native IPv6 and SCTP support. 6 * TLS support (mixed port or separate port ), even for SCTP (RFC3436)7 * Failover and failback mechanisms6 * TLS support (mixed port or separate ports), even for SCTP (in RFC3436 flavour, DTLS is not supported yet, see [ticket:19]) 7 * Diameter failover and failback mechanisms 8 8 * Diameter routing loops detection and avoidance 9 9 * Base Accounting support is provided by the [wiki:app_acct.fdx] extension. 10 * Messages '''relaying''' is natively supported by the daemon without need for any extension.10 * Messages '''relaying''' is natively supported by the framework without need for any extension (unless you need complex routing rules). 11 11 * Diameter '''Redirects''' are supported by the [wiki:rt_redirect.fdx] and [wiki:app_redirect.fdx] extensions. 12 12 * '''Diameter EAP server''' (RFC4072) support is provided by the [wiki:app_diameap.fdx] extension. … … 14 14 * '''RADIUS/Diameter translation''' for NASREQ (RFC4005), EAP (RFC4072), and SIP (RFC4740) is provided by the [wiki:app_radgw.fdx] extension. 15 15 16 Since the implementation supports '''extensions''', it is quite easy to implement support for other Diameter applications or behavior (dynamic peer discovery, ...) 16 Many additional exciting extensions are in preparation right now... 17 17