Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 07 Dec 2006 13:36:28 -0500
From:      Randall Stewart <rrs@cisco.com>
To:        maillist ifiaas <maillist.ifiaas@gmail.com>
Cc:        freebsd-net@freebsd.org
Subject:   Re: Urel, a TCP option for Unreliable Streaming. Need your help.
Message-ID:  <45785F2C.7040004@cisco.com>
In-Reply-To: <161d69110612070451o6945c7c0y9cf7a7e8b6b7225d@mail.gmail.com>
References:  <161d69110612060709n3bf99bd4y47d94b021b8f1d02@mail.gmail.com>	 <m21wncv66z.wl%gnn@neville-neil.com> <4577D858.4010300@freebsd.org>	 <2786D1DE-E8FA-490C-AFF7-E458E262AEF7@lurchi.franken.de>	 <161d69110612070242p612e2318ya8d285a15a54e9fc@mail.gmail.com>	 <4578057B.9080002@cisco.com> <161d69110612070451o6945c7c0y9cf7a7e8b6b7225d@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
maillist ifiaas wrote:
> Thanks Randall.
> 
> Am I right to say that, in SCTP, the loss information is reported to
> the sender, instead of the receiver?
Correct... the sender is notified of the loss... you could
tell the receiver as well.. but the current BSD implementation
does not do this .. the info is there .. just not reported :-D
> 
> Btw, TCP Urel is a option. To use it, you have to add something like,
> int rc = setsockopt( inSettings->mSock, IPPROTO_TCP,TCP_URE, (char*)
> &val, len );
> to enable Urel option in TCP.

Yep.. I thought so, so  basically it is no different than
having to set the prefered send option.. with a socket opt..
and then a one line change to add IPPROTO_SCTP to the socket() call ..

No different coding wise I think..
> 
> I still think that partial reliability should be performed in the
> application layer. Although transport layer knows more about the
> channel condition, but they can either be reported to the application
> (like we did on segment loss in TCP Urel),  or be infered by
> application (e.g. estimating the current bitrate by looking at the
> buffersize). As QoS is only meaningful to application, allowing
> flexibilty of implementing QoS (such as partial relaibility) mechenism
> in application layer rather than transport layer, looks much natrual to me.

Then why modify TCP?

R
> 
> -gavin
> 
> On 12/7/06, Randall Stewart <rrs@cisco.com> wrote:
> 
>> maillist ifiaas wrote:
>> > Michael,
>> >
>> > In PR-SCTP where retranmission is set off, does it allows the
>> > applications to know which part of data is lost in the stream?
>> > Thanks
>>
>> Yep.. you subscribe for a notification event and SCTP will
>> return you the data that was not sent.
>>
>> So not only does it let you know you can actually let
>> SCTP hold and return the data that did not get
>> acknowledged.. The API also has a context so you
>> can attach a user defined 32 bit value to the
>> data.. to say bind a pointer to an object to
>> the actual data... for lookup or other stuff :-)
>>
>> R
>> >
>>
>>
>>
>> -- 
>> Randall Stewart
>> NSSTG - Cisco Systems Inc.
>> 803-345-0369 <or> 803-317-4952 (cell)
>>
> 


-- 
Randall Stewart
NSSTG - Cisco Systems Inc.
803-345-0369 <or> 803-317-4952 (cell)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45785F2C.7040004>