| Will look at it tomorrow (along with performance testing existing
| changes in tree) as meant to be preparing coursework and working on
| PhD today.... Agree MSS is problematic at present without PMTU. My
| thoughts were to have moving average and explicit s setting as two
| options available to user. If they don't set s then use moving
| average. I agree with Eddie that users should be able to define s if
| they want to.
.... but then it needs support in the API as well. The broken socket API is what really
worries me - there would be this one socket option which is only for CCID 3 and only for
experimental work.
Why is it broken? The RFC says that the user can have the option of
setting the packet size s, so it is not experimental. Yes it is only
for CCID3 but there are already lots of things that are CCID2 or CCID3
only.
Ian
--
Ian McDonald
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group
Department of Computer Science
University of Waikato
New Zealand
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
