![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi Lars,
comment in-line.
Best regards Michael
On Sep 17, 2007, at 12:11 PM, Lars Eggert wrote:
On 2007-9-17, at 12:13, ext Fred Baker wrote:The SCTP sender can handle multiple messages in different stream send queues in different ways.Dumb question of the month. With the exception of the last claim ("...can prioritize..."), this could just as easily describe SCTP. What here is new? And define "prioritize"?
For how this relates to SCTP, let me refer you to Section 6. (And yes, there are obvious similarities here to SCTP, but also RFC2140- like integrated congestion control, etc.)
"Prioritize" meaning how a sender allocates the available path capacity for the SST "bundle" between connection instances. A demo that Bryan did that showed HTTP over SST dynamically adjusted priorities such that objects that were being rendered on the screen were transmitted at a higher priority, even while scrolling around a large page.
On Sep 17, 2007, at 2:02 AM, Lars Eggert wrote:You might be interested in Bryan Ford's SST paper from this year's SIGCOMM:
Structured Streams: a New Transport Abstraction. Bryan Ford. ACM SIGCOMM 2007, August 27-31, 2007, Kyoto, Japan. http:// www.brynosaurus.com/pub/net/sst-abs.html
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.