>
>
>(SIW1 has html conversions of all slides online; SIW2 is wholly
>powerpoint. Really, I'd like to see pdfs of the lot - all the
>read-anywhere-platform-independent convenience of one, all the
>download-a-single-file convenience of the other.)
I'll get around to making PDFs sometime for the appropriate
presentations. I've been using animation in some presentations which
doesn't translate well to PDF. But, for some things, animation is very
effective to make the point. I don't think the HTML conversion works for
animations.
> > By the way, SCPS-TP advertises TCP's protocol number for reliable transport
> > protocol selections. It does this even if the pure rate-based transmission
> > is used. IMO, this is terrible as it make QoS and queue management very
> > difficult.
>
>QoS and queue management shouldn't depend on what traffic is, but on
>what traffic does imo - otherwise there's a semantic gap.
I agree, but, it takes far more energy to look at per flow information and
determine the traffic pattern and then put it in a queue. Assuming that
certain protocols react in certain ways is much easier and manageable -
albeit somewhat dangerous.
> When rate-based, SCPS-TP is still sending TCP-style packets, so the
>protocol identifier is valid.
I disagree. IMHO, one should not knowingly advertise a protocol number if
one is not conforming to those protocol characteristics. Just because the
header is the same style does not mean that it is the same
protocol. IMHO, SCPS should advertise it's own protocol number when
running rate-based, no congestion control.
Will
=======================================
Will Ivancic
NASA Glenn Research Center
21000 Brookpark Road MS 54-5
Cleveland, Ohio 44135
Phone +1 (216)433-3494
Fax +1 (216) 433-8705
Yahoo Instant Messenger ID: ivancic
http://roland.grc.nasa.gov/~ivancic
This archive was generated by hypermail 2b29 : Fri Jun 14 2002 - 15:11:14 EDT