Mercurial > hg > freeDiameter
view contrib/debian/control @ 1513:73e563165594
Add 3GPP TS 29.468 V15.8.0 (2019-12)
Add AVPs:
- BMSC-Address, Address, code 3500, section 6.4.2
- BMSC-Port, Unsigned32, code 3501, section 6.4.3
- Common-Tunnel-Endpoint-Identifier, OctetString, code 3524, section 6.4.26
- FEC-Request, OctetString, code 3525, section 6.4.27
- FEC-Result, Unsigned32, code 3531, section 6.4.33
- Local-M1-Information, Grouped, code 3518, section 6.4.20
- Local-MB2-U-Information, Grouped, code 3519, section 6.4.21
- MB2U-Security, Unsigned32, code 3517, section 6.4.19
- MBMS-Bearer-Event, Unsigned32, code 3502, section 6.4.4
- MBMS-Bearer-Event-Notification, Grouped, code 3503, section 6.4.5
- MBMS-Bearer-Request, Grouped, code 3504, section 6.4.6
- MBMS-Bearer-Response, Grouped, code 3505, section 6.4.7
- MBMS-Bearer-Result, Unsigned32, code 3506, section 6.4.8
- MBMS-eNB-IP-Multicast-Address, Address, code 3520, section 6.4.22
- MBMS-eNB-IPv6-Multicast-Address, Address, code 3521, section 6.4.23
- MBMS-GW-SSM-IP-Address-29.468, Address, code 3522, section 6.4.24
- MBMS-GW-SSM-IPv6-Address-29.468, Address, code 3523, section 6.4.25
- MBMS-Start-Time, Time, code 3507, section 6.4.9
- Radio-Frequency-29.468, Unsigned32, code 3508, section 6.4.10
- ROHC-Full-Header-Periodicity, Float32, code 3527, section 6.4.29
- ROHC-Max-CID, Unsigned32, code 3532, section 6.4.34
- ROHC-Profile, Unsigned32, code 3528, section 6.4.30
- ROHC-Request, Grouped, code 3526, section 6.4.28
- ROHC-Result, Unsigned32, code 3530, section 6.4.32
- TMGI-Allocation-Request, Grouped, code 3509, section 6.4.11
- TMGI-Allocation-Response, Grouped, code 3510, section 6.4.12
- TMGI-Allocation-Result, Unsigned32, code 3511, section 6.4.13
- TMGI-Deallocation-Request, Grouped, code 3512, section 6.4.14
- TMGI-Deallocation-Response, Grouped, code 3513, section 6.4.15
- TMGI-Deallocation-Result, Unsigned32, code 3514, section 6.4.16
- TMGI-Expiry, Grouped, code 3515, section 6.4.17
- TMGI-Number, Unsigned32, code 3516, section 6.4.18
- Userplane-Protocol-Result, Grouped, code 3529, section 6.4.31
Note: Name conflict with 3GPP TS 29.061 MBMS-GW-SSM-IP-Address (924).
3GPP TS 29.061 V10.4.0 (2011-09) CR 0355 added MBMS-GW-SSM-IP-Address (924).
3GPP TS 29.468 V14.0.0 (2016-12) CR 0021 added MBMS-GW-SSM-IP-Address (3522).
Fix: MBMS-GW-SSM-IP-Address (3522) renamed to MBMS-GW-SSM-IP-Address-29.468 (3522).
Note: Name conflict with 3GPP TS 29.061 MBMS-GW-SSM-IPv6-Address (925).
3GPP TS 29.061 V10.4.0 (2011-09) CR 0355 added MBMS-GW-SSM-IPv6-Address (925).
3GPP TS 29.468 V14.0.0 (2016-12) CR 0021 added MBMS-GW-SSM-IPv6-Address (3523).
Fix: MBMS-GW-SSM-IPv6-Address (3523) renamed to MBMS-GW-SSM-IPv6-Address-29.468 (3523).
Note: Name conflict with 3GPP TS 32.299 Radio-Frequency (3462).
3GPP TS 29.468 V12.0.0 (2014-09) added Radio-Frequency (3508).
3GPP TS 32.299 V13.1.0 (2015-06) CR 0638 added Radio-Frequency (3462).
Fix: Radio-Frequency (3508) renamed to Radio-Frequency-29.468 (3508).
author | Luke Mewburn <luke@mewburn.net> |
---|---|
date | Tue, 07 Apr 2020 19:38:33 +1000 |
parents | 9caedf4a058b |
children | 699c3fb0c57b |
line wrap: on
line source
Source: freediameter Section: contrib/net Priority: extra Maintainer: Sebastien Decugis <sdecugis@freediameter.net> Build-Depends: debhelper ( >= 7.3.9), cmake, make, gcc, g++, bison, flex, libsctp-dev, libgnutls-dev | gnutls-dev, libidn11-dev, libpq-dev, libmysqlclient-dev, libxml2-dev, swig, python-dev, libgcrypt11-dev | libgcrypt20-dev Standards-Version: 3.8.3 Homepage: http://www.freediameter.net Package: freediameter-common Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: The freeDiameter libraries. This package contains the freeDiameter framework core libraries, required by all freeDiameter components. It may also be useful for other projects which need to perform operations on Diameter messages. . The freeDiameter framework provides support for the Diameter Base Protocol. Without any extension, the framework can only be used as a Diameter routing agent. You probably want to install some freeDiameter extension(s) to extend its features, and also the freediameter-daemon package that will initialize the framework for you. . See 'freeDiameter-dev' package to retrieve the API for the library. Package: freediameter-dev Architecture: any Section: contrib/devel Depends: freediameter-common (= ${binary:Version}), libsctp-dev, libgnutls-dev, libgcrypt-dev Description: This package provides the development files for freeDiameter. Package: freediameter-daemon Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends}, freediameter-common (= ${binary:Version}) Suggests: ssl-cert, freediameter-dictionary-rfc4005, freediameter-dictionary-rfc4072, freediameter-dictionary-rfc4740, freediameter-dictionary-mip6, freediameter-dictionary-legacy Description: The freeDiameter daemon. This daemon is a simple loader for the freeDiameter framework. It is shipped with a small set of extensions, for example to configure the routing behavior. See the examples in /usr/share/freediameter* for more details. Package: freediameter-debug-tools Architecture: any Section: contrib/debug Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}) Suggests: python, libmysqlclient16 | libmysqlclient18 Description: freeDiameter debug tools. This package provides useful tools to help tracking problems in freeDiameter installation. For example, the dbg_interactive.fdx extension allows access to the framework via a python interpreter console. Package: freediameter-dictionary-rfc4005 Architecture: any Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}) Description: RFC4005 (NASREQ) dictionary support. This freeDiameter extension provides the dictionary support for commands and AVP defined in RFC4005 (NASREQ). . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension does not require a configuration file. Package: freediameter-dictionary-rfc4006 Architecture: any Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}) Description: RFC4006 (DCCA) dictionary support (incomplete). This freeDiameter extension provides the dictionary support for commands and AVP defined in RFC4006 (DCCA). . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension does not require a configuration file. . Currently this extension is not complete: only AVP definitions are included. See the source file for more details. Package: freediameter-dictionary-rfc4072 Architecture: any Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}), freediameter-dictionary-rfc4005 (= ${binary:Version}) Description: RFC4072 (Diameter EAP) dictionary support. This freeDiameter extension provides the dictionary support for commands and AVP defined in RFC4072 (Diameter EAP). . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension does not require a configuration file. Package: freediameter-dictionary-rfc4740 Architecture: any Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}) Description: RFC4740 (Diameter SIP) dictionary support. This freeDiameter extension provides the dictionary support for commands and AVP defined in RFC4740 (Diameter SIP). . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension does not require a configuration file. Package: freediameter-dictionary-mip6 Architecture: any Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}) Description: Diameter Mobile IPv6 application dictionary support. This package contains a set of extensions to provide the support for commands and AVP defined in several RFCs related to Diameter MIPv6. It is split is several extensions: mip6a, mip6i, nas-mipv6, rfc5777. . In order to use these extensions, your main freeDiameter configuration file must contain LoadExtension directives. See freeDiameter documentation for more details. . These extensions do not require a configuration file. Package: freediameter-dictionary-legacy Architecture: any Depends: ${misc:Depends}, freediameter-common (= ${binary:Version}), libxml2 Description: Legacy XML dictionary files support. This freeDiameter extension allows the use of XML dictionary files with the freeDiameter framework. Please note that dictionaries provided as XML files come with less features than native binary format, so the later should be preferred when possible. . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension requires a configuration file. See dict_legacy_xml.conf.sample for documentation. Package: freediameter-radius-gateway Architecture: any Depends: ${misc:Depends}, freediameter-daemon (= ${binary:Version}) Suggests: freediameter-dictionary-rfc4072 (= ${binary:Version}), freediameter-dictionary-rfc4740 (= ${binary:Version}) Description: RADIUS/Diameter extensible gateway. This freeDiameter extension implements a RADIUS to Diameter gateway. It allows a RADIUS client to connect to a Diameter server. . The support for specific Diameter applications and/or RADIUS extensions is provided in the gateway by the use of plugins. Currently, the following plugins are available: - echodrop.rgwx : drop or echo a RADIUS attribute. The attribute is not converted to Diameter. See echodrop.rgwx.conf.sample for details. - auth.rgwx : Convert Access-Request to Diameter AAR or DER. Requests For Comments: RADIUS: 2865, 3162, 2868, 2869, 3579; Diameter: 4005, 4072. Requires freediameter-dictionary-rfc4072. - sip.rgwx : Convert Access-Request to Diameter SIP messages. Requests For Comments: Diameter: 4740. Requires freediameter-dictionary-rfc4740. - acct.rgwx : Converts Accounting-Request (2866) to Diameter ACR (3588). Requires freediameter-dictionary-rfc4072. . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension requires a configuration file. See app_radgw.conf.sample for more details. Package: freediameter-accounting-server Architecture: any Depends: ${misc:Depends}, freediameter-daemon (= ${binary:Version}), libpq5 Suggests: freediameter-dictionary-rfc4072 Description: freeDiameter simple Accounting server. This freeDiameter extension implements the Diameter Base Accounting application. It saves the accounting records in a PostgreSQL database backend in a highly configurable maneer. . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension requires a configuration file. See app_acct.conf.sample for more details. . You may find some useful resources to parse the saved records in the contrib/app_acct_tools folder in source package. Package: freediameter-eap-server Architecture: any Depends: ${misc:Depends}, freediameter-daemon (= ${binary:Version}), libmysqlclient16 | libmysqlclient18, freediameter-dictionary-rfc4072 (= ${binary:Version}) Description: freeDiameter Diameter EAP server implementation. This freeDiameter extension implements a Diameter EAP server. It supports EAP-MD5 and EAP-TLS methods currently. . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension requires a configuration file. See app_diameap.conf.sample and http://diameap.yagami.freediameter.net for more details. Package: freediameter-sip-server Architecture: any Depends: ${misc:Depends}, freediameter-daemon (= ${binary:Version}), libmysqlclient16 | libmysqlclient18, freediameter-dictionary-rfc4740 (= ${binary:Version}) Description: freeDiameter Diameter SIP server implementation. This freeDiameter extension implements a prototype Diameter SIP server. See http://www.freediameter.net/trac/wiki/app_sip.fdx for status information. . In order to use this extension, your main freeDiameter configuration file must contain a LoadExtension directive. See freeDiameter documentation for more details. . This extension requires a configuration file. See app_sip.conf.sample for more details.