Re: [tcpm] New Version Notification for draft-touch-tcpm-tcp-edo-01.txt

Joe Touch <touch@isi.edu> Fri, 02 May 2014 15:03 UTC

Return-Path: <touch@isi.edu>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B81D1A0A0D for <tcpm@ietfa.amsl.com>; Fri, 2 May 2014 08:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ln9TxPaD-jr3 for <tcpm@ietfa.amsl.com>; Fri, 2 May 2014 08:03:31 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 118001A08DA for <tcpm@ietf.org>; Fri, 2 May 2014 08:03:31 -0700 (PDT)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s42F2j5h016777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 2 May 2014 08:02:54 -0700 (PDT)
Message-ID: <5363B397.8090009@isi.edu>
Date: Fri, 02 May 2014 08:02:47 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>, Pasi Sarolahti <pasi.sarolahti@iki.fi>
References: <20140425221257.12559.43206.idtracker@ietfa.amsl.com> <2586_1398464386_535ADF82_2586_915_1_535ADF56.9050106@isi.edu> <CF8D8E25-E435-4199-8FD6-3F7066447292@iki.fi> <5363AF84.8090701@mti-systems.com>
In-Reply-To: <5363AF84.8090701@mti-systems.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpm/Mff9WAQ2gEDcmu2kX1N-fiI_iqo
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] New Version Notification for draft-touch-tcpm-tcp-edo-01.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 02 May 2014 15:03:32 -0000


On 5/2/2014 7:45 AM, Wesley Eddy wrote:
> On 5/2/2014 7:18 AM, Pasi Sarolahti wrote:
>>
>> On 26 Apr 2014, at 01:19, Joe Touch <touch@ISI.EDU> wrote:
>>
>>> I'd like to ask the chairs if we can consider a call to make this a
>>> WG doc?
>>>
>>> (given the work of the group is supposed to happen on the list -
>>> and I don't attend meetings in person these days -this doesn't seem
>>> like it needs to wait for a meeting to proceed)
>>
>> We should discuss the possible WG adoption on the list before the
>> meeting, and some people have already voiced their support. But there
>> is value in discussing this in the f2f meeting, too, before
>> confirming WG adoption (hum). Perhaps Wes can present this, or as the
>> last resort the presentation could be proxied by chairs. I don't see
>> any reason to hurry this so that we couldn't wait until the Toronto
>> meeting.
>
> That would be fine with me.  IMO, it would be nice to know what
> the perceived mailing list consensus is, and use the meeting to
> confirm that.  It's only a couple months away.

I'm not in a rush, but as a point of order:

	- work happens on the mailing list, NOT at the meetings

	- decisions at the meeting are confirmed on the list,
	not the other way around

That's why I don't see why we need to wait for the meeting. Meetings are 
places where we typically hash out issues that arise on the list, e.g.:
	a. post to the list
	b. need for interactive clarification arises
	c. meeting supports interactive clarification
	d. decision happens back on the list

Somewhere along the line this all got reversed. I would like to 
encourage the chairs to use case as an opportunity to try the intended 
process.

Joe