Re: 51 - spi collisions

 In your previous mail you wrote:

      Storing the remote tunnel header IP address in the SPD cache may
      also complicate the implementation of MOBIKE, since the address
      can change during the lifetime of the SA. Thus, we recommend
      implementing the links between the SPD cache and the SAD in a way
      that does not require modification when the tunnel header IP
      address is updated by MOBIKE. For instance, in the C programming
      language, an ordinary pointer could be used.
   
   Any comments?
   
=> I am afraid it is not enough: the link issue is not the only issue:
if the SPD has no indication of what are the new endpoint addresses
to use after an update, one cannot guarantee a new SA pair will be
create using the right addresses. So an update should impact something
somewhere in the SPD.

Regards

[email protected]

PS: NAT-T and MIPv6 have the same issue. In NAT-T it is solved by
making the initiator always behind the NAT (so the address can "float"
as it is never used :-). In MIPv6 a solution is described in
draft-sugimoto-mip6-pfkey-migrate-01.txt and in the real world
an "unique" tag is used.
BTW a C pointer is not a good solution because there is no one-to-one
mapping between SPD and SAD.