[Dime] Clarification regarding Diameter as Stateless Server and its state Machine implementation

[Bharath Meduri <[e-mail]>]

Hi Team,

          We are using Diameter stack in stateless Server Mode , and stuck with few RFC points for a Server initiated RAR .

The Stateless Server FSM State machine as per RFC 6733 Section  8.1 Authorization Session State Machine is defined below as

[cid:0a45f6db-fb66-4bb3-b227-a5c90f699a25]

and in Same Section:
=================
When a session is moved to the Idle state, any resources that were allocated for the particular session must be released.
Any event not listed in the state machines MUST be considered an error condition,  and an answer, if applicable, MUST be returned to the originator of the message.

-------> Is this means that Stateless Server cannot initiate RAR??

So we have a Case where Stateless Server should initiate a RAR and this has been failing when There is Open Session for Same Session ID pending to be responded.

Ex:


























[cid:ed9c0004-e2a2-4602-bbd9-cbb5d868f627]

But the same works Stack forwards RAR when there is no Open AAR Session
[cid:61ec0189-6a3c-488d-b126-0de4eb43f5ae]


So, Can please someone help to explain if this behavior is correct that in stateless Server mode The Diameter can Drop RAR ?
 Our expectation is that Since only state defined in RFC is  IDLE State it should be able to send RAR . And in Our case this RAR is required for Location details Updating to AF in case of 3gpp.

Thanks&Rgs
Bharath M
________________________________
This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to [e-mail]. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects. Thank You