Subject: [AAA-WG]: NASREQ14: Problem with Acct-Session-Id and Session-Id

From: Avi Lior <[email-masked]>
Date: Fri, 20 Feb 2004 14:14:20 -0500

Problem with Acct-Session-Id and Session-Id

Submitter name: Avi Lior 
Submitter email address: [email-masked] 
Date first submitted: February 20th 2004
Reference: 
Document: NASREQ-14
Comment type: Technical 
Priority: S
Section: 9.2
Rationale/Explanation of issue:

When the corresponding response is received by the Translation Agent, it
says that
Acct-Session-Id attribute is to be placed in Session-Id.

The problem is that Acct-Session-Id will always change when there are
multiple session in RADIUS.
In diameter Session-Id remains constant and therefore placing it in
Session-Id will violate Diameter.

What really needs to happen is much more complex.

Requested changes: 

Acct-Session-Id attribute should be placed in Accounting-Sub-Session-Id AVP.

The Translation Agent should be the one generating a Session-Id for the
session and its sub-sessions.

It will place Session-Id in the diameter messages.