Re: Simplifying our processes: Conference Calls

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 03 December 2012 16:07 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACB5E21F8639 for <ietf@ietfa.amsl.com>; Mon, 3 Dec 2012 08:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.672
X-Spam-Level:
X-Spam-Status: No, score=-101.672 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ES1VpLyfx7ta for <ietf@ietfa.amsl.com>; Mon, 3 Dec 2012 08:07:22 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 0310C21F8599 for <ietf@ietf.org>; Mon, 3 Dec 2012 08:07:21 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id dr13so1272802wgb.13 for <ietf@ietf.org>; Mon, 03 Dec 2012 08:07:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=51vAV/ECqf8o8MlVdlQgS6mJv0F4sgAcsMidOQXTAlY=; b=CHlnUOiUZCEn8VkokWl3FNdCOJhIu3d3qwB0MjjziS/Q5gY+BNkeX61kZKGblV8Wjk pX2gzonO6ttlp+ob22tq2AWrXnnwesi08kwzK3WQxqZDdMxn5ZD2WYAItEqXIw1k+5nX d1A6TtrxqHmV+6BYCWkvkq2W6RwO1j/JUBJ0TcKKhAWkagrosd0VZbi8IRdq/7zlwBNQ 4pg1YUjKabTPfL/UUCBUjQjpe6UCS1lW/92Nty5qadPZTm4iuczjc8K2guOdcANITqzt fDu8js279Bmy4l8xpA3J0RY9HDEGNi08u6UpypiMtIFro2eluvmqIESLoD35oQPq11Wh FkDg==
Received: by 10.216.212.2 with SMTP id x2mr3601217weo.32.1354550833121; Mon, 03 Dec 2012 08:07:13 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-71.as13285.net. [2.102.218.71]) by mx.google.com with ESMTPS id s12sm11506279wik.11.2012.12.03.08.07.11 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 08:07:12 -0800 (PST)
Message-ID: <50BCCE1D.5070001@gmail.com>
Date: Mon, 03 Dec 2012 16:06:53 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Simplifying our processes: Conference Calls
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
In-Reply-To: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 03 Dec 2012 16:07:23 -0000

On 03/12/2012 15:41, Hannes Tschofenig wrote:
> Hi all, 
> 
> seeing all these discussions related to process improvements I just noticed one annoying thing related to working group conference calls. 
> 
> It turns out that the IESG guidelines on that topic (see http://www.ietf.org/iesg/statement/interim-meetings.html) say the following: 
> "
> * Conference calls and jabber sessions must be announced at least two weeks prior to the call or session, and the agenda must be published at least one week before call or session
> 
> * Announcement text must be sent to iesg-secretary@ietf.org
> "
> 
> Having just scheduled conference calls for the OAuth mailing list I announced them on the OAuth WG mailing list (where I naively thought it belongs and forgot to re-read the IESG guidelines again). 
> 
> Why do we need to announce conference calls (or Jabber chats) on the IETF announce mailing list? How likely is it that someone cares about a working group effort, does not subscribe to the WG mailing list, has not seen a poll about the date and time, and wants to participate in the conference call? To me - this seems rather unlikely. 

The point is that we work in public, so the whole community should know.
I regularly attend WG meetings where I am not subscribed - it's one of the
side benefits of the week-long meetings - and who's to say that I might not
want to drop into OAuth too?

Suppose I happened to notice (I am making this up) that the foobar WG has
decided to use the IPv6 Flow Label for an unintended purpose? I'd like
to know if they are going to have a conf call, so that I can explain
RFC 6437 to them. Otherwise, I have no interest in foobar.

> Could we please change that? 

I hope not.

    Brian

> 
> Ciao
> Hannes
> 
>