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

Joe Touch <touch@ISI.EDU> Fri, 26 September 2008 22:32 UTC

Return-Path: <tcpm-bounces@ietf.org>
X-Original-To: tcpm-archive@megatron.ietf.org
Delivered-To: ietfarch-tcpm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 119353A6A86; Fri, 26 Sep 2008 15:32:57 -0700 (PDT)
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 295BE3A68DD for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 15:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level:
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxAVwagq49Yt for <tcpm@core3.amsl.com>; Fri, 26 Sep 2008 15:32:55 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 16EB03A6A86 for <tcpm@ietf.org>; Fri, 26 Sep 2008 15:32:55 -0700 (PDT)
Received: from [128.9.176.49] (c1-vpn10.isi.edu [128.9.176.49]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id m8QMWO3g021402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 Sep 2008 15:32:26 -0700 (PDT)
Message-ID: <48DD62F8.3080708@isi.edu>
Date: Fri, 26 Sep 2008 15:32:24 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: David Borman <david.borman@windriver.com>
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
In-Reply-To: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com>
X-Enigmail-Version: 0.95.7
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org, "Anantha Ramaiah \(ananth\)" <ananth@cisco.com>, mbashyam@ocarinanetworks.com
Subject: Re: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave,

I'm not sure any of us disagreed with the content. The question is
whether it's important, useful, or necessary (in that order) to address
this, or whether we feel that the existing specs are sufficient.

My conclusion was that applications can always terminate TCP
connections, and so can OS's - e.g., an OS can always just reboot.

This still sounds like an implementation guideline to me. It may be
useful, and may be useful to document, but since it's implementation
focused, I'm not sure I see it as a protocol document.

As a result, I don't think this needs to be a WG document (which is
where I thought things were from Dublin). We talked there about it
potentially being an errata to 1122, and even the problems with that
approach.

Finally, it is not clear this is even in scope - it's not a modification
to TCP, nor is it maintenance.

Joe

David Borman wrote:
> At Dublin a presentation was made on draft-ananth-tcpm-persist-00.txt. 
> Not a lot of people had read the document at the time of the
> presentation, but there didn't seem to be any objections to adopting it
> as a TCPM WG document.
> 
> The authors posted a summary to the mailing list, have responded to all
> issues that were raised, and have a new version of the document ready
> for publication.  We (Wes and I) feel that there is support for adopting
> this as a WG document, but as always, we need to verify this on the
> mailing list.  So, if you have any objections to adopting this as a WG
> document, please speak up now.  Also speak up if you support adopting it
> as a WG document.
> 
> I'll be the first to say I support adopting this as a WG document.  If
> there are no serious objections, the authors can submit their updated
> version next week and Wes and I will add it to our list of WG documents.
> 
>             -David Borman, TCPM WG co-chair
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjdYvgACgkQE5f5cImnZrsMrACfTV5Bl9beeAJ29JDszVT6sVhY
XQAAoN8VPIAizeB1Z+IgkD/6iwT1h+HP
=jSx6
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm