Re: [Dime] Diameter ERP

[Sebastien Decugis <sdecugis at nict.go.jp>]

Hi Qin, all,

> [Qin]: In the RFC4004, the Diameter user session and the Layer 3 mobility session associated 
> with MIP application are not the same thing,  and ERP may borrow the similar mechanism as  
> user session management described in the RFC 4004, therefore there is no conflict between ERP 
> and the MIP application.
>   
As I told before, I am not familiar with Diameter mobility applications,
so I don't know what we can/cannot do in Diameter ERP and which
conflicts we are exposing. I will have to read in depth the RFC4004
before I can really answer on this topic. In the meantime, it would be
interesting to hear from others who are familiar with Diameter MIP6 for
example ^^.

> [Qin]: It seems not efficient way for message routing. How about Redirection mechanism, i.e.,
> one EAP server possessing no EMSK can redirect the message to the EAP server possessing EMSK.
> It seems more efficient than the way you suggest.
>   
Agreed, but how does this server that does not have the EMSK learn which
server has it, to give the correct redirect indication ?

>> I believe a solution is to store the information about the server (that
>> is known during the initial EAP exchange) and then use this information
>> when ERP is started. But I am not sure in which location the information
>> should be stored, NAS or ER server...
>>     
>
> [Qin]: What I prefer is the information can be downloaded at the NAS. And then
> the peer can obtain this information directly or indirectly from the NAS.
>   
The peer does not need this information, only the NAS does. I agree that
keeping the information in the NAS is the easy and efficient solution,
but it does not work if we plan to support handovers :-) Hence the issue...

Best regards,
Sebastien.

-- 
Sebastien Decugis
Research fellow
Network Architecture Group
NICT (nict.go.jp)