Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!nike!ucbcad!ucbvax!QUABBIN.SCRC.SYMBOLICS.COM!DCP
From: DCP@QUABBIN.SCRC.SYMBOLICS.COM (David C. Plummer)
Newsgroups: mod.protocols.tcp-ip
Subject: Re:  overly short RTT's
Message-ID: <861104130028.8.DCP@KOYAANISQATSI.S4CC.Symbolics.COM>
Date: Tue, 4-Nov-86 13:00:00 EST
Article-I.D.: KOYAANIS.861104130028.8.DCP
Posted: Tue Nov  4 13:00:00 1986
Date-Received: Fri, 7-Nov-86 23:38:51 EST
References: <steve@BRL.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 16
Approved: tcp-ip@sri-nic.arpa


    Date:     Sun, 2 Nov 86 16:20:09 EST
    From:     Stephen Wolff <steve@BRL.ARPA>

    Umm.  There are even now other things than TCP lurking within those
    innocent IP wrappers, and their number will increase as various children
    of the ISO family are adopted.  Should the gateway know them all?  -s

As much as possible: Yes.  This strategy helped tremendously with
another network protocol (Chaos) which has a .5 second retransmit
timeout when used over slow (9600 baud) land lines.  It actually did
more than that: it understood enouch of Chaos to limit the number of
packets per connection.  This problem was slightly alleviated by
changing out Chaos implementation to retransmit only the first packet on
the queue, which I think is common lore for all protocol implementations
now-a-days.