top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Diameter: RAR Message with possible ReAuth-Reqiest_type

+3 votes
1,761 views

I am looking for a case where RE-AUTH-REQUEST is sent to NAS with subscriber credentials captured via web Portal (web-logon) case.

From RFC 6733, we do have two options set in REAUTH-REQUEST-TYPE AVP of the action expected. From my use-case standpoint, I would like to inform

NAS to take AUTHENTICATE_ONLY action by sending AA-Request for credential validation.

Since this is not specified as part of this RFC, do you see this needs to be addressed?

RE-AUTH-REQUEST-TYPE AVP
The Re-Auth-Request-Type AVP (AVP Code 285) is of type Enumerated and is included in application-specific auth answers to inform the client of the action expected upon expiration of the Authorization-Lifetime. If the answer message contains an Authorization-Lifetime AVP with a positive value, the Re-Auth-Request-Type AVP MUST be present in an answer message. The following values are defined:

AUTHORIZE_ONLY 0
An authorization only re-auth is expected upon expiration of the Authorization-Lifetime. This is the default value if the AVP is not present in answer messages that include the Authorization-Lifetime.

AUTHORIZE_AUTHENTICATE 1
An authentication and authorization re-auth is expected upon expiration of the Authorization-Lifetime.

posted Nov 23, 2013 by Jai Prakash

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes

In one Diameter blog, I saw a statement in which mentioned, if a Diameter node receive CER from unknown peer it responds back to that peer with Result-Code AVP set to "DIAMETER_UNKNOWN_PEER".
Now my query, Does a Diameter node keep its potential peers information in advance ?

+1 vote

I meant Can one PCRF with one RAR request can modify Default and Dedicated bearer ? If yes then what will happen if out of them one fails ? Do I have to send both modified parameters again?

0 votes

Is it possible that MCC MNC gets changed in the same Diameter session without changing session ID while in Roaming???
As I have come to across an unsupported scenario when some users are roaming in Iceland operator MCC MNC and suddenly switch to different operator MCC MNC which belongs to the USA within the same DCCA session i.e without closing the PDP context and opening a new one (that should not be possible, unsupported scenario). Is it possible??? I'm confused here.

...