[Dime] DiME ERP: new Application ID or not ? (non-roaming case)

[Julien Bournelle <julien.bournelle at gmail.com>]

Hi all,

 we try to solve the issue concerning the need for a new App-Id or not.

 The ERP protocol (RFC 5296) is to be used along with EAP. It basically
defines two new EAP codes and uses keying material derived from a first
EAP authentication.

 To start the discussion, let's take the non-roaming case.

 In non-roaming, we have first an EAP authentication using Diameter EAP.
 Then, for reauthentication using ERP, we have two messages (Request/Response)
 between NAS and the AAA/ERP server carrying EAP packets

 See (http://tools.ietf.org/html/rfc5296#page-6)

 So, either we reuse the Diameter EAP Application (DER/DEA) or we define
a new Diameter Application.

 If we use a new Diameter Application, a new Diameter session will be created
and eventually a new Diameter server will be reached. What bothers
me in this case is that we basically perform a reauthentication for the same
session which is primarly handled at the AAA/EAP server. So, i'm wondering
what happens concerning Authorization Lifetime session etc..

 Note that I still don't have strong opinion and I'll be glad to hear opinions
from others.

 Regards,

 Julien