Hi Michael, Thanks for your quick response. It will be helpful if you can explain why it should be 30.5 to 31.5. As per our understanding initially it should start with 33-seconds (30[HBInterval]+3[RTO initial]) right ?. Please correct me if my understanding is in-correct. Regards, Ravi -----Original Message----- From: Michael Tuexen [mailto:Michael.Tuexen@xxxxxxxxxxxxxxxxx] Sent: Monday, August 17, 2015 6:43 PM To: Ravi Puttachannaiah Cc: linux-sctp@xxxxxxxxxxxxxxx Subject: Re: SCTP heartbeat transmission interval in not working as expected > On 17 Aug 2015, at 13:45, Ravi Puttachannaiah <ravi.puttachannaiah@xxxxxxxxxxx> wrote: > > Hi, > > We are using LKSCTP (ver 1.0.16) and we observe that the SCTP heartbeat transmission interval in not working as expected. Following is the SCTP configuration settings we are using (applied using setsockopt()). > > > hbinterval=30-sec > RTO initial=3-sec > RTO min=1-sec > RTO max=60-sec > > As per our understanding the SCTP heartbeat transmission interval value should be between 31.5 to 34.5 seconds as per the calculation "RTO+HBInterval+delta(Âą0.5ofRTO)" but we are always seeing the value in-between 30.6 to 31.5 seconds. Assuming that the RTO is 1 second (after an RTT measurement this is true, I guess), you would get HBs every 30.5 and 31.5 seconds. Seems to be about what you measure. Best regards Michael > > Could somebody confirm if this is an issue or not and in-case of an issue how we can resolve. > > We are using LKSCTP version 1.0.16 and 1.0.7 and in both the versions we are observing the same behavior. > > > Regards, > > Ravi​ > > "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." > N‹§ēæėrļ›yúčšØbēXŽķĮ§vØ^–)Þš{.nĮ+‰·ĨŠ{ąąËiŠ{ayš ʇڙë,j ĒfĢĒ·hš‹āzđ ŪwĨĒļ Ē·Ķj:+v‰ĻŠwčjØmķŸĸū Ŧ‘ęįzZ+ƒųšˇŠÝĒj"¯ú! "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." ��.n��������+%������w��{.n�����{������ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
