Skip to content

RFC 6733 — Diameter Base Protocol⚓︎

Specification: IETF RFC 6733 · Network: 4G, 5G · Applies to: MME, HSS · Interfaces: S6a, S13

The assessed implementations declare compatibility with RFC 3588; RFC 6733 obsoletes it without changing the assessed behaviour.

Mandatory items: 72, of which 72 supported. A further 95 clauses of the specification carry no conformance requirement and are not listed.

Mandatory items⚓︎

Ref. Item Status Support Remarks
2.1 Transport Mandatory Supported
2.1.1 SCTP Guidelines Mandatory Supported
2.4 Application Identifiers Mandatory Supported
2.6 Peer Table Mandatory Supported
3.0 Diameter Header Mandatory Supported
3.2 Command Code ABNF specification Mandatory Supported
4.1 AVP Header Mandatory Supported
4.1.1 Optional Header Elements Mandatory Supported
4.2 Basic AVP Data Formats Mandatory Supported Applicable ones are supported
5.0 Diameter Peers Mandatory Supported
5.1 Peer Connections Mandatory Supported
5.3 Capabilities Exchange Mandatory Supported
5.3.1 Capabilities-Exchange-Request Mandatory Supported
5.3.2 Capabilities-Exchange-Answer Mandatory Supported
5.3.3 Vendor-Id AVP Mandatory Supported
5.3.5 Host-IP-Address AVP Mandatory Supported
5.4 Disconnecting Peer Connections Mandatory Supported
5.4.1 Disconnect-Peer-Request Mandatory Supported
5.4.2 Disconnect-Peer-Answer Mandatory Supported
5.4.3 Disconnect-Cause AVP Mandatory Supported
5.5 Transport Failure Detection Mandatory Supported
5.5.1 Device-Watchdog-Request Mandatory Supported
5.5.2 Device-Watchdog-Answer Mandatory Supported
5.5.3 Transport Failure Algorithm Mandatory Supported
5.5.4 Failover and Failback Procedures Mandatory Supported
5.6 Peer State Machine Mandatory Supported
5.6.1 Incoming connections Mandatory Supported
5.6.2 Events Mandatory Supported
5.6.3 Actions Mandatory Supported
5.6.4 The Election Process Mandatory Supported
6.0 Diameter Message Processing Mandatory Supported
6.1 Diameter Request Routing Overview Mandatory Supported
6.1.1 Originating a Request Mandatory Supported
6.1.2 Sending a Request Mandatory Supported
6.1.3 Receiving Requests Mandatory Supported
6.1.4 Processing Local Requests Mandatory Supported
6.1.5 Request Forwarding Mandatory Supported
6.1.6 Request Routing Mandatory Supported
6.1.7 Redirecting Requests Mandatory Supported
6.2 Diameter Answer Processing Mandatory Supported
6.2.1 Processing Received Answers Mandatory Supported
6.3 Origin-Host AVP Mandatory Supported
6.4 Origin-Realm AVP Mandatory Supported
6.5 Destination-Host AVP Mandatory Supported
6.6 Destination-Realm AVP Mandatory Supported
6.7 Routing AVPs Mandatory Supported
6.7.1 Route-Record AVP Mandatory Supported
6.8 Auth-Application-Id AVP Mandatory Supported
6.9 Acct-Application-Id AVP Mandatory Supported
6.11 Vendor-Specific-Application-Id AVP Mandatory Supported
6.12 Redirect-Host AVP Mandatory Supported
6.13 Redirect-Host-Usage AVP Mandatory Supported
6.14 Redirect-Max-Cache-Time AVP Mandatory Supported
6.15 E2E-Sequence AVP Mandatory Supported
7.0 Error Handling Mandatory Supported
7.1 Result-Code AVP Mandatory Supported
7.1.3 Protocol Errors Mandatory Supported
7.1.4 Transient Failures Mandatory Supported
7.2 Error Bit Mandatory Supported
8.0 Diameter User Sessions Mandatory Supported
8.3 Server-Initiated Re-Auth Mandatory Supported
8.5 Aborting a Session Mandatory Supported
8.6 Inferring Session Termination from Origin-State-Id Mandatory Supported
8.8 Session-Id AVP Mandatory Supported
8.11 Auth-Session-State AVP Mandatory Supported
8.14 User-Name AVP Mandatory Supported
8.15 Termination-Cause AVP Mandatory Supported
8.16 Origin-State-Id AVP Mandatory Supported
11.4.1 Result-Code AVP Values Mandatory Supported
11.4.3 Termination-Cause AVP Values Mandatory Supported
11.4.4 Redirect-Host-Usage AVP Values Mandatory Supported
11.5 Diameter TCP/SCTP Port Numbers Mandatory Supported

Optional items⚓︎

The specification leaves these 23 items to the implementation; 4 are supported or partially supported. An item marked Not applicable belongs to an area the platform does not provide, named in the Support column. Expand for the full list.

23 optional items
Ref. Item Support Remarks
2.2 Securing Diameter Messages Not supported
2.7 Realm-Based Routing Table Supported Using static configuration.
4.3 Derived AVP Data Formats Supported
5.2 Diameter Peer Discovery Not supported Peers are statically configured; dynamic peer discovery is not used.
5.3.4 Firmware-Revision AVP Not supported
5.3.6 Supported-Vendor-Id AVP Not supported
5.3.7 Product-Name AVP Not supported
7.1.1 Informational Not supported
7.1.2 Success Supported
7.1.5 Permanent Failures Not supported
7.3 Error-Message AVP Not supported
7.4 Error-Reporting-Host AVP Not supported
7.5 Failed-AVP AVP Not supported
7.6 Experimental-Result AVP Not supported
7.7 Experimental-Result-Code AVP Not supported
8.1 Authorization Session State Machine Not supported
8.7 Auth-Request-Type AVP Not supported
8.9 Authorization-Lifetime AVP Not supported
8.10 Auth-Grace-Period AVP Not supported
8.13 Session-Timeout AVP Supported
8.18 Session-Server-Failover AVP Not supported
8.19 Multi-Round-Time-Out AVP Not supported
8.21 Event-Timestamp AVP Not supported

Assessed 2026-09-15 against RFC 6733.