view README @ 1488:431ad99c39fe

Add 3GPP TS 29.273 V15.4.0 (2019-09) Add AVPs from 3GPP TS 29.273: - 3GPP-AAA-Server-Name, DiameterIdentity, code 318, section 8.2.3.24 - Non-3GPP-User-Data, Grouped, code 1500, section 8.2.3.1 - Non-3GPP-IP-Access, Enumerated, code 1501, section 8.2.3.3 - Non-3GPP-IP-Access-APN, Enumerated, code 1502, section 8.2.3.4 - AN-Trusted, Enumerated, code 1503, section 5.2.3.9 - ANID, UTF8String, code 1504, section 5.2.3.7 - Trace-Info, Grouped, code 1505, section 8.2.3.1.3 - MIP-FA-RK, OctetString, code 1506, section 5.2.3.12 - MIP-FA-RK-SPI, Unsigned32, code 1507, section 5.2.3.13 - PPR-Flags, Unsigned32, code 1508, section 8.2.3.17 - WLAN-Identifier, Grouped, code 1509, section 5.2.3.18 - TWAN-Access-Info, Grouped, code 1510, section 8.2.3.19 - Access-Authorization-Flags, Unsigned32, code 1511, section 8.2.3.20 - TWAN-Default-APN-Context-Id, Unsigned32, code 1512, section 8.2.3.18 - Full-Network-Name, OctetString, code 1516, section 5.2.3.14 - Short-Network-Name, OctetString, code 1517, section 5.2.3.15 - AAA-Failure-Indication, Unsigned32, code 1518, section 8.2.3.21 - Transport-Access-Type, Enumerated, code 1519, section 5.2.3.19 - DER-Flags, Unsigned32, code 1520, section 5.2.3.20 - DEA-Flags, Unsigned32, code 1521, section 5.2.3.21 - RAR-Flags, Unsigned32, code 1522, section 9.2.3.1.5 - DER-S6b-Flags, Unsigned32, code 1523, section 9.2.3.7 - SSID, UTF8String, code 1524, section 5.2.3.22 - HESSID, UTF8String, code 1525, section 5.2.3.23 - Access-Network-Info, Grouped, code 1526, section 5.2.3.24 - TWAN-Connection-Mode, Unsigned32, code 1527, section 5.2.3.25 - TWAN-Connectivity-Parameters, Grouped, code 1528, section 5.2.3.26 - Connectivity-Flags, Unsigned32, code 1529, section 5.2.3.27 - TWAN-PCO, OctetString, code 1530, section 5.2.3.28 - TWAG-CP-Address, Address, code 1531, section 5.2.3.29 - TWAG-UP-Address, UTF8String, code 1532, section 5.2.3.30 - TWAN-S2a-Failure-Cause, Unsigned32, code 1533, section 5.2.3.31 - SM-Back-Off-Timer, Unsigned32, code 1534, section 5.2.3.32 - WLCP-Key, OctetString, code 1535, section 5.2.3.33 - Origination-Time-Stamp, Unsigned64, code 1536, section 9.2.3.2.6 - Maximum-Wait-Time, Unsigned32, code 1537, section 9.2.3.2.7 - Emergency-Services, Unsigned32, code 1538, section 7.2.3.4 - AAR-Flags, Unsigned32, code 1539, section 7.2.3.5 - IMEI-Check-In-VPLMN-Result, Unsigned32, code 1540, section 5.2.3.35 - ERP-Authorization, Unsigned32, code 1541, section 8.2.3.27 Not adding Trust-Relationship-Update (1515) because that was only present in one published version: 3GPP TS 29.273 V11.3.0 (2012-09)
author Luke Mewburn <luke@mewburn.net>
date Fri, 27 Mar 2020 16:58:02 +1100
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.
"Welcome to our mercurial repository"