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

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/