|
> Perhaps you could suggest a better way to accomplish this? Maybe it's > really not needed: much more efficient to just wait till the server goes > away then retry a few times. I don't think there is a better way to accomplish this in RADIUS at this point. SIP, Diameter and HTTP all have a "redirect" error message. RADIUS does not. This means that the RADIUS accounting server either stores the accounting packet and returns an Accounting-Response, or it drops the packet, and then has to deal with a retry. Given this, about the best that can be done is for the server to process the Accounting-Request and then send whatever load shedding info it has in a VSA. If the NAS doesn't understand the VSA, then it will ignore it, and things will be no worse off than had the server not sent the VSA at all. > Excellent suggestion: it's not like the semantics of the CoA exchange bind > it to a specific session, while the Accounting-Response is a generic > accounting-related ACK. TheCoA-Request also requires the NAS (and Dynamic Authorization Client) to implement RFC 5176. |