-
sctp
SCTP Discussions
Text archives Help
- From: Raja Muhammad Hammad <rajahammad AT gmail.com>
- To: discussion AT sctp.de
- Subject: [SCTP-Discussion] SCTP Partial reliability?
- Date: Thu Mar 24 00:12:07 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=uGxC2YWO68T9TlfWGIKHQxzYiIf7bverWAViCqQQBe5sIfrlUOajvkPCY7z+sFoTgF06jFrPUeLb9Ux9hal/Nl6jtZVYloH9UDv0JTL29LBI3zvLvp/ab13lnYkal/8id/PQ7MbnxeZ5sPadaDymAVpwPxvVWQNSMqPQM4Bdb7c=
- List-id: SCTP Discussions <discussion.sctp.de>
hi
I am confused as how to use partial reliability (PR) in my application.
Does the parameter in sctp_sendmsg() "timetolive" provide PR semantics
or there is something else required to exploit PR.
As stated out in SCTP socket API draft, lifetime parameter in RFC 2960
is different from the timed-reliability service in a way that if
"if SCTP has sent the first transmission before the lifetime expires,
then the message MUST be sent as a normal reliable message." which
means retransmissions of the message even if lifetime expires until
its ACK is received.
"When the "timed reliability" service is invoked, this latter
restriction is removed." By later it definitely means retransmisions
here.
Now in sctp_sendmsg() I guess "timetolive" corresponds to "lifetime"
parameter which means it does not provide PR semantics?.
I hope somebody could clear this out as what exactly is PR and how to
use it in an application using sctp library. It would be really
helpful to give an
example here.
Regards
Hammad
- [SCTP-Discussion] SCTP Partial reliability?, Raja Muhammad Hammad, 03/24/2005
- [SCTP-Discussion] Re: SCTP Partial reliability?, Raja Muhammad Hammad, 03/25/2005
- Re: [SCTP-Discussion] SCTP Partial reliability?, Michael Tuexen, 03/26/2005
Archive powered by MHonArc 2.6.19+.
