Re: [Dime] DiME ERP - Getting the message flows right
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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, 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.

Best regards,
Sebastien.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.