Subject: RE: [Hipsec] review of comments on draft-ietf-hip-mm-00 preview

From: "Henderson, Thomas R" <[email-masked]>
Date: Tue, 12 Oct 2004 21:58:39 -0700

Mika,
I agree that we can generalize these figures, and 
will adapt some of them along the lines that you
suggested, or else point it out in the corresponding
text.

Tom

> -----Original Message-----
> From: Mika Kousa [mailto:[email-masked]]
> Sent: Monday, October 11, 2004 4:46 AM
> To: [email-masked]
> Subject: Re: [Hipsec] review of comments on 
> draft-ietf-hip-mm-00 preview
> 
> 
> 5.1  Mobility with single SA pair
> 
> Mobile Host                         Peer Host
> 
>          UPDATE(REA, SEQ)
>  ----------------------------------->
>          UPDATE(SPI, SEQ, ACK, ECHO_REQUEST)
>  <-----------------------------------
>          UPDATE(ACK, ECHO_RESPONSE)
>  ----------------------------------->
> 
>   Figure 3: Readdress without rekeying, but with address check
> 
> 
> 
> Now that we have seen the change needed for address check procedure 
> (ECHO_REQUESTs are sent to each of the addresses listed in 
> the REA, see 
> this same thread), this section needs some editing.
> 
> Peer Host does not need to send ACK for the REA-UPDATE in 
> every UPDATE it 
> sends related to address check procedure, it could send just 
> ACK-UPDATE 
> and after that the Peer Host sends the ECHO_REQUEST-UPDATEs:
> 
> For example:
> 
> 
> Mobile Host                         Peer Host
> 
>          UPDATE(REA(addr_1,addr_2), SEQ)
>  ----------------------------------->
>          UPDATE(ACK)
>  <-----------------------------------
> 
>   sent to addr_1: UPDATE(SPI, SEQ, ECHO_REQUEST)
>  <-----------------------------------
>          UPDATE(ACK, ECHO_RESPONSE)
>  ----------------------------------->
> 
>   sent to addr_2: UPDATE(SPI, SEQ, ECHO_REQUEST)
>  <-----------------------------------
>          UPDATE(ACK, ECHO_RESPONSE)
>  ----------------------------------->
> ...
> 
> 
> Maybe the other figures and related texts in section 5 need similar 
> changes when there is a possibility that REA contains many 
> addresses, too.
> _______________________________________________
> Hipsec mailing list
> [email-masked]
> http://honor.trusecure.com/mailman/listinfo/hipsec
> 
_______________________________________________
Hipsec mailing list
[email-masked]
http://honor.trusecure.com/mailman/listinfo/hipsec