Jon Crowcroft (jon@Cs.Ucl.AC.UK)
Mon, 1 Jun 87 15:23:37 GMT-0:00
Of course, if you use X.25 you don't have this problem :-). The
switches can use level 2 to support fragment sizes properly
over each hop, and level 3 to get end to end packet sizes
efficient, and a well known transport protocol over that...
Then all you need is to work out how to get CCITT to accept
giant window size and packet size options to make it work well
over a big network.
The strain of hop by hop versus end to end arguments starts to
show when you try and use an underengineered mil-spec net for
heavy duty service.
What Vint says sounds good to me - figure out how to get hop by
hop information back to the end to end protocols so they can be
taught how to behave properly. Real problem here is for short
lived protocol entities - eg query systems running in PCs - who
dont get a chance to used previously cached info...
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:38:19 GMT