Re: Summary of responses so far and proposal moving forward [Was Re: [tcpm] Is this a problem?]

John Heffner <jheffner@psc.edu> Wed, 21 November 2007 19:51 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iuvc7-0007sG-I6; Wed, 21 Nov 2007 14:51:59 -0500
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1Iuvc6-0007re-Mh for tcpm-confirm+ok@megatron.ietf.org; Wed, 21 Nov 2007 14:51:58 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iuvc5-0007nM-5M for tcpm@ietf.org; Wed, 21 Nov 2007 14:51:57 -0500
Received: from mailer2.psc.edu ([128.182.66.106]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iuvc4-0005rn-Of for tcpm@ietf.org; Wed, 21 Nov 2007 14:51:57 -0500
Received: from [128.182.160.132] (ice.psc.edu [128.182.160.132]) (authenticated bits=0) by mailer2.psc.edu (8.14.1/8.13.3) with ESMTP id lALJpsf4000620 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Nov 2007 14:51:54 -0500 (EST)
Message-ID: <47448C5A.7070007@psc.edu>
Date: Wed, 21 Nov 2007 14:51:54 -0500
From: John Heffner <jheffner@psc.edu>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
Subject: Re: Summary of responses so far and proposal moving forward [Was Re: [tcpm] Is this a problem?]
References: <0C53DCFB700D144284A584F54711EC58044CDF71@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <0C53DCFB700D144284A584F54711EC58044CDF71@xmb-sjc-21c.amer.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: tcpm@ietf.org
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Errors-To: tcpm-bounces@ietf.org

Anantha Ramaiah (ananth) wrote:
> I managed to read all the responses so far on this thread. At the time
> of writing this email, there have been 54 email exchanges (includes the
> authors' responses) around 9 people have responded so far not counting
> the private email exchanges. In order to prevent rat-holing this further
> I would like to step back a little and pose the following questions :-
> 
> A) Do we agree that it is a problem ? [the title of the thread]
> 
>    Most people seem to agree on this.

I would like to step back even further, and work on the definition of 
"it" -- the problem we want to solve.  In my mail on Nov 14 (which did 
not elicit a response), I tried to make the case that the issues framed 
in the draft are in fact only a special case of a more general problem.

I do not believe the indefinite nature of TCP's persist state is 
intrinsically something we need to fix -- in fact, it is clearly an 
important and useful feature of TCP.  It might not be terrible for a TCP 
implementation to provide a switch for an implicit ABORT after a long 
persist timeout.  However, in my opinion this is not the best solution, 
or even a solution at all to the more general problem.

I think if consensus can be reached on what the problem actually *is*, 
it may be more clear how to solve it, where the solution should go, and 
if this is something the IETF should take on.

   -John


_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm