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

Joe Touch <touch@isi.edu> Fri, 02 May 2014 20:34 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 E209B1A6FAE for <tcpm@ietfa.amsl.com>; Fri, 2 May 2014 13:34:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.85
X-Spam-Level:
X-Spam-Status: No, score=-4.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 1siVP44E7Jw2 for <tcpm@ietfa.amsl.com>; Fri, 2 May 2014 13:34:39 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 150591A6F38 for <tcpm@ietf.org>; Fri, 2 May 2014 13:34:39 -0700 (PDT)
Received: from [10.78.182.222] (mobile-198-228-210-217.mycingular.net [198.228.210.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s42KXi1s011425 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 2 May 2014 13:33:54 -0700 (PDT)
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> <5363B397.8090009@isi.edu> <CAO249yeyr5q21-=e6p5azwULOh1_jUsniZ6YPcDYd69av8MMYw@mail.gmail.com>
In-Reply-To: <CAO249yeyr5q21-=e6p5azwULOh1_jUsniZ6YPcDYd69av8MMYw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="Apple-Mail-9C539E1E-8648-43FF-8C0B-32ACD8F11083"
Message-Id: <DCC98F94-EA74-4AAA-94AE-E399A405AF13@isi.edu>
X-Mailer: iPhone Mail (11D201)
From: Joe Touch <touch@isi.edu>
Date: Fri, 02 May 2014 13:33:46 -0700
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
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/S2V38TRcnQJokIRQ4ZV0SqXnAAU
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 20:34:41 -0000


> On May 2, 2014, at 1:27 PM, Yoshifumi Nishida <nishida@sfc.wide.ad.jp> wrote:
> 
> Hi Joe,
> 
>> On Fri, May 2, 2014 at 8:02 AM, Joe Touch <touch@isi.edu> wrote:
>> 
>> 
>>> 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
> 
> I personally would like to put a line between c. and d. like:
>            c1. gauge consensus from both the list and the meetings
> I think having two ways to gauge consensus is good thing.

It's good but should not be required.  Meeting attendance isn't required and officially all IETF business is supposed to happen on the list. So holding up work to involve meetings should not ever happen IMO. 

Joe


> --
> Yoshi
>