Re: [Dime] DiME ERP - Getting the message flows right

["Hannes Tschofenig" <Hannes.Tschofenig at gmx.net>]

Hi Sebastien, 

>Hi,
>
>Hannes Tschofenig a écrit :
>>   Diameter EAP +-------------+   Diameter EAP   +-------------+
>>                |             |                  |             |
>>  <------------>| Local       |<---------------->| Home        |
>>                | Diameter    |                  | Diameter    |
>>                | EAP Proxy   |                  | EAP Server  |
>>                |             |                  |             |
>>                +-------------+                  +-------------+
>>                       ^                                ^
>>                    (a)| proprietary        proprietary |(b)
>>                       v                                v
>>                +-------------+                  +-------------+
>>   Diameter ERP |             |    Diameter ERP  |             |
>>                | Local       |                  |  Home       |
>>  <------------>| Diameter    |<---------------->|  Diameter   |
>>                | ERP Server  |                  |  ERP Server |
>>                |             |                  |             |
>>                +-------------+                  +-------------+
>>
>> It might be useful to say what information is exchanged at 
>(a) and (b) 
>> and when in the protocol exchange.
>>   
>I agree with this figure -- I mean, it reflects my current 
>understanding of the architecture.
>In my understanding of Glen's explanation during Interim 
>Meeting, there would be a "HOKEY server" as a separate entity,

Separate logical entity. 
 
>and both the local Diameter EAP Proxy and ERP proxy talk to 
>this HOKEY server using this proprietary protocol (a).
>
>Note that the proprietary exchange (a) with EAP proxy is 
>necessary only for implicit bootstrapping, which as you know I 
>believe should be avoided.
Good that you mention this. I believe that this aspect should be described
as well. It could be covered in a description that illustrates the different
stages of the ERP messaging and the variations that exist together with the
information that actually needs to be made available to the ERP server. 

What is also important with respect to the message routing, which is not yet
covered in the current figures is that the Diameter EAP exchange is routed
based on that specific application ID and Diameter ERP would be routed on
this newly defined application ID. This is quite important to capture in
this discussion and the figure above captures this aspect in some fashion. 


Ciao
Hannes

>
>Best regards,
>Sebastien.
>