Re: [tcpm] poll for adoption of draft-ananth-persist-02

Murali Bashyam <> Tue, 23 March 2010 22:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EDFC13A6841 for <>; Tue, 23 Mar 2010 15:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.305
X-Spam-Status: No, score=0.305 tagged_above=-999 required=5 tests=[AWL=1.440, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, IP_NOT_FRIENDLY=0.334]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id c3lm4Qj8qwir for <>; Tue, 23 Mar 2010 15:21:31 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 0241A3A691F for <>; Tue, 23 Mar 2010 15:21:24 -0700 (PDT)
Received: from exchsvr01.ocarina.local ([]) by exchsvr01.ocarina.local ([]) with mapi; Tue, 23 Mar 2010 15:23:28 -0700
From: Murali Bashyam <>
To: John Heffner <>, Mahesh Jethanandani <>
Date: Tue, 23 Mar 2010 15:23:19 -0700
Thread-Topic: [tcpm] poll for adoption of draft-ananth-persist-02
Thread-Index: AcrKt9ml53tX+GGiTfSHyKXBSzdMFgAGbw0w
Message-ID: <EC7B72027914A242B991C029F5F213CF3EBF3BAB5B@exchsvr01.ocarina.local>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>
Subject: Re: [tcpm] poll for adoption of draft-ananth-persist-02
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: <>, <>
X-List-Received-Date: Tue, 23 Mar 2010 22:21:38 -0000

There are other aspects too, it's also important for the application to control the duration that the connection spends in persist state, this is planned to be accomplished via a socket option. Both *OS and application* need to control the duration that a connection spends in the persist state.

There are scenarios when the application releases its connection state after writing all the data into the socket (so called orphan connections), and after this if the TCP connection enters into a ZWP condition, the application does not have the connection state to issue the ABORT, but if it has setup the socket option before, then TCP can still enforce the specified duration.

-----Original Message-----
From: [] On Behalf Of John Heffner
Sent: Tuesday, March 23, 2010 11:35 AM
To: Mahesh Jethanandani
Subject: Re: [tcpm] poll for adoption of draft-ananth-persist-02

Here's all I think needs to be said (at all, not just section 7), but
I'm a minimalist. :)

Section of RFC 1122 states:

            A TCP MAY keep its offered receive window closed
            indefinitely.  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.

To clarify, the above statement is not meant to restrict the ABORT
command [RFC793] in any way.  TCP should react to an ABORT in the same
way regardless of the current receive window.


On Tue, Mar 23, 2010 at 1:11 PM, Mahesh Jethanandani <> wrote:
> Hash: SHA1
> On 3/22/2010 7:15 PM, John Heffner wrote:
>> I'm pretty sure Section 7 describes automatically aborting connections
>> because they are in the persist state for some period of time.
> Since your concern is about the wording of section 7 you can help us
> reword it to remove any doubts that you might have.
> Do you want to do that?
> - --
> *Mahesh Jethanandani*
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla -
> gq2fGRz/SR6dm0ZR1551LfpCNSuC3Jn53DYjGILSFr2m2kzrh9KSFgjKEzBHssE0
> 8WYih30ufdTv6M9XYGhrlLq5uX5bgDAlEJP4NfmjS4B9BgW5DP95rG3PN+r/jCCb
> mLFIuOjhGyZfCYEniZHnT+TpyPS71msaLzKrXCFnWHY1Y1ybaHz8lHp9oBykTIpv
> AwE90PHSRCWP/RHYmr9d7hAagJ6Xmuruh4KSomn3BsbZHzxpOAQ8SkdHXAuPcv9u
> 4iBIQtXlz5X7EseJcORxHPV6e2OISizjkcIBxZ9qOo3hr/w0HteW50hZMbCyGjg=
> =PAr7
tcpm mailing list