![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Nicholas Weaver wrote:
Pardon me for a stupid question:
...
So the question is, why aren't the P2P developers pushing TCP Vegas, and using it whenever possible?
It loses compared to Reno - as you noted. It's also more sensitive to changes in RTT, BW due to dynamic routing.
2: A way of per-connection or per-app specifying the desired congestion control, so that a P2P program can specify "TCP Vegas". (Linux is a global /proc option rather than a per-app option IIRC).Thoughts? Comments?
AFAICT, that requires a dual stack, one like Marko Zec's Clonable Stacks (for FreeBSD).
Joe
Attachment:
signature.asc
Description: OpenPGP digital signature
Nicholas Weaver wrote:
Pardon me for a stupid question:
...
So the question is, why aren't the P2P developers pushing TCP Vegas, and using it whenever possible?
It loses compared to Reno - as you noted. It's also more sensitive to changes in RTT, BW due to dynamic routing.
2: A way of per-connection or per-app specifying the desired congestion control, so that a P2P program can specify "TCP Vegas". (Linux is a global /proc option rather than a per-app option IIRC).Thoughts? Comments?
AFAICT, that requires a dual stack, one like Marko Zec's Clonable Stacks (for FreeBSD).
Joe
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ p2pi mailing list p2pi at ietf.org https://www.ietf.org/mailman/listinfo/p2pi