Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)

Wesley Eddy <wes@mti-systems.com> Thu, 24 January 2013 05:16 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02A921F8830 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 21:16:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBq9iVHajDG2 for <tcmtf@ietfa.amsl.com>; Wed, 23 Jan 2013 21:16:34 -0800 (PST)
Received: from atl4mhob14.myregisteredsite.com (atl4mhob14.myregisteredsite.com [209.17.115.52]) by ietfa.amsl.com (Postfix) with ESMTP id 02D9F21F8518 for <tcmtf@ietf.org>; Wed, 23 Jan 2013 21:16:33 -0800 (PST)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r0O5GXbm014811 for <tcmtf@ietf.org>; Thu, 24 Jan 2013 00:16:33 -0500
Received: (qmail 11281 invoked by uid 0); 24 Jan 2013 05:16:33 -0000
Received: from unknown (HELO ?172.17.89.224?) (wes@mti-systems.com@12.161.62.194) by 0 with ESMTPA; 24 Jan 2013 05:16:33 -0000
Message-ID: <5100C3A4.2010500@mti-systems.com>
Date: Thu, 24 Jan 2013 00:16:20 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: jsaldana@unizar.es
References: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
In-Reply-To: <007801cdf961$04e78c80$0eb6a580$@unizar.es>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tcmtf@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Martin Stiemerling <Martin.Stiemerling@neclab.eu>
Subject: Re: [tcmtf] Improved version of the TCMTF Charter proposal (v3)
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2013 05:16:34 -0000

On 1/23/2013 6:58 AM, Jose Saldana wrote:
> Hello all.
> 
>  
> 
> After reading the messages in the mailing list, I think we have arrived
> to a solution. Each of the documents has been discussed in a separate
> thread, so I have tried to take everything into account. Documents (A)
> and (B) would be in the Charter. Documents (C) and (D) would only be
> announced as possibilities for re-chartering, and Document (E) can wait
> a little.
> 
> ...


In my opinion, this is decent, though here are two criticisms:

(1) In my opinion, it focuses too much on documents to be produced,
    rather than fully and clearly motivating why the working group
    is needed (i.e. to solve a problem, not to develop documents),
    how it's scope is delimited (i.e. what it *won't* touch isn't
    clear to me, along with what other areas/WGs need to be
    coordinated with), and what the end-goal is.

(2) There's a focus on defining technical solutions prior to the
    mention of fleshing out and totally defining the use cases /
    requirements.  In my opinion, that appears backwards :).

That said, I'm generally supportive of this work.  In my opinion,
as an AD, we would normally feel better having a BoF before forming
a WG, for two reasons (1) to get other areas (e.g. RAI) to be aware
of what's being proposed, and (2) to vet that there really is a
community of stakeholders that are engaged to do the work.  In this
case, I think the 2nd point is evident from the mailing list, and
I don't have a concern about it at all.  I think the 1st point can
be addressed through the responsible AD coordinating with the IESG
and the directorates or area mailing lists that related areas have.
Since I'm going away as an AD though, what really matters at the
moment is what Martin thinks :).

-- 
Wes Eddy
MTI Systems