RE: Dedicated list for technical discussions

Dave Cridland <dave@cridland.net> Mon, 30 August 2010 18:42 UTC

Return-Path: <dave@cridland.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51A8E3A682B for <ietf@core3.amsl.com>; Mon, 30 Aug 2010 11:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.546
X-Spam-Level:
X-Spam-Status: No, score=-1.546 tagged_above=-999 required=5 tests=[AWL=-0.806, BAYES_20=-0.74]
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 YNXuG6uxS9rw for <ietf@core3.amsl.com>; Mon, 30 Aug 2010 11:42:05 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by core3.amsl.com (Postfix) with ESMTP id 37C9B3A6814 for <ietf@ietf.org>; Mon, 30 Aug 2010 11:42:05 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 5FC7711680AA; Mon, 30 Aug 2010 19:42:35 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODTU5xE7+lmu; Mon, 30 Aug 2010 19:42:32 +0100 (BST)
Received: from puncture (unknown [217.155.137.60]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 5B12111680A7; Mon, 30 Aug 2010 19:42:32 +0100 (BST)
Subject: RE: Dedicated list for technical discussions
References: <CB2A0C4E-247D-4C82-A947-26F2EBF069F2@mnot.net> <001101cb4751$ef54b460$cdfe1d20$@net>
In-Reply-To: <001101cb4751$ef54b460$cdfe1d20$@net>
MIME-Version: 1.0
Message-Id: <2721.1283193752.367800@puncture>
Date: Mon, 30 Aug 2010 19:42:32 +0100
From: Dave Cridland <dave@cridland.net>
To: Glen Zorn <gwz@net-zen.net>, IETF-Discussion <ietf@ietf.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 30 Aug 2010 18:42:07 -0000

On Sun Aug 29 09:12:31 2010, Glen Zorn wrote:
> Mark Nottingham [mailto://mnot@mnot.net] writes:
> 
> > I know it's been brought up many times before, but I'd appreciate  
> a
> > separate list for technical discussions regarding drafts, etc.,  
> since
> > this list seems to have become a travel tips forum.
> 
> I'm sure that if you have some specific technical topics to discuss  
> at least
> some of us would be willing to join in.  I must note, however, that  
> your own
> posts to this list over the last month or so have been about the  
> Maastrict
> venue, IETF Logo wear and this complaint (not exactly rocket  
> science ;-).

I would note that these items are precisely the kinds of things that  
we, as an organization, are utterly ill-equipped to handle. We cannot  
use our tried and tested bureaucratic techniques to mitigate  
time-consuming discussion - we cannot insist people write a draft,  
propose a BOF, etc before actually discussing the issue.

Therefore, I suggest - and quite seriously, as I assure you I would  
never joke about something so serious as this - that a new area be  
formed forthwith to tackle what's obviously more important than any  
mere technical issue. This new area - perhaps entitled the Hotel  
Organizational Logistic Strategies area, could be home to a number of  
key working groups, aimed at solving these fundamental issues that  
plague us all.

With this in mind, I firmly look forward to seeing a requirements  
document for the area, such that we can progress by initiating BOFs,  
with a view to forming working groups to create further requirement  
documents.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade