Mercurial > hg > freeDiameter
view README @ 1515:8430dabbc637
Add 3GPP TS 29.109 V15.0.0 (2017-06)
Add AVPs:
- GBA-UserSecSettings, OctetString, code 400, section 6.3.1.1
- Transaction-Identifier, OctetString, code 401, section 6.3.1.2
- NAF-Id, OctetString, code 402, section 6.3.1.3
- GAA-Service-Identifier, OctetString, code 403, section 6.3.1.4
- Key-ExpiryTime, Time, code 404, section 6.3.1.5
- ME-Key-Material, OctetString, code 405, section 6.3.1.6
- UICC-Key-Material, OctetString, code 406, section 6.3.1.7
- GBA-U-Awareness-Indicator, Enumerated, code 407, section 6.3.1.8
- BootstrapInfoCreationTime, Time, code 408, section 6.3.1.9
- GUSS-Timestamp, Time, code 409, section 6.3.1.10
- GBA-Type, Enumerated, code 410, section 6.3.1.11
- UE-Id, OctetString, code 411, section 6.3.1.12
- UE-Id-Type, Enumerated, code 412, section 6.3.1.13
- UICC-App-Label, OctetString, code 413, section 6.3.1.14
- UICC-ME, Enumerated, code 414, section 6.3.1.15
- Requested-Key-Lifetime, Time, code 415, section 6.3.1.16
- Private-Identity-Request, Enumerated, code 416, section 6.3.1.17
- GBA-Push-Info, OctetString, code 417, section 6.3.1.18
- NAF-SA-Identifier, OctetString, code 418, section 6.3.1.19
- Security-Feature-Request, OctetString, code 419, section 6.3.1.20
- Security-Feature-Response, OctetString, code 420, section 6.3.1.21
Note: 3GPP TS 29.109 table 6.1 row GBA_U-Awareness-Indicator (407)
has an underscore in the name (contrary to RFC 6733 section 4.1).
Fix: GBA_U-Awareness-Indicator (407) renamed to GBA-U-Awareness-Indicator (407).
| author | Luke Mewburn <luke@mewburn.net> |
|---|---|
| date | Thu, 09 Apr 2020 00:34:15 +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.