RE: When to do Return Routability Checks

hi francis, 

this is issue is interesting. in a previous mail i had the impression that
you argued that only an authorized address can be used for communication
(non-return-routability-test messages). if you have an unauthorized address
you need to perform some authorization check (which might require a return
routability check) to turn this address into an authorized address which can
subsequently be used. 

if my observation is correct then you also suggest to have a window larger
than one in order for the protocol to work.

is this correct?

ciao
hannes

> 
>  In your previous mail you wrote:
> 
>    > => we need more flexibility about moving the SA: to wait the 
>    > RR check result is fine only when the previous peer address 
>    > is still usable.
> 
> => there are two cases when we move from peer address A to 
> peer address B:
>  - peer address A is still usable: the IKE SA should be updated
>    only after the end of the RR check
>  - peer address A is no more usable (the usual case with mobility):
>    the IKE SA (but not IPsec SAs) should be updated at the reception
>    of the update request
> Two details:
>  - there is scenario where ASAP update is mandatory: imagine an window
>    of one message is used and there is a pending request to send: if
>    it is sent to the peer address A and this address no more works
>    the exchange will never finish.
>  - now how to know when an address is no more usable: with my address
>    management framework the initiator wll simply remove it 
> from the set.
> 
> Thanks
> 
> [email protected]
>