Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!oddjob.uchicago.edu!matt
From: matt@oddjob.uchicago.edu.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: secure replacements for passwords
Message-ID: <8701182057.AA00808@oddjob.UChicago.EDU>
Date: Sun, 18-Jan-87 15:57:51 EST
Article-I.D.: oddjob.8701182057.AA00808
Posted: Sun Jan 18 15:57:51 1987
Date-Received: Sun, 18-Jan-87 18:35:37 EST
References: <870113143008.200363@MIT-MULTICS.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: matt@oddjob.uchicago.edu (Matt Crawford)
Organization: Just Things `n' Stuff, Et Cetera, Ltd.
Lines: 9
Approved: tcp-ip@sri-nic.arpa

J. Spencer Love writes:
) I don't know about your TCP, but the Multics TCP will send a RST
) immediately if it receives a packet with an ACK that it`s too high.  I
) believe that this is clearly spelled out in the specification, but I am
) at home and don't have the specification handy.

Nope, RFC-793 says "If the ACK acks something not yet sent
(SEG.ACK > SND.NXT) then send an ACK, drop the segment, and
return.