RE: [Mip4] 3344bis clarification on identifying the FA's SA

Hi Fredrik.

Yes, unfortunately that would be the case when using the source IP
address for indexing the SA.

BTW, there were discussions of using FA NAI to identify the FA
for authentication.  This would allow one SA per FA.

Subject was "[Issue 45] RFC 3344 - FHAE issue when using
a   different careofaddress".

>At 01:03 PM 3/16/2004 -0800, Kent Leung wrote:
>Use of FA NAI sounds reasonable and generic FA identifier will
>come in handy for future features.

But this is outside the scope of 3344bis.  I'm seeking a clarification
in 3344bis.

Kent

At 08:46 AM 1/20/2005 +0100, Fredrik Johansson wrote:
>Kent,
>
>Just a thought, what happens when you have a FA with multiple interfaces
>that all utilize the same CoA? Do you have to have multiple SAs for what is
>basically one FA?
>
>/Fredrik
>
> > -----Original Message-----
> > From: mip4-bounces@ietf.org [mailto:mip4-bounces@ietf.org] On
> > Behalf Of Kent Leung
> > Sent: den 20 januari 2005 00:25
> > To: mip4@ietf.org
> > Subject: [Mip4] 3344bis clarification on identifying the FA's SA
> >
> > Hi.  I realized during our Deregistration/FHAE discussions
> > that we assumed that the FA's SA is indexed by the source IP
> > address of the RRQ on the HA.  But it's not explicitly clear
> > in RFC 3344 (going back to RFC 2002) that source IP address
> > is the method to identify the FA since CoA may also be used.
> >
> > So this leaves ambiguity in implementation and also
> > introduces deployment issues where the SA is configured based on CoA.
> >
> > I think we should clearly state some text to avoid ambiguity?
> >  Something like "The FA or HA is identified by the source IP
> > address of the registration message.  This IP address and the
> > SPI is used to index the security association to authenticate
> > the message."
> >
> > Thoughts?
> >
> > Kent
> >
> > --
> >       |           |                   Kent Leung
> >      :|:         :|:                  IP Mobility Development
> >     :|||:       :|||:                 IOS Technologies Division
> >    :|||||||:   :|||||||:              Voice: 408.526.5030
> > .:|||||||||:.:|||||||||:.             Fax:   408.525.1653
> >   c i s c o S y s t e m s             Email: kleung@cisco.com
> >
> > --
> > Mip4 mailing list: Mip4@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/
> >
>
>
>
>--
>Mip4 mailing list: Mip4@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/

--
      |           |                   Kent Leung
     :|:         :|:                  IP Mobility Development
    :|||:       :|||:                 IOS Technologies Division
   :|||||||:   :|||||||:              Voice: 408.526.5030
.:|||||||||:.:|||||||||:.             Fax:   408.525.1653
  c i s c o S y s t e m s             Email: kleung@cisco.com

-- 
Mip4 mailing list: Mip4@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/