Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document

Joe Touch <touch@ISI.EDU> Fri, 03 October 2008 07:20 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id AA2253A6975; Fri, 3 Oct 2008 00:20:49 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id AE8993A686A for <>; Fri, 3 Oct 2008 00:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.852
X-Spam-Status: No, score=-2.852 tagged_above=-999 required=5 tests=[AWL=-0.253, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CTkHeUt3b88C for <>; Fri, 3 Oct 2008 00:20:47 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 13ED03A6A59 for <>; Fri, 3 Oct 2008 00:20:38 -0700 (PDT)
Received: from [] ( []) by (8.13.8/8.13.8) with ESMTP id m937JaTA016803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 Oct 2008 00:19:38 -0700 (PDT)
Message-ID: <>
Date: Fri, 03 Oct 2008 00:19:36 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird (Windows/20080914)
MIME-Version: 1.0
To: Murali Bashyam <>
References: <> <> <EC7B72027914A242B991C029F5F213CF2AB0CCA6AA@exchsvr01.ocarina.local> <> <EC7B72027914A242B991C029F5F213CF2AB0CCA6BB@exchsvr01.ocarina.local>
In-Reply-To: <EC7B72027914A242B991C029F5F213CF2AB0CCA6BB@exchsvr01.ocarina.local>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
Cc: David Borman <>, "" <>, "Anantha Ramaiah (ananth)" <>
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hash: SHA1

Murali Bashyam wrote:
> The standard already says, IMO, that they MAY do this. Not that they
> MUST. The standard says nothing about what to do when you run out of
> resources to run the connections you're currently supporting - it says
> nothing about what to do when new connections arrive in that state
> either. Memory management is the OS's job, not the protocol's.
>> Which standard are u referring to? I'm quoting from RFC 1122, page 91
>> the section on probing zero windows :
>> "As long as the receiving TCP continues to send acknowledgments in response to the
>> Probe segments, the sending TCP MUST allow the connection to stay open."
>> Can you point me to the word "MAY" in that sentence that you are referring to?

It's implied by the conditional. I.e., if the receiving TCP stops
sending ACKs, the sending TCP can drop the connection.

As to the sending side, there's the ABORT call in 793 - which we
discussed on this list before. The point is that _TCP_ can't decide to
stop the connection because of the TCP state of the other end, the local
TCP state, or behavior on the wire. Nothing in 793 says that the OS
can't kill the connection - any connection - at any time.

>> The important thing here is to clarify that sentence and the sender's behaviour
>> and prevent what appears to be a conflict between memory management
and protocol violation.

Please describe anywhere in 1122 or 793 where memory management is

As I've noted before, this isn't a protocol violation - it's a failure
of an OS to support arbitrary numbers of instances of a protocol.

Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla -

tcpm mailing list