Re: Re: regarding INIT ACK from different destination IP.
"Ambika Tripathy" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Hi Brain,
The section 5.1.2 of the rfc-2960 tell some thing differnet regarding
the INIT_ACK transmission.
" Note: The INIT-ACK MUST be sent to the source address of the INIT."
There is such clear description present to transmit, INIT_ACK to an IP
address which is present in INIT's IP address list in case of multihomed end
point.
Is it an implementation dependent feature?
--
Br,
Ambika Prasad Tripathy
Cell: +91-94375 47730
On 9/26/06, Brian F. G. Bidulock <[email protected]> wrote:
>
> Padmalochan,
>
> Padmalochan Moharana wrote: (Tue, 26 Sep 2006 00:17:42)
> > Hi Brian
> >
> > please suggest for the following doubt.
> >
> > Should endoint (in case of Multi-homed), encode COOKIE
> > ECHO on receive the INIT_ACK from a different
> > destination IP of the INIT or it should ignores the
> > INIT_ACK.
>
> If the INIT_ACK corresponds to an INIT that was sent (addresses
> in the address list, verification tag, parameters and a cookie),
> send the COOKIE ECHO.
>
> Why would you think otherwise?
>
> --brian
>
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/
>
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran
>
_______________________________________________
Sigtran mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/sigtran