RFC 3588:Diameter Base Protocol
RFC-Ref

Delivery


Click on the red underlined text to get to the source

... base protocol provides the following facilities: - Delivery of AVPs (attribute value pairs) ...


... re-auth or STR message fails due to a delivery problem, the Diameter client ...
... SERVICE 0 If either the re-auth or the STR message delivery fails, terminate service with the user, and do not attempt any subsequent attempts. ...
... TRY_AGAIN 1 If either the re-auth or the STR message delivery fails, resend the failed message without the Destination-Host AVP ...
... ALLOW_SERVICE 2 If re-auth message delivery fails, assume that re-authorization succeeded. If STR ...
... authorization succeeded. If STR message delivery fails, terminate the session. ...
... SERVICE 3 If either the re-auth or the STR message delivery fails, resend the failed message without the Destination-Host AVP ...
... Destination-Host AVP present. If the second delivery fails for re-auth, assume re-authorization succeeded. If the second delivery ...
... delivery fails for re-auth, assume re-authorization succeeded. If the second delivery fails for STR, terminate the session ...


... accounting protocol is based on a server directed model with capabilities for real-time delivery of accounting information. Several fault resilience methods ...
... client MUST overwrite any previous interim accounting records that are locally stored for delivery, if a new record is being generated for the same session. This ensures that only one ...



Google
Web
RFC-Ref