: Failover mechanism in DCCA

Hi all,

Apologies if this has been discussed already.

 From Section 5.7 Failure Procedures, seems to imply that DCCA client is 
managing failover to secondary servers and sometimes interpreting the 
protocol errors like DIAMETER_UNABLE_TO_DELIVER or DIAMETER_TOO_BUSY. 
These, I understand are more of BASE protocol functionalities and should 
be transparent to DCCA client. (Assuming DCCA would be layered on BASE)

In scenarios where DCCA client talking to Agents, and an Agent could be 
serving the requests for a particular realm 3 hops away, do we need to 
start all over again to try the alternate secondary server which could 
have been reached from the same Agent ? Further, how would the DCCA 
client know which is the alternate server that needs to be tried ?

As far as I see, DCCA should include Dest-Host AVP for the subsequent 
requests after initial CCA received *IF* failover_is_not_supported else 
it shouldn't include this AVP so that the BASE/Agents can do a failover 
to other servers in a given realm.

But, with the above approach it is not guaranteed that we always try the 
server which replied with initial CCA before failing over to the other 
alternate servers.

Regards,
~sumanth