Re: [SCTP] clarification about HB.Max.Burst parameter

"Ashish Gupta" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <2690213D5CBF0C479454EE80957DA8BD092B10@in-exchange>
Hi Ashwani,

 

When RTO expires for an address, your path probing module will get
chance to send HEARTBEATS to other UNCONFIREMD addresses as well (NOT
only to the address for which RTO has expired) limited by HB.Max.Burst
parameter.

 

Hope this helps.

 

Regards,

-Ashish

 

________________________________

From: [email protected] [mailto:[email protected]] On
Behalf Of Ash Kat
Sent: Wednesday, June 04, 2008 3:14 PM
To: [email protected]; [email protected]
Subject: [Sigtran] [SCTP] clarification about HB.Max.Burst parameter

 

Hello All,

 

SCTP RFC 4690 has mentioned a parameter HB.Max.Burst.

As per RFC 4960 section 4.5 :

   The number of HEARTBEATS sent at each RTO SHOULD be limited by the
   HB.Max.Burst parameter.

 

During the Path verification when an RTO expires, SCTP will re-send the
Heartbeat to that address.

Please clarify me, how HB.Max.Burst parameter will control the number of
Heartbeat sent to that address.

Shouldn't the number of Heartbeat send to a particular address at any
time will always be 1? 

If Yes, then why HB.Max.Burst is required?

If No, then please make me understand that how this parameter is used.

 

Thanks & Regards,

Ashwani Kathuria





________________________________

Bring your gang together. Do your thing. Find your favourite Yahoo!
Group.
<http://in.rd.yahoo.com/tagline_groups_9/*http:/in.promos.yahoo.com/grou
ps/>

_______________________________________________
Sigtran mailing list
[email protected]
https://www.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.