Re: SCTP: Heartbeat ack recieved without sending Heartbeat

Michael Tuexen <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
Hi,

since it is not from you:
Do not process it.

I would also just drop it and take no further action.

Best regards
Michael

PS: When receiving a HB-ACK in response to an HB I would check if
     all fields make sense. You should not be attackable by a peer
     which modifies the HB info...

On Jun 16, 2006, at 11:09 AM, ash kat wrote:

> Hi All
>
> What should be the behavior of SCTP when an endpoint recieved a  
> Heartbeat-ack from peer when it has not sent any heartbeat to peer?
>
> Is RFC 2960 say anything about this?
>
> If Not then What is the proper solution:
> 1. The Endpoint should drop the message [ ignore the Heartbeat ack ]
> 2. Process the Hearbeat ack as normal.
> 3. Send an Abort to peer.
> 4. Some other option.....
>
> Regards,
> Ashwani Kathuria.
>
> Do you Yahoo!?
> Next-gen email? Have it all with the all-new Yahoo! Mail Beta.
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.