Mercurial > hg > freeDiameter
view README @ 1517:9e233ef0b07e
Add 3GPP TS 29.283 V15.1.0 (2019-09)
Add AVPs:
- MCPTT-ID, UTF8String, code 4500, section 7.3.2
- Data-Identification, Grouped, code 4501, section 7.3.3
- Data-Identification-Prefix, Unsigned32, code 4502, section 7.3.11
- Data-Identification-Flags, Unsigned64, code 4503, section 7.3.12
- DPR-Flags, Unsigned32, code 4504, section 7.3.13
- DPA-Flags, Unsigned32, code 4505, section 7.3.14
- DUR-Flags, Unsigned32, code 4506, section 7.3.15
- DUA-Flags, Unsigned32, code 4507, section 7.3.16
- NDR-Flags, Unsigned32, code 4508, section 7.3.17
- NDA-Flags, Unsigned32, code 4509, section 7.3.18
- User-Data-Id, Unsigned32, code 4510, section 7.3.19
- MC-Service-User-Profile-Data, Grouped, code 4511, section 7.3.20
- Sequence-Number-29.283, Unsigned32, code 4512, section 7.3.21
- Data, Grouped, code 4513, section 7.3.22
- MCVideo-ID, UTF8String, code 4514, section 7.3.24
- MCData-ID, UTF8String, code 4515, section 7.3.25
Note: Name conflict with 3GPP TS 29.140 Sequence-Number (1107).
and 3GPP TS 29.329 Sequence-Number (716).
3GPP TS 29.140 V6.1.0 (2005-06) allocated Sequence-Number (1107).
3GPP TS 29.329 V10.0.0 (2010-09) CR 0163 added Sequence-Number (716).
3GPP TS 29.283 V13.1.0 (2016-06) allocated Sequence-Number (4512).
Fix: Sequence-Number (4512) renamed to Sequence-Number-29.283 (4512).
| author | Luke Mewburn <luke@mewburn.net> |
|---|---|
| date | Thu, 09 Apr 2020 10:32:09 +1000 |
| parents | ce3cacbbccc9 |
| children |
line wrap: on
line source
freeDiameter is an implementation of the Diameter protocol. Diameter is a protocol designed to carry Authentication, Authorization and Accounting (AAA) payload. It is an evolution of the RADIUS protocol (as the name suggests). Diameter is an extensible protocol. RFC3588 (currently under revision) defines the Base Protocol that all Diameter nodes must support, while other documents define the additional protocol support for specific applications. Such applications include for example Network Access Servers (RFC4005), EAP (RFC4072), ... The implementation consists in several components: - libfdproto : this shared library provides the functions to manipulate Diameter messages and dictionary. This library is meant to be re-used by other projects that would require parsing or manipulating Diameter messages. - libfdcore : this shared library contains the core of the framework. It establishes the network connections with other Diameter peers and performs the tasks described in Diameter Base Protocol, such as watchdogs, basic routing, ... It also handles the loading of extensions (see below). - freeDiameterd : this simple daemon parses the command line and initializes the freeDiameter framework. Use it for your Diameter server & agent components. In case of Diameter clients, you probably will prefer linking the libfdcore directly with your client application that must be made Diameter-aware. - extensions : the extensions provide the mean to augment the features of the freeDiameterd framework. Extensions can provide the handling of a Diameter server application, but also advanced routing features, peer management, etc. See http://www.freediameter.net/ for more information on the project. freeDiameter was previously known as the "waaad" project (WIDE AAA Daemon) This project is not related to the "freediameter" project from Sun on sourceforge. Author: Sebastien Decugis. See LICENSE file for legal information on this software. See INSTALL for information on building and using this software.