> As I am sure you recall, the IETF held a BOF on "TCPng" some years > ago. It went over exactly the same ground tilled Mr. Gao. The > BOF's conclusion was that any gains would be marginal and would > not justify the trauma of change. 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. allman --- Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/
- Re: An alternative to TCP (part 1) Jon Crowcroft
- Re: An alternative to TCP (part 1) Colin Perkins
- Re: An alternative to TCP (part 1) Jun'an Gao
- Re: An alternative to TCP (part 1) Harald Alvestrand
- Re: An alternative to TCP (part 1) Jun'an Gao
- RE: An alternative to TCP (part 1) aaron
- Re: An alternative to TCP (part 1) Richard Carlson
- Re: An alternative to TCP (part 1) John Stracke
- Re: An alternative to TCP (part 1) Bob Braden
- Re: An alternative to TCP (part 1) Keith Moore
- Re: An alternative to TCP (part 1) Mark Allman
- Re: An alternative to TCP (part 1) Kevin Farley
- 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
