From: Mark Allman <[EMAIL PROTECTED]>
Date: Wed, 07 Feb 2001 16:12:52 -0500
I am fairly unconvinced in the arguments made by Mr. Gao. However,
maybe a TCPng is the wrong way to look at things. A better model,
it seems to me, is the one followed by SCTP. In other words, let's
build a new transport that has semantics that are different from
TCP. As long as it is safe (i.e., follows good congestion control),
why should we care how many of these protocols are defined? After
we ensure the protocols are safe we can just let Darwinism take its
course.
Does SCTP really have different semantics from TCP? I thought it was
more of a superset.
- Ted
- Re: An alternative to TCP (part 1) John Stracke
- Re: An alternative to TCP (part 1) Mahadevan Iyer
- Re: An alternative to TCP (part 1) Richard Carlson
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) Larry Foore
- Re: An alternative to TCP (part 1) joaquin . riverarodriguez
- Re: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) Iliff, Tina
- Re: An alternative to TCP (part 1) tytso
- Re: An alternative to TCP (part 1) Randall R. Stewart
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Randall R. Stewart
- RE: An alternative to TCP (part 1) Bernard Aboba
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Mark Allman
- Re: An alternative to TCP (part 1) James P. Salsman
