Mercurial > hg > waaad
changeset 413:844f921713d5
Updated design notes for sessions
| author | Sebastien Decugis <sdecugis@nict.go.jp> |
|---|---|
| date | Mon, 15 Jun 2009 13:37:13 +0900 |
| parents | 2d1f1c6ae1cd |
| children | c7ce13cb7d23 |
| files | extensions/radius_gw/design.txt |
| diffstat | 1 files changed, 3 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/extensions/radius_gw/design.txt Mon Jun 15 13:35:01 2009 +0900 +++ b/extensions/radius_gw/design.txt Mon Jun 15 13:37:13 2009 +0900 @@ -30,7 +30,7 @@ - (eventually for later) An immediate RADIUS answer must be sent, without going to Diameter network. This can be used for example for fragmented RADIUS requests (not supported in initial version, may require change in the design...). - When all extensions have been called, the Diameter message is checked for consistency. If it is a valid message, - it is sent on the Diameter Network, and the RADIUS message is saved in the session. + it is sent on the Diameter Network, and the RADIUS message is saved until an answer is received. When the Diameter answer is received, the radius_gw retrieves the corresponding RADIUS request, then a similar process happens (extensions are the same as for the request). @@ -40,12 +40,12 @@ - RADIUS answer (to add attributes) - Diameter answer (with linked Diameter Request inside) - When all extensions have been called, the RADIUS answer is generated, with appropriate authenticator and all, and - sent to the RADIUS client. + sent to the RADIUS client. The session is deleted (radius gateways are stateless). *** About sessions *** The session is created the first time an Access-Request is received. -Then a State attribute in the form "Diameter/..." is used to store the information. +Then a State or Class attribute in the form "Diameter/..." is used to store the information. More details in http://tools.ietf.org/html/rfc4005#section-9