- From: Raja Muhammad Hammad <rajahammad AT gmail.com>
- To: discussion AT sctp.de
- Subject: [SCTP-Discussion] Re: SCTP Partial reliability?
- Date: Fri Mar 25 17:52:03 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:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KRI3M81ngzjz+E9mFQ/QagZtnMR6ZOiLO4UkJ53iLwrmSFfYXbsoPI88HfTDDfEevkLDQjVmZUab4cTNQVVO+CwH0JBIGKA7Yq4OZnsYxWZFrtglIbeCbabRm3FreOaAYzQDEX1C66c4HE0/9Wfu6YxhgUNhBZODHRqT6EA9GDw=
- List-id: SCTP Discussions <discussion.sctp.de>
Can somebody please help me here?
On Thu, 24 Mar 2005 04:10:22 +0500, Raja Muhammad Hammad
<rajahammad AT gmail.com>
wrote:
>
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
>
Archive powered by MHonArc 2.6.19+.