[Mip4] RE: [Dime] RE: Issue 3: Diameter MIP4 Application vs. RADIUSArchitecture
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Mip4] RE: [Dime] RE: Issue 3: Diameter MIP4 Application vs. RADIUSArchitecture
Alper Yegin wrote:
> Pete,
>> No, I don't. Putting the Registration Request in the AMR is a
>> feature. It allows the registration to happen in one round-trip.
>
> Obviously it is a feature. But don't you think it is a bit of a hack?
> I mean, tunneling one protocol inside another for the sake of saving
> round-trips? For example, we could further reduce the round-trips by
> tunneling MIP4 inside EAP of network access authentication.
I don't think it's a hack. When we have Mobile IP being used
for access authentication I think it makes sense to carry the
RRQ in a Diameter application. EAP is a different case because
then we have a separate protocol doing access authentication.
> I also understand that having to go to HAAA twice for each MIP RegReq
> is bothersome. But then, maybe we should re-consider the necessity of
> MN-FA authentication. Given that HA is going to authenticate the MN,
> does FA also need to do the same?
The FA and HA might be part of different administrative domains.
I think the FA has just as much reason to authenticate the MN as
the HA.
> Alper
-Pete
--
Mip4 mailing list: Mip4 at ietf.org
Web interface: https://www1.ietf.org/mailman/listinfo/mip4
Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.