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

"Anantha Ramaiah (ananth)" <ananth@cisco.com> Wed, 14 April 2010 15:32 UTC

Return-Path: <ananth@cisco.com>
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 0F44728C1E3 for <tcpm@core3.amsl.com>; Wed, 14 Apr 2010 08:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 phlm8tdI15kz for <tcpm@core3.amsl.com>; Wed, 14 Apr 2010 08:32:25 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8ED1228C1EF for <tcpm@ietf.org>; Wed, 14 Apr 2010 08:32:24 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAM58xUurR7Ht/2dsb2JhbACbVnGjV5luhQ0Egyk
X-IronPort-AV: E=Sophos;i="4.52,205,1270425600"; d="scan'208";a="514867708"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 14 Apr 2010 15:32:18 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3EFWIHq029440; Wed, 14 Apr 2010 15:32:18 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Apr 2010 08:32:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Apr 2010 08:32:17 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5809605EAA@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <C304DB494AC0C04C87C6A6E2FF5603DB47E1253387@NDJSSCC01.ndc.nasa.gov>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] poll for adoption of draft-ananth-persist-02
Thread-Index: Acq++HhKPa/WNfamRcGprqSmMXJeBgc3B4fwAARMR6A=
References: <C304DB494AC0C04C87C6A6E2FF5603DB47DF997794@NDJSSCC01.ndc.nasa.gov> <C304DB494AC0C04C87C6A6E2FF5603DB47E1253387@NDJSSCC01.ndc.nasa.gov>
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: "Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]" <wesley.m.eddy@nasa.gov>, <tcpm@ietf.org>
X-OriginalArrivalTime: 14 Apr 2010 15:32:18.0523 (UTC) FILETIME=[AAEF7AB0:01CADBE7]
Subject: Re: [tcpm] poll for adoption of draft-ananth-persist-02
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: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 14 Apr 2010 15:32:26 -0000

Wes, 

> -----Original Message-----
> From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On 
> Behalf Of Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
> Sent: Wednesday, April 14, 2010 6:22 AM
> To: tcpm@ietf.org
> Subject: Re: [tcpm] poll for adoption of draft-ananth-persist-02
> 
> After reviewing this mailing list thread and the IETF 77 
> discussion, David and I think there's support to make this a 
> working group document.
> 
> As we see it, the path to take toward publication is:
> 
> 1) authors submit a draft-ietf-tcpm version of the document

Should we re-submit the draft-ietf version taking into incorporating all
the comments we have received so far + new boiler plate etc.,? 


> 2) authors need to come to closure with several people who
>    disagree with specification of a new socket option; this
>    seems to be the main point of contention

Ok, there seems to be some confusion caused with the purpose of socket
option and the references to SO_LINGER etc., I think we need to get
closure on this issue. We (authors) discussed these responses and we
agree that if there is enough guidance that already exists to support
the implementers, then there is no need to invent any new socket option
and just mention the existing tools. OTOH, if currently there are no
ways to make things work reliably, we think that it is not a bad idea to
give some examples in the appendix (after all it is an informational
document and we are not changing ANY standard here, so I personally see
no conflict of interest here). The key is to give a guidance (or at the
least an example) to implementers and we think it is within the scope of
the informational document. That is the reason to mention the socket
option etc., in the first place.

That said, we will work with the folks who have had concerns and see if
we are on the same page w.r.t their thoughts. This is a pending action
from our side.

> 3) issue a WGLC once consensus is determined for the socket
>    option issue

Sounds good to me.

Thanks,
-Anantha
>