Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -foreignagent failed authentication
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mip4] RFC 3344 - Home Agent Registration Code 132 -foreignagent failed authentication
Hi Ahmad. Yes, a similar remark was made in this thread already.
Anyways, just wanted to point out this issue is more applicable to MHAE.
Kent
-----Original Message-----
From: Ahmad Muhanna [mailto:amuhanna at nortel.com]
Sent: Friday, August 22, 2008 10:13 AM
To: Kent Leung (kleung); Charles E. Perkins; Mobile IPv4 Mailing List
Cc: George Tsirtsis; Acee Lindem
Subject: RE: [Mip4] RFC 3344 - Home Agent Registration Code 132
-foreignagent failed authentication
Hi Kent,
>
> Anyways, I'm not sure how my quoted comment was interpreted as a
> "MAY"?
> A response from the HA (when it has a FA-HA security
> association) to the FA has been userful in deployments.
> There isn't likely a DoS from FA.
[Ahmad]
Sure, any behaving node will not cause a DoS attack. The problem is from
an attacker claiming that it is an honest FA. I am not trying to open
this topic for discussion again, but I am strictly commenting on your
above statement.
Cheers!
Ahmad
>
> I think the more relevant issue is with the MN-HA authentication
> rejection. The current text contains:
>
--
Mip4 mailing list: Mip4 at ietf.org
Web interface: https://www.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.