Subject: [Mip4] [Issue 21] MN-AAA extension not considered in FA to HA forwarding rules

From: "Charles E. Perkins" <[email-masked]>
Date: Wed, 28 Jan 2004 13:59:53 -0800

Hello folks,

Please refer to previous discussion at the following URL:
        http://www.mip4.org/issues/tracker/mip4/issue21
as necessary.

The problem with this text results from the
previous change to Mobile IP whereby registrations
can be authorized by including alternative
"authorization-enabling" extensions, for instance
the "MN-AAA Authentication" extension.  I fixed
this by rewording the bullet item as suggested at
the working group meeting.

OLD:
      -  It MUST process and remove any Extensions following the
         Mobile-Home Authentication Extension,
NEW:
      -  It MUST process and remove any Extensions which do not  
         precede any authorization-enabling extension.

I _think_ this also takes care of the case where a
foreign agent doesn't recognize the authorization-enabling
extension.  Perhaps we should designate new Extension
with subtypes that would take care of all future
authentication-enabling extensions.  That would be
the clearest resolution of this problem.

Comments?

Regards,
Charlie P.

-- 
Mip4 mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/mip4