Re: Re: regarding INIT ACK from different destination IP.

Bhanu,

All addresses provided by the user to the INIT are considered confirmed.
Therefore, the receiver of the INIT-ACK is welcomed to send a COOKIE-ECHO
to one of the addresses provided by the user for which the INIT was
launched.  It does not matter what destination address was in the INIT-ACK.

I think that you miss the point.  The INIT-ACK MUST be sent to the source
address of the INIT.  But the receiver of the INIT-ACK may ignore the
destination address in the message.

--brian

Bhanu Prakash wrote:                          (Tue, 26 Sep 2006 14:17:23)
> 
>    Brian,
>    In the same section please see the following explanation:
>    ***********************
>        An  endpoint  MUST  NOT send any chunks to an UNCONFIRMED address,
>    with
>       the following exceptions:
>       - A HEARTBEAT including a nonce MAY be sent to an UNCONFIRMED
>         address.
>       - A HEARTBEAT-ACK MAY be sent to an UNCONFIRMED address.
>        -  A COOKIE-ACK MAY be sent to an UNCONFIRMED address, but it MUST
>    be
>          bundled  with  a HEARTBEAT including a nonce.  An implementation
>    that
>         does NOT support bundling MUST NOT send a COOKIE-ACK to an
>         UNCONFIRMED address.
>        -  A COOKE-ECHO MAY be sent to an UNCONFIRMED address, but it MUST
>    be
>          bundled  with a HEARTBEAT including a nonce, and the packet MUST
>    NOT
>         exceed the path MTU.  If the implementation does NOT support
>         bundling or if the bundled COOKIE-ECHO plus HEARTBEAT (including
>          nonce)  would  exceed the path MTU, then the implementation MUST
>    NOT
>         send a COOKIE-ECHO to an UNCONFIRMED address.
>    ************************
>    Thanks,
>    Bhanuprakash.
>    Brian F. G. Bidulock wrote:
> 

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/