RE: discussion style and respect

"Tony Hain" <alh-ietf@tndh.net> Sun, 14 June 2015 03:59 UTC

Return-Path: <alh-ietf@tndh.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 588B81A8BBF for <ietf@ietfa.amsl.com>; Sat, 13 Jun 2015 20:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.899
X-Spam-Level:
X-Spam-Status: No, score=0.899 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 qHJv1QlvFI-4 for <ietf@ietfa.amsl.com>; Sat, 13 Jun 2015 20:59:27 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F0121A8BBD for <ietf@ietf.org>; Sat, 13 Jun 2015 20:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tndh.net; s=dkim; h=Subject:Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:In-Reply-To:References:Cc:To:From; bh=sI7Yo7bGpd6DQycYbM3izJRxm225UGpVnZ5+XJhZ2i8=; b=AB8LpOKiKN7lweCizZPRkOsGos30gOAV+gZHvC3ozNE4WppM07Z20uexVO+xKAPkrZs/6JUVITcalJ0JSvBPb36LbIEc+pOEjJAuiCWd492nOZMF2nr1RnXLvPee9tVK+rX0la0+QVyb+G3R5HOANxcuy//ER7RzBhYpSCksJBNbpHQH;
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1Z3z4a-000Nck-8n; Sat, 13 Jun 2015 20:59:24 -0700
From: Tony Hain <alh-ietf@tndh.net>
To: 'Melinda Shore' <melinda.shore@gmail.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, 'John C Klensin' <john-ietf@jck.com>
References: <20150610204037.6837A1ACD25@ietfa.amsl.com> <5578AB4F.3020406@dcrocker.net> <48E1A67CB9CA044EADFEAB87D814BFF632D561D2@eusaamb107.ericsson.se> <20150610215800.867D91B2C4A@ietfa.amsl.com> <CAMm+Lwi5=TfVd26QOx6THXCKsRrgKpi9rHdST5WQZ=Ayzw+sMA@mail.gmail.com> <557A27C5.8030600@gmail.com> <F66440F9-6795-46B6-A4C9-8EFAA4CF79AE@piuha.net> <20150612165256.7E4001ABD3C@ietfa.amsl.com> <557B3C30.602@gmail.com> <132d01d0a580$427d28c0$c7777a40$@tndh.net> <20150613102154.GH23916@verdi> <54BFB0E8D227E8EEF55AF353@JcK-HP8200.jck.com> <557C9116.2080701@gmail.com> <557CA253.5040001@gmail.com>
In-Reply-To: <557CA253.5040001@gmail.com>
Date: Sat, 13 Jun 2015 20:59:04 -0700
Message-ID: <001e01d0a656$74cdff80$5e69fe80$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQG8B3U5pMQA6MciRvF2ZHeOuUjaQQJuIDrrAk42Xg4CbqxqyQI1VriiAO4MQvQBp4LjYgKEKHcLAqCAPnsCGG/X+AK7Sn+MAczXju4B2wpwNgHq8GennPiS8lA=
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
Subject: RE: discussion style and respect
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on express.tndh.net)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GTX6qJ3sH5bTUy_-on4Ov4YtgXc>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Jun 2015 03:59:28 -0000

Melinda Shore wrote:
> On 6/13/15 12:22 PM, Brian E Carpenter wrote:
> > On 14/06/2015 01:19, John C Klensin wrote:
> >> ...   However, if a WG is
> >> started with a "solution" and a group of people behind it, there are
> >> some bad effects:
> > Yes, and this is certainly a very real situation. I've personally
> > experienced it in the past, and am currently experiencing it (without
> > belligerence, fortunately).
> 
> I'm actually pretty ambivalent about this one.  I'd much rather see things
> coming in that are relatively well-baked than see proposals that are just
> problem descriptions.
> It seems to me to be a more productive use of energy to negotiate
> engineering differences than it is go try to figure out whether or not a given
> problem statement reflects an actual problem that somebody is really
> experiencing, or if there's the ability to come up with a useful solution.
> Yes, it can be heated and horrible (and I actually left the IETF for several
> years in part because of my experience along these lines in one particular
> working group), but I think we're better off figuring out how to deal with
> these situations than we are going with the problem statement/ use
> case/gap analysis model, which is really beginning to annoy me as
> unproductive, slow, and unmoored to much that's useful.

If a research team brings in a prototype and 'throws it over the wall' to le the WG refine it, I agree. All too often though a product team brings in a beta, and expects a rubber stamp of their soon to ship product. Those are the times that get heated, because changing the 'requirements' means slowing down the release.

I understand that many people hate the requirements/problem-statement/use-case documents, but without those the spec has no goals. Granted people driving a given solution will have a set in their head, but if you really expect consensus, and particularly if you expect the wider IETF to understand the context, it has to be documented and agreed on by the WG. Contention rooted in a difference of opinion about the requirements / use-cases can be dealt with by letting each faction solve their favorite subset. Saying 'there can be only one true way' will force heated discussions.

Tony

> 
> Melinda