Bob, I think I attended that BOF, but if I recall correctly I came away from it thinking that the group had based its conclusions on a fairly narrow set of assumptions about the nature and use of that protocol; change those assumptions slightly and it gets much more feasible. At any rate I don't see that this would have to be an entirely different transport protocol; it could be implemented using TCP options. If the server didn't support them, it would degrade to ordinary TCP. Keith
- Re: An alternative to TCP (part 1) Keith Moore
- 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
