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

"Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov> Tue, 30 September 2008 04:24 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 C58783A68B5; Mon, 29 Sep 2008 21:24:58 -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 B5BF13A6974 for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 21:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level:
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 95TktotrElpx for <tcpm@core3.amsl.com>; Mon, 29 Sep 2008 21:24:56 -0700 (PDT)
Received: from ndmsnpf02.ndc.nasa.gov (ndmsnpf02.ndc.nasa.gov [198.117.0.122]) by core3.amsl.com (Postfix) with ESMTP id 9E38A3A68B5 for <tcpm@ietf.org>; Mon, 29 Sep 2008 21:24:56 -0700 (PDT)
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102]) by ndmsnpf02.ndc.nasa.gov (Postfix) with ESMTP id B8F237A1A2; Mon, 29 Sep 2008 23:25:10 -0500 (CDT)
Received: from ndjsxgw03.ndc.nasa.gov (ndjsxgw03.ndc.nasa.gov [129.166.32.111]) by ndjsppt03.ndc.nasa.gov (8.14.1/8.14.1) with ESMTP id m8U4P9rj019009; Mon, 29 Sep 2008 23:25:09 -0500
Received: from NDJSEVS25A.ndc.nasa.gov ([129.166.32.124]) by ndjsxgw03.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.3959); Mon, 29 Sep 2008 23:25:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 29 Sep 2008 23:25:10 -0500
Message-ID: <B5A5E01F9387F4409E67604C0257C71E0991C8@NDJSEVS25A.ndc.nasa.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] draft-ananth-tcpm-persist-00.txt as a WG document
Thread-Index: AckihQdHudyMWFA4TMCB0PC/1aEl4wALmbAL
References: <53797EED-2C93-4E20-AF60-E3C0EF8F85AC@windriver.com><48DD62F8.3080708@isi.edu> <26E7B0F8-D0E7-4C3D-B51D-EA89B2045BAC@windriver.com>
From: "Eddy, Wesley M. (GRC-RCN0)[VZ]" <Wesley.M.Eddy@nasa.gov>
To: "David Borman" <david.borman@windriver.com>, "Joe Touch" <touch@isi.edu>
X-OriginalArrivalTime: 30 Sep 2008 04:25:11.0035 (UTC) FILETIME=[86F3C4B0:01C922B4]
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: multipart/mixed; boundary="===============1627835457=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

As an individual, not a co-chair, it's my hope that part of "TCP maintenance" would include clarifying questions that implementers are bringing when it's legitimately the case that the original specification can be viewed as unclear or missing some commentary.  Amazingly, there are still new TCP implementations being written in 2008, and likely into the future, so it may prove useful.
 
My personal feeling is that the content of this particular draft is so easy to agree on (nobody has objected to it, at least), that it should ideally be very quick and easy to make a few editorial passes on it and and call it done.  It would probably take less time than debating over whether it's absolutely undeniably necessary or what WG it belongs to :).  As for where the work should be done, if it is done, I agree with Ted that TCPM exists to offload work from the RSVP maintenance and minor extensions working group aka TSVWG.
 
 
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm