Re: Structure of IETF meeting weeks

Dave Crocker <dhc@dcrocker.net> Wed, 19 April 2017 16:23 UTC

Return-Path: <dhc@dcrocker.net>
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 852601293E9 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 SyFG7wM5OJhJ for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:23:04 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8B5C128CB9 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:23:04 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v3JGPD4k017170 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Apr 2017 09:25:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1492619114; bh=5OJDfNo6rzCVm+jD5wCojMCLe3VNsbyc4Yxe+xBGPuo=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To:From; b=mGyey36Y8Tr9BvE+r7Bg/WBSlxfdEj0W11OCh5NDEIJi3W9EYG/odM0mNsT1OOS1D DM6OHNNtGA2KLsktbpomFwT8rVzkcbhZOJwO00kDD9koUr4yP0hSFU07cpI87wGTRs 8GxVhv01ai9ra/lnwzwAc+GHUxHVnef6HCXdTpWo=
Reply-To: dcrocker@bbiw.net
Subject: Re: Structure of IETF meeting weeks
To: joel jaeggli <joelja@bogus.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Toerless Eckert <tte@cs.fau.de>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
References: <AF3B5F0A-EEA7-402D-B61E-EDE6CE2AE16C@tzi.org> <8546635c-f838-e7f7-a5ec-3a855a14c0f9@dcrocker.net> <20170411232408.GE48535@verdi> <15694.1491965723@obiwan.sandelman.ca> <f1481391-b477-0596-d8ea-adc02ec48e94@pi.nu> <10890.1492007455@obiwan.sandelman.ca> <04c5e6a6-fe92-20ca-f01e-5c2d17dc6022@gmail.com> <9609909d-f631-4651-23a0-c7267bc3b7f5@joelhalpern.com> <87inm6uhet.fsf@chopps.org> <6566.1492264901@obiwan.sandelman.ca> <20170418212254.GB5937@faui40p.informatik.uni-erlangen.de> <d6efee1c-fc7c-a402-d7b2-a13082f8479c@cs.tcd.ie> <b102cda8-d42a-81b7-42ca-cc345eeef922@bogus.com> <467e6b73-274a-8142-0d1d-54cf1197efc0@dcrocker.net> <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <f86fa6f8-305c-c85f-b363-516620946817@dcrocker.net>
Date: Wed, 19 Apr 2017 09:22:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <e92edc66-f92b-5160-54ae-13aea988f479@bogus.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tOvEF0wjovtU_ZUte5QEY-elHF4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 19 Apr 2017 16:23:05 -0000

On 4/19/2017 9:16 AM, joel jaeggli wrote:
> As an AD I was relatively assiduous at working with my chairs to cancel
> working group slots where the agenda/acitivity didn't justify meeting
> (beyond the case of the empty agenda that's probably somewhat subjective).


Thanks for checking off that script requirement in this sequence.  When 
discussing such management issues on the we always get one or more 
postings following the template "my management oversight did/does what 
you are suggesting".

As always, individual anecdotes have nothing to do with patterns of 
concern.  It's not that they are untrue, it's that they are a single 
datum, which never explains or resolves a pattern.

Note, for example Ted Lemon's view that meaningful filtering isn't 
possible due to individual differences in defining an applying criteria.

All of this, of course, provides continuing comfort in taking no action 
to manage the week's time better.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net