From ops-area-bounces@ietf.org  Fri Aug  1 06:55:10 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB2C13A6D9D;
	Fri,  1 Aug 2008 06:55:09 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 86AF13A6938
	for <ops-area@core3.amsl.com>; Fri,  1 Aug 2008 06:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level: 
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=0.225, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 o125N2VJKMRz for <ops-area@core3.amsl.com>;
	Fri,  1 Aug 2008 06:55:02 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175])
	by core3.amsl.com (Postfix) with ESMTP id 2EF2B3A6DA0
	for <ops-area@ietf.org>; Fri,  1 Aug 2008 06:54:39 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob111.postini.com
	([64.18.6.12]) with SMTP; Fri, 01 Aug 2008 06:54:59 PDT
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by p-emsmtp03.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Fri, 1 Aug 2008 06:54:59 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Fri, 1 Aug 2008 09:54:58 -0400
Received: from [172.23.1.182] ([172.23.1.182] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 1 Aug 2008 09:54:57 -0400
Message-ID: <489315AC.1040903@juniper.net>
Date: Fri, 01 Aug 2008 09:54:52 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
In-Reply-To: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 01 Aug 2008 13:54:57.0756 (UTC)
	FILETIME=[2F0A69C0:01C8F3DE]
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the
	session
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Bert,

I apologize for this. If the presenters will send me their slides I will 
post them with the minutes.

                              Ron


Bert Wijnen (IETF) wrote:
> Being a jabber scribe for the OPS area, I clearly see how BAD it
> is if slides are not ONLINE before the meeting starts.
> Also... SLIDES MUST be numbers, and speakers should mention the
> slide numbers.
> 
> I spend considerable amount of time typing slide titles after first 
> having had
> to email slides to remote participants from memory sticks.
> 
> Bert Wijnen
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Fri Aug  1 15:30:13 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 671263A68FB;
	Fri,  1 Aug 2008 15:30:13 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CA453A68FB
	for <ops-area@core3.amsl.com>; Fri,  1 Aug 2008 15:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Level: 
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465, 
	BAYES_00=-2.599]
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 3yqLpiOsdSpC for <ops-area@core3.amsl.com>;
	Fri,  1 Aug 2008 15:30:11 -0700 (PDT)
Received: from relay.versatel.net (relay.versatel.net [62.250.3.110])
	by core3.amsl.com (Postfix) with SMTP id F27773A6873
	for <ops-area@ietf.org>; Fri,  1 Aug 2008 15:30:10 -0700 (PDT)
Received: (qmail 50111 invoked from network); 1 Aug 2008 22:30:23 -0000
Received: from unknown (HELO BertLaptop) (87.215.199.34)
	by relay.versatel.net with SMTP; 1 Aug 2008 22:30:23 -0000
Message-ID: <0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "Ron Bonica" <rbonica@juniper.net>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
	<489315AC.1040903@juniper.net>
In-Reply-To: <489315AC.1040903@juniper.net>
Date: Sat, 2 Aug 2008 00:25:12 +0200
Organization: Consultant
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the
	session
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Let me suggest that if a presenter does not provide his/her presentation at 
the latest 24
hours before the session start, then cancel his/her presentation.

Bert
----- Original Message ----- 
From: "Ron Bonica" <rbonica@juniper.net>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Cc: "ops-area (IETF)" <ops-area@ietf.org>
Sent: Friday, August 01, 2008 3:54 PM
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the 
session


> Bert,
>
> I apologize for this. If the presenters will send me their slides I will 
> post them with the minutes.
>
>                              Ron
>
>
> Bert Wijnen (IETF) wrote:
>> Being a jabber scribe for the OPS area, I clearly see how BAD it
>> is if slides are not ONLINE before the meeting starts.
>> Also... SLIDES MUST be numbers, and speakers should mention the
>> slide numbers.
>>
>> I spend considerable amount of time typing slide titles after first 
>> having had
>> to email slides to remote participants from memory sticks.
>>
>> Bert Wijnen
>>
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-area
>>
>
> 


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Sun Aug  3 22:36:28 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AC9603A6901;
	Sun,  3 Aug 2008 22:36:28 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04B2A3A6870
	for <ops-area@core3.amsl.com>; Sun,  3 Aug 2008 22:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059, 
	BAYES_00=-2.599]
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 QD1pN+amJJBq for <ops-area@core3.amsl.com>;
	Sun,  3 Aug 2008 22:36:26 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1])
	by core3.amsl.com (Postfix) with ESMTP id B79E03A6901
	for <ops-area@ietf.org>; Sun,  3 Aug 2008 22:36:25 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id m745ag4k011259;
	Mon, 4 Aug 2008 08:36:42 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m745aguP011254;
	Mon, 4 Aug 2008 08:36:42 +0300
Date: Mon, 4 Aug 2008 08:36:41 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
In-Reply-To: <0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
Message-ID: <alpine.LRH.1.10.0808040835530.9304@netcore.fi>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
	<489315AC.1040903@juniper.net>
	<0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.93.3/7930/Mon Aug 4 03:09:38 2008 on otso.netcore.fi
X-Virus-Status: Clean
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the
 session
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

On Sat, 2 Aug 2008, Bert Wijnen (IETF) wrote:
> Let me suggest that if a presenter does not provide his/her presentation at 
> the latest 24
> hours before the session start, then cancel his/her presentation.

If we go along this path -- and if the agenda is not uploaded to the 
web a week before the meeting, cancel the meeting :-)

> ----- Original Message ----- From: "Ron Bonica" <rbonica@juniper.net>
> To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
> Cc: "ops-area (IETF)" <ops-area@ietf.org>
> Sent: Friday, August 01, 2008 3:54 PM
> Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the 
> session
>
>
>>  Bert,
>>
>>  I apologize for this. If the presenters will send me their slides I will
>>  post them with the minutes.
>>
>>                               Ron
>> 
>>
>>  Bert Wijnen (IETF) wrote:
>> >  Being a jabber scribe for the OPS area, I clearly see how BAD it
>> >  is if slides are not ONLINE before the meeting starts.
>> >  Also... SLIDES MUST be numbers, and speakers should mention the
>> >  slide numbers.
>> > 
>> >  I spend considerable amount of time typing slide titles after first 
>> >  having had
>> >  to email slides to remote participants from memory sticks.
>> > 
>> >  Bert Wijnen
>> > 
>> >  _______________________________________________
>> >  OPS-AREA mailing list
>> >  OPS-AREA@ietf.org
>> >  https://www.ietf.org/mailman/listinfo/ops-area
>> > 
>>
>> 
>
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 03:01:18 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABEC23A6A18;
	Mon,  4 Aug 2008 03:01:17 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EEB963A6896
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 03:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053, 
	BAYES_00=-2.599]
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 9qqYptRwv1h7 for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 03:01:12 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id 4A62E3A6A8B
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 03:01:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,304,1215403200"; d="scan'208";a="129740342"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 04 Aug 2008 06:01:37 -0400
X-IronPort-AV: E=Sophos;i="4.31,304,1215403200"; d="scan'208";a="250168159"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	04 Aug 2008 06:01:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Aug 2008 12:01:37 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E8E09B@307622ANEX5.global.avaya.com>
In-Reply-To: <alpine.LRH.1.10.0808040835530.9304@netcore.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] meeting materials MUST be online well BEFORE the
	session
Thread-Index: Acj19Bzo+IRRpcDiTYqNKxAbzWJtxwAJFxgw
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
	<alpine.LRH.1.10.0808040835530.9304@netcore.fi>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Pekka Savola" <pekkas@netcore.fi>,
	"Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the
	session
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

 

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Pekka Savola
> Sent: Monday, August 04, 2008 8:37 AM
> To: Bert Wijnen (IETF)
> Cc: ops-area (IETF)
> Subject: Re: [OPS-AREA] meeting materials MUST be online well 
> BEFORE the session
> 
> On Sat, 2 Aug 2008, Bert Wijnen (IETF) wrote:
> > Let me suggest that if a presenter does not provide his/her 
> > presentation at the latest 24 hours before the session start, then 
> > cancel his/her presentation.
> 
> If we go along this path -- and if the agenda is not uploaded 
> to the web a week before the meeting, cancel the meeting :-)
> 

I would actually drop the smiley and entertain such an idea. I find
practically impossible for someone to prepare for a meeting if the
agenda is not posted less than a week before the meeting. Of course,
changes should be allowed until the last day, but the main items on the
agenda, and the preliminary reading materials list can be made available
one week in advance. 

Please allow to Ron and me to compile these proposals and get back with
a proposal submitted for community consensus. 

Dan
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 04:33:07 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 205DC3A6C89;
	Mon,  4 Aug 2008 04:33:07 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AF583A6C5B
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 04:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.399
X-Spam-Level: 
X-Spam-Status: No, score=-3.399 tagged_above=-999 required=5
	tests=[AWL=-0.800, BAYES_00=-2.599]
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 cpV8f68-YUnl for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 04:21:00 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net
	[217.115.75.234])
	by core3.amsl.com (Postfix) with ESMTP id 616743A6C89
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 04:20:12 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56])
	by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id
	m74BKXiX010931
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Aug 2008 13:20:33 +0200
Received: from demuexc022.nsn-intra.net (webmail.nsn-intra.net [10.150.128.35])
	by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP
	id m74BKXGj009466; Mon, 4 Aug 2008 13:20:33 +0200
Received: from DEMUEXC005.nsn-intra.net ([10.150.128.17]) by
	demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 4 Aug 2008 13:20:33 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Aug 2008 13:20:31 +0200
Message-ID: <A294F5A3E722D94FBEB6D49C1506F6F7EA6020@DEMUEXC005.nsn-intra.net>
In-Reply-To: <0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
Thread-Index: Acj0Jj9c4Dl+CzZSRvG6r7DfSRcmvgB/NlfQ
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net>
	<0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
From: "Ersue, Mehmet (NSN - DE/Muenich)" <mehmet.ersue@nsn.com>
To: "ext Bert Wijnen (IETF)" <bertietf@bwijnen.net>,
	"ops-area (IETF)" <ops-area@ietf.org>
X-OriginalArrivalTime: 04 Aug 2008 11:20:33.0182 (UTC)
	FILETIME=[1C29DBE0:01C8F624]
X-Mailman-Approved-At: Mon, 04 Aug 2008 04:33:06 -0700
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org


+1

It is not helpful for remote attendees and is actually too 
late if the presenter shows up in the last second with a 
USB stick.

OTOH the WG chairs should take a look on the slides 
before the session and request changes if the slides are 
not appropriate (e.g. tutorial instead of issue discussion, 
too many slides for the time available in the session slot).

We need to find a way to force early provision of the 
presentation slides to the meeting material site.

Cheers, 
Mehmet
 

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of ext Bert Wijnen (IETF)
> Sent: Saturday, August 02, 2008 12:25 AM
> To: Ron Bonica
> Cc: ops-area (IETF)
> Subject: Re: [OPS-AREA] meeting materials MUST be online well 
> BEFORE thesession
> 
> Let me suggest that if a presenter does not provide his/her 
> presentation at 
> the latest 24
> hours before the session start, then cancel his/her presentation.
> 
> Bert
> ----- Original Message ----- 
> From: "Ron Bonica" <rbonica@juniper.net>
> To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
> Cc: "ops-area (IETF)" <ops-area@ietf.org>
> Sent: Friday, August 01, 2008 3:54 PM
> Subject: Re: [OPS-AREA] meeting materials MUST be online well 
> BEFORE the 
> session
> 
> 
> > Bert,
> >
> > I apologize for this. If the presenters will send me their 
> slides I will 
> > post them with the minutes.
> >
> >                              Ron
> >
> >
> > Bert Wijnen (IETF) wrote:
> >> Being a jabber scribe for the OPS area, I clearly see how BAD it
> >> is if slides are not ONLINE before the meeting starts.
> >> Also... SLIDES MUST be numbers, and speakers should mention the
> >> slide numbers.
> >>
> >> I spend considerable amount of time typing slide titles 
> after first 
> >> having had
> >> to email slides to remote participants from memory sticks.
> >>
> >> Bert Wijnen
> >>
> >> _______________________________________________
> >> OPS-AREA mailing list
> >> OPS-AREA@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ops-area
> >>
> >
> > 
> 
> 
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 05:19:11 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18D9C3A6CA0;
	Mon,  4 Aug 2008 05:19:11 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0F603A6C9F
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 05:19:09 -0700 (PDT)
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=[AWL=0.000, 
	BAYES_00=-2.599]
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 pT8xK+WECNk1 for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 05:19:08 -0700 (PDT)
Received: from QMTA02.emeryville.ca.mail.comcast.net
	(qmta02.emeryville.ca.mail.comcast.net [76.96.30.24])
	by core3.amsl.com (Postfix) with ESMTP id D7C8D3A68BE
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 05:19:08 -0700 (PDT)
Received: from OMTA05.emeryville.ca.mail.comcast.net ([76.96.30.43])
	by QMTA02.emeryville.ca.mail.comcast.net with comcast
	id yAvb1Z0080vp7WLA2CKdHa; Mon, 04 Aug 2008 12:19:37 +0000
Received: from Harrington73653 ([24.128.66.199])
	by OMTA05.emeryville.ca.mail.comcast.net with comcast
	id yCKa1Z0054HwxpC8RCKbsS; Mon, 04 Aug 2008 12:19:36 +0000
X-Authority-Analysis: v=1.0 c=1 a=cFV7fDH4X3AA:10 a=gbrI5vREOLoA:10
	a=48vgC7mUAAAA:8 a=n_E3HDN86VBhtZkiTK0A:9 a=ZBuqkeNfD8Gef3MIEwwA:7
	a=W2AzGM4v0Wd8dzw9FNNtbyMux-MA:4 a=si9q_4b84H0A:10 a=hPjdaMEvmhQA:10
	a=lZB815dzVvQA:10 a=50e4U0PicR4A:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	"'Pekka Savola'" <pekkas@netcore.fi>,
	"'Bert Wijnen \(IETF\)'" <bertietf@bwijnen.net>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop><alpine.LRH.1.10.0808040835530.9304@netcore.fi>
	<EDC652A26FB23C4EB6384A4584434A04E8E09B@307622ANEX5.global.avaya.com>
Date: Mon, 4 Aug 2008 13:19:34 +0100
Message-ID: <009201c8f62c$5c4663d0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04E8E09B@307622ANEX5.global.avaya.com>
Thread-Index: Acj19Bzo+IRRpcDiTYqNKxAbzWJtxwAJFxgwAALVVbA=
Cc: "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi,

I think we should focus more on carrots than sticks. This is a
volunteer organization.
My name is Dave and I am a sinner.

Sometimes the chairs get tied up with day-job work and have difficulty
finding time to focus on writing up an agenda. Sometimes the chairs
need to wait until they get input from volunteers about presentations
that will will be done before setting up an agenda. Do you recommend
posting empty agendas so that the deadline is met, and then editing it
later when we have content?

Have you thought about the unintended consequences of a rule that
prevents a WG from meeting or discussing a particular topic if the
agenda and materials are not posted in advance? What will be the
consequences if volunteers spend money to travel to an IETF meeting,
only to find that their only session has been cancelled because a
chair was tied down with day-job work, or they could not work on
resolving the issues because the presentation didn't get posted? Will
they continue to travel to IETF meetings? Will they request new
chairs? Where will we get new chairs that are not burdened by day-job
demands? Will the WG accomplish better standards, or get them done
faster, as a result of such rules?

My WG didn't get an early agenda posted because one chair was
travelling internationally for day-job work for the month prior to
Dublin (justifying funding of a team to work on IETF standards), and
the other was on a 3.5 week vacation with his family. Which of those
should we have given up to ensure that the agenda was posted more than
a week in advance? Should we resign as chairs because we cannot
guarantee timely delivery of the agenda? Should the whole WG suffer by
having its sessions cancelled because the chairs faced competing real
world priorities?

We were also guilty of not posting the presentations well in advance.
We had to wait for the presentations to be written, which usually
happened within 24 hours of when the presentation would be delivered.
The content of those presentations was sometimes impacted by the f2f
discussions that occurred during the IETF week, including during
evening bar time when compromises were worked out between major
contributors on open issues.

Some chairs had problems with connectivity. I know my co-chair could
not access the web during our first session, so he could not even
access the meeting materials himself. I had spotty connectivity; I
frequently did not get emails from my co-chair or the contributors for
hours after they were sent to me, so I did not have access to the
presentations or to the meeting materials page on a timely basis.
Should the WG session be cancelled or the topic be banned because the
network connectivity was not always perfect enough to ensure postings
at least 24 hours in advance?

I would be very careful about trying to legislate too much and to
penalize whole WGs because the chairs failed to post meeting materials
on time. I think the cure would be worse than the problem.

I know I failed to post on a timely basis this time, and I will try to
do better in the future, although some are real-world obstacles beyond
my control. If you start punishing the whole WG for late postings by
the chairs, I will probably just ask you to find a new chair.

David Harrington
dbharrington@comcast.net
ietfdbh@comcast.net
dharrington@huawei.com

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: Monday, August 04, 2008 11:02 AM
> To: Pekka Savola; Bert Wijnen (IETF)
> Cc: ops-area (IETF)
> Subject: Re: [OPS-AREA] meeting materials MUST be online well 
> BEFORE thesession
> 
>  
> 
> > -----Original Message-----
> > From: ops-area-bounces@ietf.org 
> > [mailto:ops-area-bounces@ietf.org] On Behalf Of Pekka Savola
> > Sent: Monday, August 04, 2008 8:37 AM
> > To: Bert Wijnen (IETF)
> > Cc: ops-area (IETF)
> > Subject: Re: [OPS-AREA] meeting materials MUST be online well 
> > BEFORE the session
> > 
> > On Sat, 2 Aug 2008, Bert Wijnen (IETF) wrote:
> > > Let me suggest that if a presenter does not provide his/her 
> > > presentation at the latest 24 hours before the session 
> start, then 
> > > cancel his/her presentation.
> > 
> > If we go along this path -- and if the agenda is not uploaded 
> > to the web a week before the meeting, cancel the meeting :-)
> > 
> 
> I would actually drop the smiley and entertain such an idea. I find
> practically impossible for someone to prepare for a meeting if the
> agenda is not posted less than a week before the meeting. Of course,
> changes should be allowed until the last day, but the main 
> items on the
> agenda, and the preliminary reading materials list can be 
> made available
> one week in advance. 
> 
> Please allow to Ron and me to compile these proposals and get 
> back with
> a proposal submitted for community consensus. 
> 
> Dan
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 06:33:36 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 503543A68FB;
	Mon,  4 Aug 2008 06:33:36 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A9E863A68FB
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 06:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051, 
	BAYES_00=-2.599]
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 ygwdmFaLGwbr for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 06:33:34 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 46DA13A684B
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 06:33:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,304,1215403200"; d="scan'208";a="138068728"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 04 Aug 2008 09:34:00 -0400
X-IronPort-AV: E=Sophos;i="4.31,304,1215403200"; d="scan'208";a="243399585"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	04 Aug 2008 09:33:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Aug 2008 15:33:53 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E8E151@307622ANEX5.global.avaya.com>
In-Reply-To: <009201c8f62c$5c4663d0$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
Thread-Index: Acj19Bzo+IRRpcDiTYqNKxAbzWJtxwAJFxgwAALVVbAABBxMUA==
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop><alpine.LRH.1.10.0808040835530.9304@netcore.fi>
	<EDC652A26FB23C4EB6384A4584434A04E8E09B@307622ANEX5.global.avaya.com>
	<009201c8f62c$5c4663d0$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>,
	"Pekka Savola" <pekkas@netcore.fi>,
	"Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi David,

Wow, I think that I pushed a red-hot button :-) 

Let me try to address the issues that you are raising. We all want to
make the standards process work better and faster, get more people
involved and motivated and issue better standards at the end of the
process. The intent of such rules would not be to punish and to exclude
but to make agendas and materials available in advance for people to be
more efficient at the meeting. I believe that at the meeting last week
some people could not prepare well because agendas (not only from your
WG) came too late, and the remote participation lacked efficiency
because many presentations were not available even by the time the
meetings started.  

My experience is that if rules are in place and known in advance
responsible people do their best in order to respect them. In the case
of your WG if the one week agenda rule was in advance I am sure that you
and David would have done the best to submit a preliminary agenda by the
deadline, or would have announced the WG and the AD before traveling
'look, we are traveling this period for such and such reasons,
preliminary agenda will not be available on the Monday deadline but only
Wednesday before the meeting'. Being predictive is what we seek here,
being able for all participants in the process to plan and allow the
best possible fairness and preparation time is what we seek. 

There are always exceptions and life situations that make some deadlines
impossible to match. For these purposes all the IETF systems or the
majority of them accept human override with proper approval level. In
the case such rules will be adopted in the future, ADs will have the
capability of accepting agendas after the deadline and WG chairs will be
able to accept presentations or updates even in the last 24 hours before
the meeting. However, this would be an exception, the rule would be that
agendas and presentations need to be submitted in time, and I am sure
that the majority of the volunteers who are all on both provider and
receiver roles will make the rules work in most cases. 

Regards,

Dan

BTW - you criticized my use of some kind of stick menace, but you did
not suggest any carrot. I would love a carrot-only based system if
somebody can come with one. 



> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net] 
> Sent: Monday, August 04, 2008 3:20 PM
> To: Romascanu, Dan (Dan); 'Pekka Savola'; 'Bert Wijnen (IETF)'
> Cc: 'ops-area (IETF)'
> Subject: RE: [OPS-AREA] meeting materials MUST be online well 
> BEFORE thesession
> 
> Hi,
> 
> I think we should focus more on carrots than sticks. This is 
> a volunteer organization.
> My name is Dave and I am a sinner.
> 
> Sometimes the chairs get tied up with day-job work and have 
> difficulty finding time to focus on writing up an agenda. 
> Sometimes the chairs need to wait until they get input from 
> volunteers about presentations that will will be done before 
> setting up an agenda. Do you recommend posting empty agendas 
> so that the deadline is met, and then editing it later when 
> we have content?
> 
> Have you thought about the unintended consequences of a rule 
> that prevents a WG from meeting or discussing a particular 
> topic if the agenda and materials are not posted in advance? 
> What will be the consequences if volunteers spend money to 
> travel to an IETF meeting, only to find that their only 
> session has been cancelled because a chair was tied down with 
> day-job work, or they could not work on resolving the issues 
> because the presentation didn't get posted? Will they 
> continue to travel to IETF meetings? Will they request new 
> chairs? Where will we get new chairs that are not burdened by 
> day-job demands? Will the WG accomplish better standards, or 
> get them done faster, as a result of such rules?
> 
> My WG didn't get an early agenda posted because one chair was 
> travelling internationally for day-job work for the month 
> prior to Dublin (justifying funding of a team to work on IETF 
> standards), and the other was on a 3.5 week vacation with his 
> family. Which of those should we have given up to ensure that 
> the agenda was posted more than a week in advance? Should we 
> resign as chairs because we cannot guarantee timely delivery 
> of the agenda? Should the whole WG suffer by having its 
> sessions cancelled because the chairs faced competing real 
> world priorities?
> 
> We were also guilty of not posting the presentations well in advance.
> We had to wait for the presentations to be written, which 
> usually happened within 24 hours of when the presentation 
> would be delivered.
> The content of those presentations was sometimes impacted by 
> the f2f discussions that occurred during the IETF week, 
> including during evening bar time when compromises were 
> worked out between major contributors on open issues.
> 
> Some chairs had problems with connectivity. I know my 
> co-chair could not access the web during our first session, 
> so he could not even access the meeting materials himself. I 
> had spotty connectivity; I frequently did not get emails from 
> my co-chair or the contributors for hours after they were 
> sent to me, so I did not have access to the presentations or 
> to the meeting materials page on a timely basis.
> Should the WG session be cancelled or the topic be banned 
> because the network connectivity was not always perfect 
> enough to ensure postings at least 24 hours in advance?
> 
> I would be very careful about trying to legislate too much 
> and to penalize whole WGs because the chairs failed to post 
> meeting materials on time. I think the cure would be worse 
> than the problem.
> 
> I know I failed to post on a timely basis this time, and I 
> will try to do better in the future, although some are 
> real-world obstacles beyond my control. If you start 
> punishing the whole WG for late postings by the chairs, I 
> will probably just ask you to find a new chair.
> 
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
> dharrington@huawei.com
> 
> > -----Original Message-----
> > From: ops-area-bounces@ietf.org
> > [mailto:ops-area-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> > Sent: Monday, August 04, 2008 11:02 AM
> > To: Pekka Savola; Bert Wijnen (IETF)
> > Cc: ops-area (IETF)
> > Subject: Re: [OPS-AREA] meeting materials MUST be online 
> well BEFORE 
> > thesession
> > 
> >  
> > 
> > > -----Original Message-----
> > > From: ops-area-bounces@ietf.org
> > > [mailto:ops-area-bounces@ietf.org] On Behalf Of Pekka Savola
> > > Sent: Monday, August 04, 2008 8:37 AM
> > > To: Bert Wijnen (IETF)
> > > Cc: ops-area (IETF)
> > > Subject: Re: [OPS-AREA] meeting materials MUST be online 
> well BEFORE 
> > > the session
> > > 
> > > On Sat, 2 Aug 2008, Bert Wijnen (IETF) wrote:
> > > > Let me suggest that if a presenter does not provide his/her 
> > > > presentation at the latest 24 hours before the session
> > start, then
> > > > cancel his/her presentation.
> > > 
> > > If we go along this path -- and if the agenda is not 
> uploaded to the 
> > > web a week before the meeting, cancel the meeting :-)
> > > 
> > 
> > I would actually drop the smiley and entertain such an idea. I find 
> > practically impossible for someone to prepare for a meeting if the 
> > agenda is not posted less than a week before the meeting. 
> Of course, 
> > changes should be allowed until the last day, but the main items on 
> > the agenda, and the preliminary reading materials list can be made 
> > available one week in advance.
> > 
> > Please allow to Ron and me to compile these proposals and get back 
> > with a proposal submitted for community consensus.
> > 
> > Dan
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> > 
> 
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 06:49:58 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BD31728C2A4;
	Mon,  4 Aug 2008 06:49:58 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC7B728C2A0
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 06:49:57 -0700 (PDT)
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.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lvu8wbdkuIVk for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 06:49:52 -0700 (PDT)
Received: from QMTA10.emeryville.ca.mail.comcast.net
	(qmta10.emeryville.ca.mail.comcast.net [76.96.30.17])
	by core3.amsl.com (Postfix) with ESMTP id 8C74228C2A2
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 06:49:52 -0700 (PDT)
Received: from OMTA01.emeryville.ca.mail.comcast.net ([76.96.30.11])
	by QMTA10.emeryville.ca.mail.comcast.net with comcast
	id yAtl1Z0070EPchoAADqLjq; Mon, 04 Aug 2008 13:50:20 +0000
Received: from Harrington73653 ([24.128.66.199])
	by OMTA01.emeryville.ca.mail.comcast.net with comcast
	id yDqJ1Z00F4HwxpC8MDqJiM; Mon, 04 Aug 2008 13:50:20 +0000
X-Authority-Analysis: v=1.0 c=1 a=cFV7fDH4X3AA:10 a=gbrI5vREOLoA:10
	a=48vgC7mUAAAA:8 a=JNQPh5K-9wdwOv2mEgYA:9 a=oVqfggwBVUljUvKoLmEA:7
	a=NcY2iXQzwvOCJ7pR772fND33JH8A:4 a=4dyfk4FV-b8A:10 a=si9q_4b84H0A:10
	a=hPjdaMEvmhQA:10 a=lZB815dzVvQA:10 a=50e4U0PicR4A:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	"'Pekka Savola'" <pekkas@netcore.fi>,
	"'Bert Wijnen \(IETF\)'" <bertietf@bwijnen.net>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop><alpine.LRH.1.10.0808040835530.9304@netcore.fi>
	<EDC652A26FB23C4EB6384A4584434A04E8E09B@307622ANEX5.global.avaya.com>
	<009201c8f62c$5c4663d0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A04E8E151@307622ANEX5.global.avaya.com>
Date: Mon, 4 Aug 2008 09:50:16 -0400
Message-ID: <009301c8f639$08415fd0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04E8E151@307622ANEX5.global.avaya.com>
Thread-Index: Acj19Bzo+IRRpcDiTYqNKxAbzWJtxwAJFxgwAALVVbAABBxMUAAAzS+w
Cc: "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi Dan,

IETF volunteers are here to produce standards. That is not always a
fun thing to do, and the sloeness of IETF work is extrememly
frustrating, but moist of our main volunteer contributors do this work
because they believe in the benefits of an open and fair volunteer
process of standards development. Some even get paid to do it; many do
not. Helping to develop a better Internet by working on standards
**is** the carrot. 

The discussion "hey, folks, it is hard for remote contributors to
participate effectively if the agendas and/or the presentations are
posted too late" focuses on the carrot; when agendas and presentations
are not posted early enough, if skews the process and makes the WG
less effective - it affects the carrot.

When the discussion removed the smiley and started talking about
punative actions - cancelling sessions and removing presentations from
the sessions, then you turned the discussion into a "stick" discussion
rather than a carrot discussion.

dbh

> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com] 
> Sent: Monday, August 04, 2008 9:34 AM
> To: David Harrington; Pekka Savola; Bert Wijnen (IETF)
> Cc: ops-area (IETF)
> Subject: RE: [OPS-AREA] meeting materials MUST be online well 
> BEFORE thesession
> 
> Hi David,
> 
> Wow, I think that I pushed a red-hot button :-) 
> 
> Let me try to address the issues that you are raising. We all want
to
> make the standards process work better and faster, get more people
> involved and motivated and issue better standards at the end of the
> process. The intent of such rules would not be to punish and 
> to exclude
> but to make agendas and materials available in advance for 
> people to be
> more efficient at the meeting. I believe that at the meeting last
week
> some people could not prepare well because agendas (not only from
your
> WG) came too late, and the remote participation lacked efficiency
> because many presentations were not available even by the time the
> meetings started.  
> 
> My experience is that if rules are in place and known in advance
> responsible people do their best in order to respect them. In the
case
> of your WG if the one week agenda rule was in advance I am 
> sure that you
> and David would have done the best to submit a preliminary 
> agenda by the
> deadline, or would have announced the WG and the AD before traveling
> 'look, we are traveling this period for such and such reasons,
> preliminary agenda will not be available on the Monday 
> deadline but only
> Wednesday before the meeting'. Being predictive is what we seek
here,
> being able for all participants in the process to plan and allow the
> best possible fairness and preparation time is what we seek. 
> 
> There are always exceptions and life situations that make 
> some deadlines
> impossible to match. For these purposes all the IETF systems or the
> majority of them accept human override with proper approval level.
In
> the case such rules will be adopted in the future, ADs will have the
> capability of accepting agendas after the deadline and WG 
> chairs will be
> able to accept presentations or updates even in the last 24 
> hours before
> the meeting. However, this would be an exception, the rule 
> would be that
> agendas and presentations need to be submitted in time, and I am
sure
> that the majority of the volunteers who are all on both provider and
> receiver roles will make the rules work in most cases. 
> 
> Regards,
> 
> Dan
> 
> BTW - you criticized my use of some kind of stick menace, but you
did
> not suggest any carrot. I would love a carrot-only based system if
> somebody can come with one. 
> 
> 
> 
> > -----Original Message-----
> > From: David Harrington [mailto:ietfdbh@comcast.net] 
> > Sent: Monday, August 04, 2008 3:20 PM
> > To: Romascanu, Dan (Dan); 'Pekka Savola'; 'Bert Wijnen (IETF)'
> > Cc: 'ops-area (IETF)'
> > Subject: RE: [OPS-AREA] meeting materials MUST be online well 
> > BEFORE thesession
> > 
> > Hi,
> > 
> > I think we should focus more on carrots than sticks. This is 
> > a volunteer organization.
> > My name is Dave and I am a sinner.
> > 
> > Sometimes the chairs get tied up with day-job work and have 
> > difficulty finding time to focus on writing up an agenda. 
> > Sometimes the chairs need to wait until they get input from 
> > volunteers about presentations that will will be done before 
> > setting up an agenda. Do you recommend posting empty agendas 
> > so that the deadline is met, and then editing it later when 
> > we have content?
> > 
> > Have you thought about the unintended consequences of a rule 
> > that prevents a WG from meeting or discussing a particular 
> > topic if the agenda and materials are not posted in advance? 
> > What will be the consequences if volunteers spend money to 
> > travel to an IETF meeting, only to find that their only 
> > session has been cancelled because a chair was tied down with 
> > day-job work, or they could not work on resolving the issues 
> > because the presentation didn't get posted? Will they 
> > continue to travel to IETF meetings? Will they request new 
> > chairs? Where will we get new chairs that are not burdened by 
> > day-job demands? Will the WG accomplish better standards, or 
> > get them done faster, as a result of such rules?
> > 
> > My WG didn't get an early agenda posted because one chair was 
> > travelling internationally for day-job work for the month 
> > prior to Dublin (justifying funding of a team to work on IETF 
> > standards), and the other was on a 3.5 week vacation with his 
> > family. Which of those should we have given up to ensure that 
> > the agenda was posted more than a week in advance? Should we 
> > resign as chairs because we cannot guarantee timely delivery 
> > of the agenda? Should the whole WG suffer by having its 
> > sessions cancelled because the chairs faced competing real 
> > world priorities?
> > 
> > We were also guilty of not posting the presentations well 
> in advance.
> > We had to wait for the presentations to be written, which 
> > usually happened within 24 hours of when the presentation 
> > would be delivered.
> > The content of those presentations was sometimes impacted by 
> > the f2f discussions that occurred during the IETF week, 
> > including during evening bar time when compromises were 
> > worked out between major contributors on open issues.
> > 
> > Some chairs had problems with connectivity. I know my 
> > co-chair could not access the web during our first session, 
> > so he could not even access the meeting materials himself. I 
> > had spotty connectivity; I frequently did not get emails from 
> > my co-chair or the contributors for hours after they were 
> > sent to me, so I did not have access to the presentations or 
> > to the meeting materials page on a timely basis.
> > Should the WG session be cancelled or the topic be banned 
> > because the network connectivity was not always perfect 
> > enough to ensure postings at least 24 hours in advance?
> > 
> > I would be very careful about trying to legislate too much 
> > and to penalize whole WGs because the chairs failed to post 
> > meeting materials on time. I think the cure would be worse 
> > than the problem.
> > 
> > I know I failed to post on a timely basis this time, and I 
> > will try to do better in the future, although some are 
> > real-world obstacles beyond my control. If you start 
> > punishing the whole WG for late postings by the chairs, I 
> > will probably just ask you to find a new chair.
> > 
> > David Harrington
> > dbharrington@comcast.net
> > ietfdbh@comcast.net
> > dharrington@huawei.com
> > 
> > > -----Original Message-----
> > > From: ops-area-bounces@ietf.org
> > > [mailto:ops-area-bounces@ietf.org] On Behalf Of 
> Romascanu, Dan (Dan)
> > > Sent: Monday, August 04, 2008 11:02 AM
> > > To: Pekka Savola; Bert Wijnen (IETF)
> > > Cc: ops-area (IETF)
> > > Subject: Re: [OPS-AREA] meeting materials MUST be online 
> > well BEFORE 
> > > thesession
> > > 
> > >  
> > > 
> > > > -----Original Message-----
> > > > From: ops-area-bounces@ietf.org
> > > > [mailto:ops-area-bounces@ietf.org] On Behalf Of Pekka Savola
> > > > Sent: Monday, August 04, 2008 8:37 AM
> > > > To: Bert Wijnen (IETF)
> > > > Cc: ops-area (IETF)
> > > > Subject: Re: [OPS-AREA] meeting materials MUST be online 
> > well BEFORE 
> > > > the session
> > > > 
> > > > On Sat, 2 Aug 2008, Bert Wijnen (IETF) wrote:
> > > > > Let me suggest that if a presenter does not provide his/her 
> > > > > presentation at the latest 24 hours before the session
> > > start, then
> > > > > cancel his/her presentation.
> > > > 
> > > > If we go along this path -- and if the agenda is not 
> > uploaded to the 
> > > > web a week before the meeting, cancel the meeting :-)
> > > > 
> > > 
> > > I would actually drop the smiley and entertain such an 
> idea. I find 
> > > practically impossible for someone to prepare for a 
> meeting if the 
> > > agenda is not posted less than a week before the meeting. 
> > Of course, 
> > > changes should be allowed until the last day, but the 
> main items on 
> > > the agenda, and the preliminary reading materials list 
> can be made 
> > > available one week in advance.
> > > 
> > > Please allow to Ron and me to compile these proposals and 
> get back 
> > > with a proposal submitted for community consensus.
> > > 
> > > Dan
> > > _______________________________________________
> > > OPS-AREA mailing list
> > > OPS-AREA@ietf.org
> > > https://www.ietf.org/mailman/listinfo/ops-area
> > > 
> > 
> > 
> 

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 07:03:03 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A60CF28C110;
	Mon,  4 Aug 2008 07:03:03 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 642973A6CB8
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 07:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049, 
	BAYES_00=-2.599]
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 0r7Z8HOhtsaq for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 07:03:00 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com
	(de307622-de-outbound.net.avaya.com [198.152.71.100])
	by core3.amsl.com (Postfix) with ESMTP id 419AB3A6C9D
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 07:02:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,304,1215403200"; d="scan'208";a="117003336"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	04 Aug 2008 10:03:24 -0400
X-IronPort-AV: E=Sophos;i="4.31,304,1215403200"; d="scan'208";a="243433796"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	04 Aug 2008 10:03:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Aug 2008 16:03:15 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E8E16C@307622ANEX5.global.avaya.com>
In-Reply-To: <009301c8f639$08415fd0$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
Thread-Index: Acj19Bzo+IRRpcDiTYqNKxAbzWJtxwAJFxgwAALVVbAABBxMUAAAzS+wAACRZUA=
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop><alpine.LRH.1.10.0808040835530.9304@netcore.fi>
	<EDC652A26FB23C4EB6384A4584434A04E8E09B@307622ANEX5.global.avaya.com>
	<009201c8f62c$5c4663d0$0600a8c0@china.huawei.com>
	<EDC652A26FB23C4EB6384A4584434A04E8E151@307622ANEX5.global.avaya.com>
	<009301c8f639$08415fd0$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>,
	"Pekka Savola" <pekkas@netcore.fi>,
	"Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi David,

It is not only the remote participants who are affected by not having
the agendas in place before the meeting. It is also those participants
who want to prepare for the meeting, to download print (or not) and read
the Internet-Drafts in advance (many of them use the long
inter-continental flights for this). Carrots are not only for the
editors. Mehmet rightly pointed to the fact that a WG chair needs to see
the documents a day in advance in order to fine tune them in the context
of the meeting that he/she needs to run. 

I see that you took the punitive side too seriously, and I apologize
because maybe it is me who made the proposal sound too harsh (or was it
Bert who started? It is always good to blame the previous AD :-)).
Cancelling a meeting or a presentation should indeed be an extreme
action. What we want to change is to make of posting agendas and
presentations in advance to allow proper preparation of the meetings and
remote participation efficient the rule to be followed by all. Let us
find the ways to do it with as much carrot and as little stick as
possible. 

Dan


> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net] 
> Sent: Monday, August 04, 2008 4:50 PM
> To: Romascanu, Dan (Dan); 'Pekka Savola'; 'Bert Wijnen (IETF)'
> Cc: 'ops-area (IETF)'
> Subject: RE: [OPS-AREA] meeting materials MUST be online well 
> BEFORE thesession
> 
> Hi Dan,
> 
> IETF volunteers are here to produce standards. That is not 
> always a fun thing to do, and the sloeness of IETF work is 
> extrememly frustrating, but moist of our main volunteer 
> contributors do this work because they believe in the 
> benefits of an open and fair volunteer process of standards 
> development. Some even get paid to do it; many do not. 
> Helping to develop a better Internet by working on standards
> **is** the carrot. 
> 
> The discussion "hey, folks, it is hard for remote 
> contributors to participate effectively if the agendas and/or 
> the presentations are posted too late" focuses on the carrot; 
> when agendas and presentations are not posted early enough, 
> if skews the process and makes the WG less effective - it 
> affects the carrot.
> 
> When the discussion removed the smiley and started talking 
> about punative actions - cancelling sessions and removing 
> presentations from the sessions, then you turned the 
> discussion into a "stick" discussion rather than a carrot discussion.
> 
> dbh
> 
> > -----Original Message-----
> > From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
> > Sent: Monday, August 04, 2008 9:34 AM
> > To: David Harrington; Pekka Savola; Bert Wijnen (IETF)
> > Cc: ops-area (IETF)
> > Subject: RE: [OPS-AREA] meeting materials MUST be online 
> well BEFORE 
> > thesession
> > 
> > Hi David,
> > 
> > Wow, I think that I pushed a red-hot button :-)
> > 
> > Let me try to address the issues that you are raising. We all want
> to
> > make the standards process work better and faster, get more people 
> > involved and motivated and issue better standards at the end of the 
> > process. The intent of such rules would not be to punish and to 
> > exclude but to make agendas and materials available in advance for 
> > people to be more efficient at the meeting. I believe that at the 
> > meeting last
> week
> > some people could not prepare well because agendas (not only from
> your
> > WG) came too late, and the remote participation lacked efficiency 
> > because many presentations were not available even by the time the 
> > meetings started.
> > 
> > My experience is that if rules are in place and known in advance 
> > responsible people do their best in order to respect them. In the
> case
> > of your WG if the one week agenda rule was in advance I am 
> sure that 
> > you and David would have done the best to submit a 
> preliminary agenda 
> > by the deadline, or would have announced the WG and the AD before 
> > traveling 'look, we are traveling this period for such and such 
> > reasons, preliminary agenda will not be available on the Monday 
> > deadline but only Wednesday before the meeting'. Being 
> predictive is 
> > what we seek
> here,
> > being able for all participants in the process to plan and 
> allow the 
> > best possible fairness and preparation time is what we seek.
> > 
> > There are always exceptions and life situations that make some 
> > deadlines impossible to match. For these purposes all the 
> IETF systems 
> > or the majority of them accept human override with proper approval 
> > level.
> In
> > the case such rules will be adopted in the future, ADs will 
> have the 
> > capability of accepting agendas after the deadline and WG 
> chairs will 
> > be able to accept presentations or updates even in the last 
> 24 hours 
> > before the meeting. However, this would be an exception, the rule 
> > would be that agendas and presentations need to be 
> submitted in time, 
> > and I am
> sure
> > that the majority of the volunteers who are all on both 
> provider and 
> > receiver roles will make the rules work in most cases.
> > 
> > Regards,
> > 
> > Dan
> > 
> > BTW - you criticized my use of some kind of stick menace, but you
> did
> > not suggest any carrot. I would love a carrot-only based system if 
> > somebody can come with one.
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: David Harrington [mailto:ietfdbh@comcast.net]
> > > Sent: Monday, August 04, 2008 3:20 PM
> > > To: Romascanu, Dan (Dan); 'Pekka Savola'; 'Bert Wijnen (IETF)'
> > > Cc: 'ops-area (IETF)'
> > > Subject: RE: [OPS-AREA] meeting materials MUST be online 
> well BEFORE 
> > > thesession
> > > 
> > > Hi,
> > > 
> > > I think we should focus more on carrots than sticks. This is a 
> > > volunteer organization.
> > > My name is Dave and I am a sinner.
> > > 
> > > Sometimes the chairs get tied up with day-job work and have 
> > > difficulty finding time to focus on writing up an agenda.
> > > Sometimes the chairs need to wait until they get input from 
> > > volunteers about presentations that will will be done 
> before setting 
> > > up an agenda. Do you recommend posting empty agendas so that the 
> > > deadline is met, and then editing it later when we have content?
> > > 
> > > Have you thought about the unintended consequences of a rule that 
> > > prevents a WG from meeting or discussing a particular 
> topic if the 
> > > agenda and materials are not posted in advance?
> > > What will be the consequences if volunteers spend money 
> to travel to 
> > > an IETF meeting, only to find that their only session has been 
> > > cancelled because a chair was tied down with day-job 
> work, or they 
> > > could not work on resolving the issues because the presentation 
> > > didn't get posted? Will they continue to travel to IETF meetings? 
> > > Will they request new chairs? Where will we get new 
> chairs that are 
> > > not burdened by day-job demands? Will the WG accomplish better 
> > > standards, or get them done faster, as a result of such rules?
> > > 
> > > My WG didn't get an early agenda posted because one chair was 
> > > travelling internationally for day-job work for the month 
> prior to 
> > > Dublin (justifying funding of a team to work on IETF 
> standards), and 
> > > the other was on a 3.5 week vacation with his family. 
> Which of those 
> > > should we have given up to ensure that the agenda was posted more 
> > > than a week in advance? Should we resign as chairs 
> because we cannot 
> > > guarantee timely delivery of the agenda? Should the whole 
> WG suffer 
> > > by having its sessions cancelled because the chairs faced 
> competing 
> > > real world priorities?
> > > 
> > > We were also guilty of not posting the presentations well
> > in advance.
> > > We had to wait for the presentations to be written, which usually 
> > > happened within 24 hours of when the presentation would be 
> > > delivered.
> > > The content of those presentations was sometimes impacted 
> by the f2f 
> > > discussions that occurred during the IETF week, including during 
> > > evening bar time when compromises were worked out between major 
> > > contributors on open issues.
> > > 
> > > Some chairs had problems with connectivity. I know my 
> co-chair could 
> > > not access the web during our first session, so he could not even 
> > > access the meeting materials himself. I had spotty 
> connectivity; I 
> > > frequently did not get emails from my co-chair or the 
> contributors 
> > > for hours after they were sent to me, so I did not have access to 
> > > the presentations or to the meeting materials page on a timely 
> > > basis.
> > > Should the WG session be cancelled or the topic be banned because 
> > > the network connectivity was not always perfect enough to ensure 
> > > postings at least 24 hours in advance?
> > > 
> > > I would be very careful about trying to legislate too much and to 
> > > penalize whole WGs because the chairs failed to post meeting 
> > > materials on time. I think the cure would be worse than 
> the problem.
> > > 
> > > I know I failed to post on a timely basis this time, and 
> I will try 
> > > to do better in the future, although some are real-world 
> obstacles 
> > > beyond my control. If you start punishing the whole WG for late 
> > > postings by the chairs, I will probably just ask you to 
> find a new 
> > > chair.
> > > 
> > > David Harrington
> > > dbharrington@comcast.net
> > > ietfdbh@comcast.net
> > > dharrington@huawei.com
> > > 
> > > > -----Original Message-----
> > > > From: ops-area-bounces@ietf.org
> > > > [mailto:ops-area-bounces@ietf.org] On Behalf Of
> > Romascanu, Dan (Dan)
> > > > Sent: Monday, August 04, 2008 11:02 AM
> > > > To: Pekka Savola; Bert Wijnen (IETF)
> > > > Cc: ops-area (IETF)
> > > > Subject: Re: [OPS-AREA] meeting materials MUST be online
> > > well BEFORE
> > > > thesession
> > > > 
> > > >  
> > > > 
> > > > > -----Original Message-----
> > > > > From: ops-area-bounces@ietf.org
> > > > > [mailto:ops-area-bounces@ietf.org] On Behalf Of Pekka Savola
> > > > > Sent: Monday, August 04, 2008 8:37 AM
> > > > > To: Bert Wijnen (IETF)
> > > > > Cc: ops-area (IETF)
> > > > > Subject: Re: [OPS-AREA] meeting materials MUST be online
> > > well BEFORE
> > > > > the session
> > > > > 
> > > > > On Sat, 2 Aug 2008, Bert Wijnen (IETF) wrote:
> > > > > > Let me suggest that if a presenter does not provide his/her 
> > > > > > presentation at the latest 24 hours before the session
> > > > start, then
> > > > > > cancel his/her presentation.
> > > > > 
> > > > > If we go along this path -- and if the agenda is not
> > > uploaded to the
> > > > > web a week before the meeting, cancel the meeting :-)
> > > > > 
> > > > 
> > > > I would actually drop the smiley and entertain such an
> > idea. I find
> > > > practically impossible for someone to prepare for a
> > meeting if the
> > > > agenda is not posted less than a week before the meeting. 
> > > Of course,
> > > > changes should be allowed until the last day, but the
> > main items on
> > > > the agenda, and the preliminary reading materials list
> > can be made
> > > > available one week in advance.
> > > > 
> > > > Please allow to Ron and me to compile these proposals and
> > get back
> > > > with a proposal submitted for community consensus.
> > > > 
> > > > Dan
> > > > _______________________________________________
> > > > OPS-AREA mailing list
> > > > OPS-AREA@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/ops-area
> > > > 
> > > 
> > > 
> > 
> 
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug  4 10:12:32 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5343E3A6D28;
	Mon,  4 Aug 2008 10:12:32 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E08B13A6D21
	for <ops-area@core3.amsl.com>; Mon,  4 Aug 2008 10:12:30 -0700 (PDT)
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.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y10PsiVODU7L for <ops-area@core3.amsl.com>;
	Mon,  4 Aug 2008 10:12:30 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net
	(elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66])
	by core3.amsl.com (Postfix) with ESMTP id 02F963A6D11
	for <ops-area@ietf.org>; Mon,  4 Aug 2008 10:12:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=dk20050327; d=mindspring.com;
	b=WmWuv46hgGHGeAHJJ0LJBtObh8iWw1VDus+AtXyZrnkhVUsDjKV0wh2nshU+drqb;
	h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [68.166.189.209] (helo=oemcomputer)
	by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67)
	(envelope-from <randy_presuhn@mindspring.com>) id 1KQ3c1-00089w-8r
	for ops-area@ietf.org; Mon, 04 Aug 2008 13:12:49 -0400
Message-ID: <008301c8f655$6ce59f20$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "ops-area \(IETF\)" <ops-area@ietf.org>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
	<A294F5A3E722D94FBEB6D49C1506F6F7EA6020@DEMUEXC005.nsn-intra.net>
Date: Mon, 4 Aug 2008 10:13:32 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888a63b7957ab9b23b3a4f319c5bb481725c51c0fd5fca9de1c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 68.166.189.209
Subject: Re: [OPS-AREA] meeting materials MUST be online well
	BEFOREthesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi -

> From: "Ersue, Mehmet (NSN - DE/Muenich)" <mehmet.ersue@nsn.com>
> To: "ext Bert Wijnen (IETF)" <bertietf@bwijnen.net>; "ops-area (IETF)" <ops-area@ietf.org>
> Sent: Monday, August 04, 2008 4:20 AM
> Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFOREthesession
...
> It is not helpful for remote attendees and is actually too 
> late if the presenter shows up in the last second with a 
> USB stick.
> 
> OTOH the WG chairs should take a look on the slides 
> before the session and request changes if the slides are 
> not appropriate (e.g. tutorial instead of issue discussion, 
> too many slides for the time available in the session slot).
> 
> We need to find a way to force early provision of the 
> presentation slides to the meeting material site.
...

YES, especially for BOFs.  I've found that BOF presenters often stray
far from the agreed BOF focus in counter-productive ways, despite
advance discussion.  Though carrots are nice in theory, this is
one of those cases where having a stick would really help.  But
I agree with David Harrington that completely dropping the meeting
or presentation in question may in some cases be a bit too
draconian, even though I think such a policy might be better in
the aggregate than what we have now.  But perhaps we could
try another path: construct some kind of public pillory (with company
affiliation for identification purposes) for the offendors - folks with
excessive fluff, excessive marketing, or who hand chairs memory
sticks loaded with beside-the-point material.

Randy

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed Aug  6 04:49:44 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1C7333A6C0A;
	Wed,  6 Aug 2008 04:49:44 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A0E873A69C6;
	Wed,  6 Aug 2008 04:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, 
	BAYES_00=-2.599]
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 uXuKvF1JlHY1; Wed,  6 Aug 2008 04:49:41 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id 7D75F3A6B88;
	Wed,  6 Aug 2008 04:49:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,314,1215403200"; d="scan'208";a="130088172"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 06 Aug 2008 07:50:12 -0400
X-IronPort-AV: E=Sophos;i="4.31,314,1215403200"; d="scan'208";a="245093739"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	06 Aug 2008 07:50:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 6 Aug 2008 13:50:10 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E8E57D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sponsor Ballot for IEEE P802.1ap
Thread-Index: Acj3upRTYvrlsI+MScOPl33cayAdqQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,
	"ops-area (IETF)" <ops-area@ietf.org>
Cc: David Levi <dlevi@nortel.com>, Glenn Parsons <gparsons@nortel.com>
Subject: [OPS-AREA] Sponsor Ballot for IEEE P802.1ap
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

The P802.1ap (Q MIBs) Sponsor ballot is now under way, and will close on
4th September.

This work is a continuation of the Bridge MIB WG work, which was
transferred to the IEEE 802.1 Working Group as described in RFC4663. It
is a major revision of the Bridge MIB RFCs, covering many of the
extensions in the IEEE 802.1 bridging and VLAN technologies approved in
the last few years by the IEEE 802.1 WG. 

It would be useful if the IETF MIB Doctors and OPS Area experts could
review this document and the MIB modules it incorporates and provide
comments to me or Glenn Parsons until the date of the ballot closure. 

The draft being balloted, and the text version of the MIBs, can be found
here:

http://www.ieee802.org/1/files/private/ap-drafts/d4/

Username: *****
Password: ***********

Please contact me or Glenn to get the username and password for the
purpose of accessing the documents in ballot. 

Dan
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed Aug  6 04:53:35 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 989E328C1D3;
	Wed,  6 Aug 2008 04:53:35 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E4A453A6C2C;
	Wed,  6 Aug 2008 04:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037, 
	BAYES_00=-2.599]
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 FMM8lA-xX5Di; Wed,  6 Aug 2008 04:53:34 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id E3D403A6C2A;
	Wed,  6 Aug 2008 04:53:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,314,1215403200"; d="scan'208";a="138430482"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 06 Aug 2008 07:54:05 -0400
X-IronPort-AV: E=Sophos;i="4.31,314,1215403200"; d="scan'208";a="252018741"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	06 Aug 2008 07:54:04 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 6 Aug 2008 13:54:03 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E8E586@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04E8E57D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MIB-DOCTORS] Sponsor Ballot for IEEE P802.1ap
Thread-Index: Acj3upRTYvrlsI+MScOPl33cayAdqQAAFrXw
References: <EDC652A26FB23C4EB6384A4584434A04E8E57D@307622ANEX5.global.avaya.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>,
	"ops-area (IETF)" <ops-area@ietf.org>
Cc: Glenn Parsons <gparsons@nortel.com>, David Levi <dlevi@nortel.com>
Subject: Re: [OPS-AREA] [MIB-DOCTORS] Sponsor Ballot for IEEE P802.1ap
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

I should have probably mentioned for those who are not familiar with
IEEE 802 terminology that Sponsor Ballot is a phase roughly similar to
IETF Last Call, being thus the last opportunity for the community at
large to provide feedback on a standard-to-be. 

Dan
 

> -----Original Message-----
> From: mib-doctors-bounces@ietf.org 
> [mailto:mib-doctors-bounces@ietf.org] On Behalf Of Romascanu, 
> Dan (Dan)
> Sent: Wednesday, August 06, 2008 2:50 PM
> To: MIB Doctors (E-mail); ops-area (IETF)
> Cc: David Levi; Glenn Parsons
> Subject: [MIB-DOCTORS] Sponsor Ballot for IEEE P802.1ap
> 
> The P802.1ap (Q MIBs) Sponsor ballot is now under way, and 
> will close on 4th September.
> 
> This work is a continuation of the Bridge MIB WG work, which 
> was transferred to the IEEE 802.1 Working Group as described 
> in RFC4663. It is a major revision of the Bridge MIB RFCs, 
> covering many of the extensions in the IEEE 802.1 bridging 
> and VLAN technologies approved in the last few years by the 
> IEEE 802.1 WG. 
> 
> It would be useful if the IETF MIB Doctors and OPS Area 
> experts could review this document and the MIB modules it 
> incorporates and provide comments to me or Glenn Parsons 
> until the date of the ballot closure. 
> 
> The draft being balloted, and the text version of the MIBs, 
> can be found
> here:
> 
> http://www.ieee802.org/1/files/private/ap-drafts/d4/
> 
> Username: *****
> Password: ***********
> 
> Please contact me or Glenn to get the username and password 
> for the purpose of accessing the documents in ballot. 
> 
> Dan
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug 11 09:08:16 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A7C303A692D;
	Mon, 11 Aug 2008 09:08:16 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABF883A692D
	for <ops-area@core3.amsl.com>; Mon, 11 Aug 2008 09:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.426
X-Spam-Level: 
X-Spam-Status: No, score=0.426 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, HELO_MISMATCH_NET=0.611]
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 44Ko+yYzTnDL for <ops-area@core3.amsl.com>;
	Mon, 11 Aug 2008 09:08:13 -0700 (PDT)
Received: from mail.hardakers.net (dcn236-43.dcn.davis.ca.us [168.150.236.43])
	by core3.amsl.com (Postfix) with ESMTP id AA9943A68A2
	for <ops-area@ietf.org>; Mon, 11 Aug 2008 09:08:13 -0700 (PDT)
Received: from wes.hardakers.net (dawn.hardakers.net [127.0.0.1])
	by mail.hardakers.net (Postfix) with ESMTP id 280D6983D6;
	Mon, 11 Aug 2008 09:08:16 -0700 (PDT)
Received: from wes.hardakers.net (wlap.dyn.hardakers.net [127.0.0.1])
	by wes.hardakers.net (Postfix) with ESMTP id EA2DD2C3301;
	Mon, 11 Aug 2008 09:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hardakers.net; h=from:to
	:cc:subject:references:date:in-reply-to:message-id:mime-version:
	content-type; s=wesmail; bh=HP4VkngLDYXHyecFN/YVKaSkzEM=; b=Z/V4
	MeJn0qvtMehRMw31hqNuBeHTNgs6awwpdO+QfjTgTwPR6p7LPBdJo8W75Ej0x4At
	gTa5rFmctyKIXOMfsFOsc2alqtrdrXhMfF3K742o61QeZvRgsPSRdltsNSv1qAjF
	PIviuBJZXcFqE8KHIvuDnjG3s7iFHvrw8OdM8kA=
Received: by wes.hardakers.net (Postfix, from userid 274)
	id CC0E32C3300; Mon, 11 Aug 2008 09:08:15 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "Ersue\, Mehmet \(NSN - DE\/Muenich\)" <mehmet.ersue@nsn.com>
Organization: Sparta
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
	<489315AC.1040903@juniper.net>
	<0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop>
	<A294F5A3E722D94FBEB6D49C1506F6F7EA6020@DEMUEXC005.nsn-intra.net>
Date: Mon, 11 Aug 2008 09:08:15 -0700
In-Reply-To: <A294F5A3E722D94FBEB6D49C1506F6F7EA6020@DEMUEXC005.nsn-intra.net>
	(Mehmet Ersue's message of "Mon, 4 Aug 2008 13:20:31 +0200")
Message-ID: <sdzlnjwn4g.fsf@wes.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) XEmacs/21.4.21 (linux, no MULE)
MIME-Version: 1.0
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE
	thesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

>>>>> On Mon, 4 Aug 2008 13:20:31 +0200, "Ersue, Mehmet (NSN - DE/Muenich)" <mehmet.ersue@nsn.com> said:

ME> It is not helpful for remote attendees and is actually too 
ME> late if the presenter shows up in the last second with a 
ME> USB stick.

Speaking as someone who is one of the sources of a recent USB stick: I
agree things should be encouraged as much as possible in advance.  The
problem comes in that we're a real-world seat-of-the-pants type of
standardization body.  We work on things in the hallway sometimes
minutes before meetings that affect presentations and may require slide
changes.  Yes, we could force presentations/meetings to be canceled if
slides/agendas aren't available.  But the question is: how does this
removal of work items actually benefit us?  It actually will inhibit our
already too-slow work process, not help it.  It would certainly help
some, as probably 50% of the people would get things submitted in time.
But I'm sure the other 50% probably wouldn't.


In my particular case, I simultaneously sent slides in for two
presentations I was giving (more than 24 hours in advance).  One of the
two bounced.  Real life servers got in the way.  Had I been allowed to
submit my own slides instead via the presentation submission tool (I
checked; I couldn't) this wouldn't have been an issue as I could get to
that page (though even that could have gone down).


(Another option is to force them to give a talk at a microphone without
their slides; it'd still allow discussion without the presentation
material ;-)

-- 
Wes Hardaker
Sparta, Inc.
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug 11 10:53:57 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D2C093A69D0;
	Mon, 11 Aug 2008 10:53:57 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2FDA93A69D0
	for <ops-area@core3.amsl.com>; Mon, 11 Aug 2008 10:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5
	tests=[AWL=-1.300, BAYES_50=0.001]
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 nJ4s0Uh-6lxP for <ops-area@core3.amsl.com>;
	Mon, 11 Aug 2008 10:53:56 -0700 (PDT)
Received: from QMTA05.emeryville.ca.mail.comcast.net
	(qmta05.emeryville.ca.mail.comcast.net [76.96.30.48])
	by core3.amsl.com (Postfix) with ESMTP id 67F923A6801
	for <ops-area@ietf.org>; Mon, 11 Aug 2008 10:53:56 -0700 (PDT)
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA05.emeryville.ca.mail.comcast.net with comcast
	id 11wg1a0060x6nqcA55teXd; Mon, 11 Aug 2008 17:53:38 +0000
Received: from Harrington73653 ([24.128.66.199])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id 15tb1a00E4HwxpC8Y5tcpK; Mon, 11 Aug 2008 17:53:37 +0000
X-Authority-Analysis: v=1.0 c=1 a=WNO6NfqQiqkA:10 a=gbrI5vREOLoA:10
	a=NeXrn9EyP4zwy-xp4UEA:9 a=ZtCIudNCWPLF0XVH0O0A:7
	a=LG7hxQGryAinvt4VJyJVElKCv6kA:4 a=gJcimI5xSWUA:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Wes Hardaker'" <wjhns1@hardakers.net>,
	"'Ersue, Mehmet \(NSN - DE/Muenich\)'" <mehmet.ersue@nsn.com>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop><A294F5A3E722D94FBEB6D49C1506F6F7EA6020@DEMUEXC005.nsn-intra.net>
	<sdzlnjwn4g.fsf@wes.hardakers.net>
Date: Mon, 11 Aug 2008 13:53:39 -0400
Message-ID: <04d401c8fbdb$30c733b0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <sdzlnjwn4g.fsf@wes.hardakers.net>
Thread-Index: Acj7zHjhAMKxTNawSDSfFjD7yHuytgADLVbw
Cc: "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online well
	BEFOREthesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

 

> Yes, we could force presentations/meetings to be canceled if
> slides/agendas aren't available.  But the question is: how does this
> removal of work items actually benefit us?  It actually will 
> inhibit our
> already too-slow work process, not help it.  

> (Another option is to force them to give a talk at a 
> microphone without
> their slides; it'd still allow discussion without the presentation
> material ;-)

I think the "another option" suffers from the same problem as the
cancellation option. I do not see how forcing people to discuss things
at the microphone without the benefit of the slides they submitted
late, benefits the IETF. I think this restriction would inhibit
progress.

Working for a Chinese company whose personnel often have difficulty
attending meetings due to travel budget or visa concerns, and who
frequently utilize our tools for remote participation, I am very
sensitive to the importance of having the slides available for remote
participants. But at this point in time, remote particiants are still
a small minority in the IETF community, and penalizing the IETF
community in attendance at the meeting because the remote participants
might be inconvenienced does not make much sense to me.

If we want to be serious about supporting remote participants (and I
think we should), I think there are a lot of things besides having
slides available that are important. In Dublin, as I watched chairs
sometimes talk into their mikes, but not consistently, and chairs
counting hands but not verbally reporting the results, and people at
the mikes rushing through what they had to say rather than thinking
about how well remote participants would be able to understand them, I
thought to myself maybe every chair should be required to actually
listen to and replay their recorded sessions to see just how difficult
it is to be a remote participant in their WG. That might have a much
greater effect toward supporting remote participants than cancelling
presentations.

dbh

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Aug 11 11:55:33 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 375963A6CB9;
	Mon, 11 Aug 2008 11:55:33 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 290C23A6CA9
	for <ops-area@core3.amsl.com>; Mon, 11 Aug 2008 11:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.345
X-Spam-Level: 
X-Spam-Status: No, score=-1.345 tagged_above=-999 required=5 tests=[AWL=1.254, 
	BAYES_00=-2.599]
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 2CBvH6NKGlji for <ops-area@core3.amsl.com>;
	Mon, 11 Aug 2008 11:55:31 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by core3.amsl.com (Postfix) with SMTP id A78CA3A6878
	for <ops-area@ietf.org>; Mon, 11 Aug 2008 11:55:30 -0700 (PDT)
Received: (qmail invoked by alias); 11 Aug 2008 18:55:07 -0000
Received: from a91-154-105-144.elisa-laajakaista.fi (EHLO [192.168.255.3])
	[91.154.105.144]
	by mail.gmx.net (mp040) with SMTP; 11 Aug 2008 20:55:07 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18BP6FDpooBSxh4EaZU17miXx14fGUgJGnVmI/D7y
	ok0E2BYCBJiYdy
Message-ID: <48A08B17.4060001@gmx.net>
Date: Mon, 11 Aug 2008 21:55:19 +0300
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop><489315AC.1040903@juniper.net><0FE3428BDAAD47A791EDBBD03F938B2D@BertLaptop><A294F5A3E722D94FBEB6D49C1506F6F7EA6020@DEMUEXC005.nsn-intra.net>	<sdzlnjwn4g.fsf@wes.hardakers.net>
	<04d401c8fbdb$30c733b0$0600a8c0@china.huawei.com>
In-Reply-To: <04d401c8fbdb$30c733b0$0600a8c0@china.huawei.com>
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.65
Cc: "'Ersue, Mehmet \(NSN - DE/Muenich\)'" <mehmet.ersue@nsn.com>,
	"'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] meeting materials MUST be online
	well	BEFOREthesession
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

A few notes from my side:

* I doubt that the reason for the slow progress in the IETF is related 
to the face-to-face meeting. The problem is the time in between meetings.

* Those who do not know what drafts have to be read for the meeting 
(because of an absent agenda) haven't followed the work in the working 
group and are therefore not very likely to read the drafts anyway. These 
folks need a tutorial or a monthly status update (we distribute these 
status update in DIME).

* BOFs are a completely separate subject. They typically need far more 
preparation for a variety of reasons. A different story.

* Reading through everyone's slides: Well. If you are really serious 
about that issue and you think you know everything better than the folks 
in the group then the chairs should write the slides for the group. 
(This makes the time management much easier. Additionally, you have to 
consider that some folks speak slow, are hard to understand, never get 
to the point, talk about things not written on the slides, etc. etc. ) 
The question is how much "show" do you want to provide during the meeting.

* Demanding that folks have their slides ready a week before the meeting 
is not realistic. We would have to cancel almost all our meetings. It 
would be nice to have everything available, great meeting minutes, good 
jabber scribes, briliant audio recordings, etc. Just a bit hard to make 
this happen. I tried to create podcasts myself during meetings but it 
was really tough to get a good output.

* If you believe that you have to wait for the IETF meeting to make 
"progress" then you are wrong. Do it in the time between meetings on the 
mailing list (or potentially via phone conf. calls). This is obviously 
best for "remote participants".

* The most important time during an IETF meeting are the hallway 
conversations and the socializing in the evening, before the IETF 
meeting starts and after the IETF meeting is finished. You can hardly 
deliver that experience to remote participants.

Ciao
Hannes




David Harrington wrote:
>  
>
>   
>> Yes, we could force presentations/meetings to be canceled if
>> slides/agendas aren't available.  But the question is: how does this
>> removal of work items actually benefit us?  It actually will 
>> inhibit our
>> already too-slow work process, not help it.  
>>     
>
>   
>> (Another option is to force them to give a talk at a 
>> microphone without
>> their slides; it'd still allow discussion without the presentation
>> material ;-)
>>     
>
> I think the "another option" suffers from the same problem as the
> cancellation option. I do not see how forcing people to discuss things
> at the microphone without the benefit of the slides they submitted
> late, benefits the IETF. I think this restriction would inhibit
> progress.
>
> Working for a Chinese company whose personnel often have difficulty
> attending meetings due to travel budget or visa concerns, and who
> frequently utilize our tools for remote participation, I am very
> sensitive to the importance of having the slides available for remote
> participants. But at this point in time, remote particiants are still
> a small minority in the IETF community, and penalizing the IETF
> community in attendance at the meeting because the remote participants
> might be inconvenienced does not make much sense to me.
>
> If we want to be serious about supporting remote participants (and I
> think we should), I think there are a lot of things besides having
> slides available that are important. In Dublin, as I watched chairs
> sometimes talk into their mikes, but not consistently, and chairs
> counting hands but not verbally reporting the results, and people at
> the mikes rushing through what they had to say rather than thinking
> about how well remote participants would be able to understand them, I
> thought to myself maybe every chair should be required to actually
> listen to and replay their recorded sessions to see just how difficult
> it is to be a remote participant in their WG. That might have a much
> greater effect toward supporting remote participants than cancelling
> presentations.
>
> dbh
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>   

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Tue Aug 12 04:18:38 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 82FB73A68CA;
	Tue, 12 Aug 2008 04:18:38 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8B0893A6833
	for <ops-area@core3.amsl.com>; Tue, 12 Aug 2008 04:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level: 
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=0.230, 
	BAYES_00=-2.599]
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 6VLs-VPXs+Am for <ops-area@core3.amsl.com>;
	Tue, 12 Aug 2008 04:18:36 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 6043E3A68CA
	for <ops-area@ietf.org>; Tue, 12 Aug 2008 04:18:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,195,1217822400"; d="scan'208";a="139248307"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 12 Aug 2008 07:17:12 -0400
X-IronPort-AV: E=Sophos;i="4.32,195,1217822400"; d="scan'208";a="256396211"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	12 Aug 2008 07:17:12 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 12 Aug 2008 13:17:11 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E8EF98@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Fourth Nomcom 2008-9Call for Volunteers 
Thread-Index: Acj8GXuyCzaF+M9FQRGvxOCQ7AsWggAU0NYg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ops-area (IETF)" <ops-area@ietf.org>,
	<ops-ads@tools.ietf.org>
Subject: [OPS-AREA] FW: Fourth Nomcom 2008-9Call for Volunteers
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org



-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of NomCom Chair
Sent: Tuesday, August 12, 2008 4:19 AM
To: IETF Announcement list
Subject: Fourth Nomcom 2008-9Call for Volunteers 

Fourth Nomcom 2008-9 Call for Volunteers!
I am pleased to report that there are 91 volunteers whose qualifications
have been confirmed by the secretariat.  
There is 1 more volunteers awaiting confirmation, as of Monday
afternoon, August 11, 2008.
However, I would still like more volunteers.
You have until August 18th, 2008 as stated below.  Please do so. 
The full details are included below.  Please use the listed format, as
that helps me and the secretariat do our jobs better. 

In a separate note, I will post the current list of verified Volunteers.
 

Thank you, and I look forward to hearing from you, Joel M. Halpern


Once again, the IETF nominating process has begun, and the community
(and I) need your help.  The IETF Nominating Committee appoints folks to
fill the open slots on the IAOC, the IAB, and the IESG.  The people who
do that are 10 folks selected randomly from the pool of volunteers.
To make this work well for the community, we need people to volunteer.
Lots of people.  Please!

Volunteers must have attended 3 of the past 5 IETF meetings.  As defined
by RFC 3777, that is 3 of the past 5 meetings as of the time this
announcement goes out to start the solicitation. If you qualify, and are
willing to forgo appointment to any of the positions for which the
nominating committee is responsible, please volunteer.  Details on the
nominating process can be found in RFC 3777.

Below is the list of people and posts whose terms end with the March
2009 IETF meeting, and whose positions therefore the nominating
committee is responsible for:

IAOC:
Jonne Soininen

IAB:
Loa Andersson
Barry Leiba
Kurtis Lindqvist
Danny McPherson
Dave Thaler
Lixia Zhang

IESG:
IETF and IESG Chair: Russ Housley
Applications Area (app): Chris Newman
Internet Area (int): Mark Townsley
Operations and Management Area (ops): Ronald Bonica Real-time
Applications and Infrastructure Area (rai):
    Jon Peterson
Routing Area (rtg): David Ward
Security Area (sec): Tim Polk
Transport Area (tsv): Lars Eggert

Before volunteering, please think about whether you want to be
considered for one of the above positions instead.  If you are willing
to volunteer, please send email before 5:00 pm EDT (2100 UTC/GMT) August
18, 2008 (otherwise, please read on)

Please send email to me using the following skeleton:

To: jmh@joelhalpern.com
Subject: Nomcom 2008-9 Volunteer
Body:

<Your Full Name>  // As you enter in the IETF Registration Form,
                  // First/Given name followed by Last/Family Name
<Current Primary Affiliation>
                  // typically what goes in the Company field
                  //  in the IETF Registration Form [<all email
addresses used to Register for the past 5 IETF meetings>] <Preferred
email address>  //
<Telephone number>         // For confirmation if selected

Please expect an email response from me within 1-2 days stating whether
you are qualified or not.  If you don't receive anything, please re-send
your email with the tag (duplicate) in the subject line.
During the IETF meeting in Dublin, responses will be somewhat slower,
due to both my activities at the meeting and the secretariat's many
activities in support of the meeting.   I will try to send out at least
a prompt confirmation that your email volunteering has been received.


Not convinced yet?  Please consider that nomcom members play an
important role in shaping the leadership of the IETF.  If you are a
people person, you will enjoy meeting many of the active contributors to
the IETF.  If you prefer instead to read a lot of email, well, we have
that too.  Being a nomcom member is also an important responsibility: it
requires adherence to confidentiality rules and some time commitment
from the members.  The term of this nomcom will begin in early September
this year.  We will be talking with folks at the Minneapolis IETF (if
you are there.  It is not mandatory that all nomcom members come to the
meeting.)  I hope to wrap up our primary selection work by mid-December,
and we must complete our selection work by mid-January.

We will be collecting requirements from the community, as well as
talking to candidates and to community members about candidates.
There will be weekly conference calls to ensure progress.


Nomcom members are selected following a publicly verifiable random
selection method specified in RFC 3797.

For the nomcom to work as it should, the pool from which the volunteers
are chosen should be as large as possible. The more people who
volunteer, the better chance we have of choosing a random yet
representative cross section of the IETF population.

Ensuring the leadership of the IETF is fair and balanced and comprised
of those who can lead the IETF in the right direction is an important
responsibility that rests on the IETF participants at large.
Volunteering for the nomcom is a good way of contributing in that
direction.  So please volunteer!


I will be publishing a more thorough and precise target timetable, as
well as details of the randomness seeds to be used for the RFC 3797
selection process within the next few days.


Thank you, and I hope to hear from you,
Joel M. Halpern
jmh@joelhalpern.com
nomcom-chair@ietf.org


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed Aug 13 09:57:13 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD0CF3A698F;
	Wed, 13 Aug 2008 09:57:13 -0700 (PDT)
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 442783A6814
	for <ops-area@core3.amsl.com>; Wed, 13 Aug 2008 09:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level: 
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.297, 
	BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_21=0.6,
	J_CHICKENPOX_31=0.6, J_CHICKENPOX_41=0.6]
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 cPQyPHCVLrUy for <ops-area@core3.amsl.com>;
	Wed, 13 Aug 2008 09:57:11 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 09B503A698F
	for <ops-area@ietf.org>; Wed, 13 Aug 2008 09:57:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,202,1217822400"; 
	d="txt'?scan'208";a="139481126"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 13 Aug 2008 12:57:12 -0400
X-IronPort-AV: E=Sophos;i="4.32,202,1217822400"; 
	d="txt'?scan'208";a="257700726"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	13 Aug 2008 12:57:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C8FD65.A0D4FABE"
Date: Wed, 13 Aug 2008 18:57:10 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04ECC3DD@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Preliminary Minutes of the Dublin OPSAREA meeting
Thread-Index: Acj9ZaBvnCbDeZLxSAyn0fUJpVWVyw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ops-area (IETF)" <ops-area@ietf.org>
Subject: [OPS-AREA] Preliminary Minutes of the Dublin OPSAREA meeting
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8FD65.A0D4FABE
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Please find below the preliminary minutes of the open area meeting in
Dublin. Thanks to the two notes takers - Balazs and Benoit - for their
notes. Please review and let me know what I got wrong or what I missed.=20

There are a few ?? where neither the notes takes nor me could recall who
was the speaker. Identifying yourselves would be nice.=20

Thanks and Regards,

Dan

------_=_NextPart_001_01C8FD65.A0D4FABE
Content-Type: text/plain;
	name="ops-area-ietf72-dublin-meeting-minutes.txt"
Content-Transfer-Encoding: base64
Content-Description: ops-area-ietf72-dublin-meeting-minutes.txt
Content-Disposition: attachment;
	filename="ops-area-ietf72-dublin-meeting-minutes.txt"

T1BTQVJFQSBPcGVuIE1lZXRpbmcNCkFyZWEgRGlyZWN0b3JzOiBEYW4gUm9tYXNjYW51IGFuZCBS
b24gQm9uaWNhDQpUVUVTREFZIEp1bHkgMjksIDIwMDgNCjA5MDAtMTEzMCAgTW9ybmluZyBTZXNz
aW9uDQoNCg0KMS4gTm90ZSB3ZWxsLCBhZ2VuZGEgYmFzaGluZywgbm90ZSB0YWtlcnMsIGJsdWUg
c2hlZXRzIC0gNSBtaW4NCg0KMi4gSVRVLVQgSkNBIG5ldyB3b3JrLCBEYW4NCg0KaHR0cDovL3d3
dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy8wOGp1bC9zbGlkZXMvb3BzYXJlYS0xLnBwdCANCg0KLSBK
b2ludCBDb29yZGluYXRpb24gQWN0aXZpdHkgb24gTWFuYWdlbWVudCAoSkNBLU1ndCkgaXMgdGhl
IGNvb3JkaW5hdGlvbiBvZiB0aGUgbWFuYWdlbWVudCBzdGFuZGFyZGl6YXRpb24gd29yayBpbnNp
ZGUgYW5kIG91dHNpZGUgb2YgdGhlIElUVS1ULiBUaGlzIEpDQSBpbmNsdWRlcyB0aGUgY29vcmRp
bmF0aW9uIHJlc3BvbnNpYmlsaXRpZXMgcHJldmlvdXNseSBhZGRyZXNzZWQgYnkgdGhlIE5HTiBN
YW5hZ2VtZW50IEZvY3VzIEdyb3VwIChOR05NRkcpIHJlZ2FyZGluZyBOR04gbWFuYWdlbWVudCwg
YnV0IGdvZXMgYmV5b25kIGJ5IGluY2x1ZGluZyBhbHNvIHRoZSBjb29yZGluYXRpb24gb2YgdGhl
IHdvcmsgcmVsYXRlZCB0byB0aGUgbmV4dCBnZW5lcmF0aW9uIG9mIHRlbGVjb21tdW5pY2F0aW9u
IG1hbmFnZW1lbnQgbmV0d29ya3MuIA0KLSBTTk1QLCBORVRDT05GIGFuZCBNSUIgZG9jdW1lbnRz
IGluY2x1ZGVkIGluIHRoZSBtYW5hZ2VtZW50IHJvYWRtYXAgZG9jdW1lbnRzIGlzc3VlZCBieSBO
R05NRkcNCi0gZm9jdXNlZCBvbiB0aGUgc3BlY2lmaWNhdGlvbiBvZiBtYW5hZ2VtZW50IGludGVy
ZmFjZXMgYXNzb2NpYXRlZCB3aXRoIGEgdGVsZWNvbW11bmljYXRpb24gbWFuYWdlbWVudCBuZXR3
b3JrLiBTdWNoIG1hbmFnZW1lbnQgaW50ZXJmYWNlcyBpbmNsdWRlIGludGVyZmFjZXMgYmV0d2Vl
biBhIG5ldHdvcmsgZWxlbWVudCBhbmQgYSBtYW5hZ2VtZW50IHN5c3RlbSBhbmQgYmV0d2VlbiB0
d28gbWFuYWdlbWVudCBzeXN0ZW1zLCBidXQgZXhjbHVkZSBtYW5hZ2VtZW50IGludGVyZmFjZXMg
YmV0d2VlbiBuZXR3b3JrIGVsZW1lbnRzLiANCi0gZXN0YWJsaXNoZWQgYnkgSVRVLVQgU3R1ZHkg
R3JvdXAgNCBpbiBNYXkgMjAwOCAobGlhaXNvbiBsZXR0ZXIgc2VudCB0byBhIG51bWJlciBvZiBT
RE9zLCBpbmNsdWRpbmcgdGhlIElFVEYpIGFuZCBpdHMgdGVybXMgb2YgcmVmZXJlbmNlIGlzIGRv
Y3VtZW50ZWQgaW4gU0cgNCBURCA2MTcgR0VODQotIFBhcnRpY2lwYXRpb24gaXMgb3BlbiB0byBs
ZWFkZXJzIGFuZCBvdGhlciBpbnZpdGVkIGluZGl2aWR1YWxzIGZyb20gSVRVLVQgYW5kIG5vbi1J
VFUtVCBvcmdhbml6YXRpb25zIHdpdGggZXhwZXJ0aXNlIGFuZCBzcGVjaWZpY2F0aW9ucyBhcHBs
aWNhYmxlIHRvIG1hbmFnZW1lbnQgaW50ZXJmYWNlcw0KLSBEYW4gYW5kIEJlcnQgaGF2ZSBiZWVu
IHBhcnRpY2lwYXRpbmcsIGFzIGluZGl2aWR1YWwgY29udHJpYnV0b3IsIGluIHRoZSBOR05NRkcg
Zm9yIHRoZSBsYXN0IHR3by10aHJlZSB5ZWFycywgUm9uIGpvaW5lZCBsYXRlbHkNCi0gUmVmcmVz
aGluZyB0aGUgcGFydGljaXBhbnRzIGxpc3QgbWF5IGJlIGEgZ29vZCB0aGluZw0KLSBQbGVhc2Ug
Y29udGFjdCB0aGUgQURzIGlmIHlvdSBhcmUgaW50ZXJlc3RlZCB0byBwYXJ0aWNpcGF0ZSBpbiB0
aGlzIGFjdGl2aXR5DQoNCkRpc2N1c3Npb25zOg0KDQotIFNjb3R0IEJyYWRuZXI6IGFueSBvdmVy
bGFwIHdpdGggdGhlIElFVEY/IEhvdyBkb2VzIHRoaXMgYWZmZWN0IHVzDQotIERhbjogSVRVLVQg
d2FudHMgdG8gYXZvaWQgb3ZlcmxhcCBieSBkb2luZyARaGFybW9uaXphdGlvbhIuIFVzZWZ1bCwg
c291cmNlIG9mIGluZm8gYW5kIGEgZ29vZCB3YXkgdG8gc3ByZWFkIGluZm8gb24gb3VyIHdvcmsu
DQoNCjMuIFBlcmZvcm1hbmNlIG9mIFNOTVAgb3ZlciBUQ1AgYW5kIFVEUCB1bmRlciB2YXJpb3Vz
IGxldmVscyBvZiBsb3NzeSBjb25kaXRpb25zIC0gV2VzIEhhcmRha2VyDQoNCmh0dHA6Ly93d3cu
aWV0Zi5vcmcvcHJvY2VlZGluZ3MvMDhqdWwvc2xpZGVzL29wc2FyZWEtMi5wZGYgDQoNCi0gV2Fu
dGVkIHRvIHNlZSBzb21lIHJlYWwgbnVtYmVycywgc28gZGlkIHRoZSBleHBlcmltZW50DQotIFB1
cnBvc2U6DQoJSG93IFNOTVAgcGVyZm9ybXMgaW4gYmFkIGVudmlyb25tZW50cw0KCUhvdyB0byBw
aWNrIHRoZSByaWdodCBwcm90b2NvbCBmb3IgdGhlIHJpZ2h0IHRhc2sNCi0gV2h5Og0KCUxvc3N5
IG5ldHdvcmtzIGFyZSBzdGlsbCBjb21tb24gYmVjYXVzZSBvZiAuLg0KCQljb25nZXN0aW9uLCBt
b2JpbGl0eSwgd2lyZWxlc3MgbWVzaGVzLCBzYXRlbGxpdGUgbmV0d29yaw0KCVBhc3QgVURQIHZz
IFRDUCBzdHVkeSBhcmVuP3QgcmVjZW50DQotIE1JVBJzIFJvb2ZOZXQgZGlkIHNvbWUgdGVzdHMg
d2l0aCBsaW5rcyB3aXRoIGF2ZXJhZ2UgbG9zcyByYXRlIG9mIDUwJS4gICAgDQotIENvbmNsdXNp
b246IHJlYWxseSBkaWZmaWN1bHQgdG8gcHJlZGljdCB0aGUgbG9zcyByYXRlLiANCi0gVGhpcyBp
cyBhIHZlcnkgcXVpY2sgc3R1ZHkgKG5vIHBsYW5zIHRvIGRvIG1vcmUgdGVzdHMgZm9yIG5vdykN
CgkyIFBDcyB3aXRoIGEgcm91dGVyIGluIHRoZSBtaWRkbGUsIGRyb3BwaW5nIHJhbmRvbSBwYWNr
ZXRzDQoJMTAwMCBHRVQgcmVxdWVzdHMgd2l0aCBTTk1QdjJjLCBwb2xsaW5nIG9uZSBzeXNDb250
YWN0LjANClN0dWR5IDE6IA0KCVdoZW4gdGhlcmUgYXJlIG5vIGxvc3MsIFVEUCBhbmQgVENQIGFy
ZSBpZGVudGljYWwNCglXaXRoIHNvbWUgbG9zczogVENQICh3aXRoIGEgdGltZW91dD0xcykgdGFr
ZXMgbG9uZ2VyIC0+IHRoaXMgaXMgbm9ybWFsDQoJSGlnaGVyIGxvc3MgKDI3LjclKTogdGhlIHJl
c3VsdHMgYXJlIHN0aWxsIGNvbnNpc3RlbnQgKHRoZSBUQ1AgcmVzcG9uc2UgdGltZSBpcyBsaW5l
YXIgY29tcGFyZWQgdG8gdGhlIG51bWJlciBvZiByZXF1ZXN0cykNCglCdXQgd2l0aCAzMi43JSwg
dGhlIFRDUCByZXNwb25zZSB0aW1lIGlzIG5vdCBsaW5lYXIgYW55bW9yZSBjb21wYXJlZCB0byB0
aGUgbnVtYmVyIG9mIHJlcXVlc3RzIHdoaWxlIHRoZSBVRFAgaXMgc3RpbGwgbGluZWFyDQotIElm
IHlvdSBrbm93IGhvdyBsb25nIHlvdXIgYWdlbnQgdGFrZXMgdG8gcmVzcG9uZCwgd2l0aCBVRFAs
IHlvdSBjYW4gcHJlZGljdCBob3cgbG9uZyB0aGUgcG9sbGluZyB3aWxsIHRha2UNCg0KLSBTdHVk
eSAyOiBHZXQgMjAgc3lzQ29udGFjdC4wIGluc3RhbmNlcyB3aXRoIGZyYWdtZW50YXRpb24NCi0g
VENQIGRvZXMgYSBiZXR0ZXIgdGhhbiBVRFAgKHJlbHlpbmcgb24gSVApIGRvaW5nIGZyYWdtZW50
YXRpb24sIGV4Y2VwdCBhdCBoaWdoZXIgcmF0ZSBsb3NzIChhcm91bmQgMzAlIGxvc3MpLCB3aGVy
ZSB0aGUgVENQIGxpbmUgaXMgbm90IGxpbmVhciBhbnltb3JlDQoNCi0gV2l0aCBoaWdoIGxvc3Mg
cmF0ZSAoMjcuNyUpLCB3aXRoIFRDUCwgdGhlcmUgaXMgbm8gd2F5IHRvIHByZWRpY3QgdGhlIHJl
c3BvbnNlIHRpbWUNCi0gQ29uY2x1c2lvbnM6IA0KTm90IGdvaW5nIHRvIGRyYXcgYSBsb3Qgb2Yg
Y29uY2x1c2lvbnMvcmVjb21tZW5kYXRpb25zDQotIFF1ZXN0aW9uIGZvciB0aGUgdmlld2VyOiB3
aGVuIGlzIGl0IHdpc2UgdG8gdXNlIFVEUCB2ZXJzdXMgVENQPw0KLSBUQ1AgaXMgZ3JlYXQgdW5k
ZXIgaWRlYWwgY29uZGl0aW9ucyBhbmQgZXZlbiBtaWxkeSBiYWQgb25lcw0KLSBQcm9wZXIgc2V0
dGluZyBvZiBVRFAgdGltZW91dCB2YWx1ZXMgaXMgY3JpdGljYWwgKG5vIG9uZXMgc2V0cyB0aGVt
IHVwIHByb3Blcmx5KQ0KLSBEb24SdCBsZXQgVURQIGZyYWdtZW50LiBTaG91bGQgbWFrZSBzdXJl
IHRoYXQgd2UgZG9uP3QgaGF2ZSB0b28gYmlnIFNOTVAgcGFja2V0DQotIFRDUCBpcyBncmVhdCB1
bmRlciBpZGVhbCBjb25kaXRpb25zIGFuZCBldmVuIG1pbGR5IGJhZCBvbmVzDQotIFByb3BlciBz
ZXR0aW5nIG9mIFVEUCB0aW1lb3V0IHZhbHVlcyBpcyBjcml0aWNhbCAobm8gb25lcyBzZXRzIHRo
ZW0gdXAgcHJvcGVybHkpDQoNCkRpc2N1c3Npb25zDQoNClJvbiBCOiBIb3cgbG9zc3kgYXJlIHRo
ZSBuZXR3b3JrcyB0aGF0IGFyZSBzdGlsbCB1c2UsIGFueXRoaW5nIG92ZXIgNSU/DQpXZXM6IE1v
cmUgdGhlIDUlIGlzIGNvbW1vbiwgYnV0IGFmdGVyIGEgbGV2ZWwgb2YgbG9zcyBUQ1AgZ2l2ZXMg
dXAuDQpUQ1Agc2hvdWxkIHNvbWV0aW1lcyBzdG9wIGFuZCByZXN0YXJ0LiBVc2VycyB3aXRoIGEg
YnJvd3NlciBkbyB0aGF0DQpwcm9ncmFtcyBkb250LiBXaHk/IEFsc28gdGhlIHVzZXJzIGRvbj90
IGFsd2F5cyBjb21wbGFpbi4gRXhhbXBsZTogd2FpdGluZyBmb3IgYSBicm93c2VyIHBhZ2UsIHN0
b3AgaXQsIHRoZW4gcmVsb2FkIHNvbWV0aW1lcyB3b3Jrcw0KLSBMaXNzID86ICBJZiBMb3NzIGlz
IGNhdXNlZCBDb25nZXN0aW9uLCB5b3Ugc2hvdWxkIG5vdCBwdXNoIGhhcmRlciwgb3RoZXJ3aXNl
IGl0IGlzIGEgZ29vZCB0YWN0aWMuIEJlY2F1c2UgaWYgdGhlIGNhdXNlIGlzIGNvbmdlc3Rpb24s
IHRoZW4gdGhlcmUgaXMgbm8gcG9pbnQgdG8gcHVzaCBpdA0KLSBMaXNzPyA6IFRDUCBtZWV0IGEg
Y29tcHJvbWlzZSBiZXR3ZWVuIGNvbmdlc3Rpb24gYW5kIHRocm91Z2hwdXQuIFJ1biB0aGUgdGVz
dCB3aXRoIGZyYWdtZW50YXRpb24gd2l0aCBkaWZmZXJlbnQgc3RhY2tzIGJlY2F1c2UgdGhlIGlt
cGxlbWVudGF0aW9uIG1pZ2h0IGJlIGRpZmZlcmVudC4gVHJ5IGRpZmZlcmVudCBVRFAgc3RhY2tz
LCBlc3BlY2lhbGx5IFVEUCBmcmFnbWVudGluZyBjYXNlcyEgUHJvYmxlbXMgbWlnaHQgYmUgaW1w
bGVtZW50YXRpb24gc3BlY2lmaWMuDQpXZXM6IFBsYW5uZWQgdG8gdHJ5IHdpbmRvd3MsIGRpZG50
IGhhdmUgdGltZQ0KIC0gSnVlcmdlbiBTY2hvbndhZWxkZXI6IGZvciBUQ1AsIHdlIGtub3cgaG93
IGNvbmdlc3Rpb24gd29ya3MuIEZvciBTTk1QIG92ZXIgVURQLCB0aGVyZSBpcyBub3RoaW5nOiBp
dCBkZXBlbmRzIG9uIHRoZSBpbXBsZW1lbnRhdGlvbi4gTmV0U05NUCBkb2VzIGxpbmVhciBiYWNr
dXAsIG5vdCBleHBvbmVudGlhbA0KLSBXZXM6IHdlIGRvbhJ0IHdhbnQgdG8gc2V0IHRoZSB0aW1l
b3V0IGJlbG93IHRoZSBsYXRlbmN5DQpKdXJnZW4gU2Nob3VlbndhbGRlcjogIFVEUCBjb25nZXN0
aW9uIGNvbnRyb2w/IENvbmdlc3Rpb24gd291bGQgbW9kaWZ5IHRoZSByZXN1bHRzLg0KV2VzOiBV
RFAgdXNlcyBncmVhdCBsb3Qgb2YgYmFuZHdpZHRoLiBUaGUgbWFuYWdlciBzaG91bGQga25vdyB0
aGUgbmV0d29yayBpdCBtYW5hZ2VzLiBXZSBhbHdheXMgdXNlZCBzYWZlIFVEUCB0aW1lb3V0cy4g
U2V0dGluZyBpdCB0b28gbG93IGlzIHJpc2t5LiBHZXRuZXh0IGlzIG5vdCB1c2VkLCBzcGVjaWFs
IGNhc2UuDQoNCg0KCQ0KNC4gT3BlcmF0aW9uYWwgYXNwZWN0cyBvZiBOQVQtUFQNCg0KNC4xIFBv
c3QgSVB2NCA/Y29tcGxldGlvbiAtIEFsYWluIER1cmFuZA0KDQotIFdoeSBhcmUgcGVvcGxlIGxv
b2tpbmcgYXQgSVB2NiBhZ2Fpbj8NCi0gVGhlIGludGVybmV0IG11c3Qgc3VwcG9ydCBjb250aW51
ZXMsIHVuLWludGVycnVwdGVkIGdyb3d0aCByZWdhcmRsZXNzIG9mIElQdjQgYWRkcmVzcyBhdmFp
bGFiaWxpdHkNCi0gU3RpbGwgSVB2NDoNCglNYW55IGhvc3RzIGluIHRoZSBob21lIGFyZSBJUHY0
LW9ueQ0KCUNvbnRlbnQgc2VydmVycyBob3N0ZWQgd2lsbCB0YWtlIHRpbWUgdG8gZ28gdG8gSVB2
Ng0KLSBUd28gZGVwbG95bWVudCBzY2VuYXJpb3MgZm9yIGxlZ2FjeSBkZXBsb3ltZW50czoNCglE
b3VibGUgTkFUIHY0djQNCglEdWFsLXN0YWNrIGxpdGUNCi0gQWxsLW5ldyBkZXZpY2UgZGVwbG95
bWVudHMgKGVnOiB3aXJlbGVzcykNCglEdWFsLXN0YWNrIGxpdGUNCglOQVQtUFQsIE5BVDY0LElW
SQ0KLSBEaXNjdXNzZWQgdGhlIGltcGFjdCBvbiB0aGUgSVB2NC9JUHY2IG9wZXJhdGlvbiBhbmQg
RE5TDQotIERvIHdlIHdhbnQgdG8gaGF2ZSBJUHY2IG9ubHkgc2VydmVyPyBEbyB3ZSBoYXZlIHJl
cXVpcmVtZW50IGZvciBJUHY0IC0+IElQdjYNCg0KRGlzY3Vzc2lvbnMNCg0KTWFyZ2FyZXQ6IFY2
IGVuZCBkZXZpY2Ugc3BlYWtzIHY0IHRvIHRoZSB2NCBpbnRlcm5ldCwgd2h5IGRvIHdlIG5lZWQg
YSBOQVQ/DQpBbGFpbjogTm90IGVub3VnaCB2NCBhZGRyZXNzIChlLmcuIHdpcmVsZXNzIGRldmlj
ZXMpLCAxMC0yMDAgbWlsbGlvbiBuZXcgYWRkcmVzc2VzIG5lZWRlZC4gRXZlbiB0aGUgcHJpdmF0
ZSB2NCBhZGRyZXNzZXMgYXJlIG5vdCBlbm91Z2guICg2NCBtaWxsaW9uIGFkZHJlc3MpDQpNYXJn
YXJldDogQUxHIGZvciB2NCB0byB2NiBleGlzdD8NCkFsYWluOiBOb3QgeWV0DQoNCg0KNC4yIE5B
VCBvcGVyYXRpb25hbCBjb25zaWRlcmF0aW9ucywgSWxqaXRzY2ggdmFuIEJlaWpudW0NCg0KLSBo
dHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzA4anVsL3NsaWRlcy9vcHNhcmVhLTMucGRm
DQoNCi0gTkFUNjQ/cyB1c2VmdWxuZXNzDQogICAgICBEdWFsIHN0YWNrIGxpZ2h0IHByb3ZpZGVz
IG1vcmUgYmFja3dhcmQgY29tcGF0aWJpbGl0eSB3aXRoIElQdjQgc3R1ZmYNCglIb3dldmVyLCBO
QVQ2NCBicmVha3MgdGhlIHZpY2lvdXMgY3ljbGUgZm9yIHN5c3RlbXMgdGhhdCAocHJlZmVyIHRv
KSBvbmx5IC0gdXNlIElQdjY6DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1iYWdu
dWxvLWJlaGF2ZS1uYXQ2NC0wMA0KDQpBYnN0cmFjdA0KICAgTkFUNjQgaXMgYSBtZWNoYW5pc20g
Zm9yIHRyYW5zbGF0aW5nIElQdjYgcGFja2V0cyB0byBJUHY0IHBhY2tldHMgYW5kDQogICB2aWNl
LXZlcnNhLiAgRE5TNjQgaXMgYSBtZWNoYW5pc20gZm9yIHN5bnRoZXNpemluZyBBQUFBIHJlY29y
ZHMgZnJvbQ0KICAgQSByZWNvcmRzLiAgVGhlc2UgdHdvIG1lY2hhbmlzbXMgdG9nZXRoZXIgZW5h
YmxlIGNsaWVudC1zZXJ2ZXINCiAgIGNvbW11bmljYXRpb24gYmV0d2VlbiBhbiBJUHY2LW9ubHkg
Y2xpZW50IGFuZCBhbiBJUHY0LW9ubHkgc2VydmVyLA0KICAgd2l0aG91dCByZXF1aXJpbmcgYW55
IGNoYW5nZXMgdG8gZWl0aGVyIHRoZSBJUHY2IG9yIHRoZSBJUHY0IG5vZGUsDQogICBmb3IgdGhl
IGNsYXNzIG9mIGFwcGxpY2F0aW9ucyB0aGF0IHdvcmsgdGhyb3VnaCBOQVRzLiAgVGhleSBhbHNv
DQogICBlbmFibGUgcGVlci10by1wZWVyIGNvbW11bmljYXRpb24gYmV0d2VlbiBhbiBJUHY0IGFu
ZCBhbiBJUHY2IG5vZGUsDQogICB3aGVyZSB0aGUgY29tbXVuaWNhdGlvbiBjYW4gYmUgaW5pdGlh
dGVkIGJ5IGVpdGhlciBlbmQgdXNpbmcNCiAgIGV4aXN0aW5nLCBOQVQtdHJhdmVyc2luZywgcGVl
ci10by1wZWVyIGNvbW11bmljYXRpb24gdGVjaG5pcXVlcy4NCiAgIFRoaXMgZG9jdW1lbnQgc3Bl
Y2lmaWVzIE5BVDY0IGFuZCBETlM2NCwgYW5kIGdpdmVzIHN1Z2dlc3Rpb25zIG9uIGhvdw0KICAg
dGhleSBzaG91bGQgYmUgZGVwbG95ZWQuDQoNCi0gRGlzY3Vzc2VkIHRoZSBwb3NzaWJsZSBsb2Nh
dGlvbnMgb2YgTkFUNjQNCi0gRGlzY3Vzc2VkIHRoZSBwb3NzaWJsZSBsb2NhdGlvbnMgb2YgRE5T
NjQNCi0gQ29uY2x1c2lvbnM6DQpVc2VmdWwgaW5pdGlhbCBhcHByb2FjaDoNCiAgICAgIHBsYWNl
IE5BVDY0IHNvbWV3aGVyZSBpbiBJU1AgbmV0d29yaw0KICAgICAgcGxhY2UgRE5TNjQgaW4gSVNQ
IG5ldCBjbG9zZSB0byB1c2VyDQpUaGVuIGxhdGVyIG9wdGltaXplOg0KICAgICAgYWRkIEROUzY0
IHRvIENQRXMgYW5kL29yIGhvc3RzDQoNCkRpc2N1c3Npb25zDQoNCj8/PzogQ1BFIGlzIHdoYXQ/
IEwyIG9yIEwzPw0KSWxqaXRzdGg6IENQRSBnYXRld2F5IG9yIGRzbCBtb2RlbS4gU29tZSBMYXll
cjMgZGV2aWNlIG5lZWRlZA0KDQo/Pz86IENQRSBpcyBkaWZmZXJlbnQgZm9yIENhYmxlIG5ldHdv
cmtzIGFuZCBEU0wgbmV0cw0KDQo/Pz86IEhvdyB0byBtaWdyYXRlIEROUzY0IGZyb20gSVNQIHRv
IGhvc3Q/DQpJbGppdHNjaDogV2lsbCBub3QgYmUgYSBwcm9ibGVtIGFzIGhvc3QgaXMgdjYNCg0K
DQpEYXZlOiBQbGFjZW1lbnQgb2YgTkFUNjQgaW4gcG9pbnQ3LCB3aHkgaXMgdGhpcyBiYWQgZm9y
IGdsb2JhbCBwcmVmaXg/DQpJbGppdHNjaDogRE5TNjQgd2lsbCBiZSBhdmFpbGFibGUgY2xvc2Vy
IHRvIHRoZSBvcmlnaW4gYW55d2F5Lg0KRGF2ZTogVXNlIG5hdDY0IGFuZCBkbnM2NCBpbiB0aGUg
ZGVzdGluYXRpb24gbm9kZQ0KSWxqaXRzY2g6IE5vIHNlbnNlLiBUaGUgaW50ZXJuZXQgb3RoZXJz
IHdpbGwgbm90IGtub3cgYWJvdXQgdGhlIHdob2xlIHN0dWZmDQoNCj8/PzogTkFUNjQgaW4gcG9z
aXRpb242LiBJZiBJU1AgQSBhbmQgUHJvdmlkZXIgQiBoYXMgYW4gYWdyZWVtZW50IGF1dGhlbnRp
Y2F0aW9uIGlzIG5vdCBwcm9ibGVtYXRpYy4NCg0KDQoNCjQuMyBJVkkgT3BlcmF0aW9uYWwgQ29u
c2lkZXJhdGlvbnMgYW5kIHByYWN0aWNlDQoNCi0gaHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVk
aW5ncy8wOGp1bC9zbGlkZXMvb3BzYXJlYS00LnBkZiANCg0KLSBDTkdJLUNFUk5FVCBpcyBhbiBJ
UHY2IHNpbmdsZSBzdGFjayBuZXR3b3JrLg0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2lkL2RyYWZ0
LXhsaS1iZWhhdmUtaXZpLTAwLnR4dCANCg0KICAgUHJlZml4LXNwZWNpZmljIGFuZCBTdGF0ZWxl
c3MgQWRkcmVzcyBNYXBwaW5nIChJVkkpIGZvciBJUHY0L0lQdjYNCiAgICAgICAgICAgICAgICAg
ICAgICAgQ29leGlzdGVuY2UgYW5kIFRyYW5zaXRpb24NCkFic3RyYWN0DQogICBUaGlzIGRvY3Vt
ZW50IHByZXNlbnRzIHRoZSBjb25jZXB0IGFuZCBwcmFjdGljZSBvZiB0aGUgcHJlZml4LQ0KICAg
c3BlY2lmaWMgYW5kIHN0YXRlbGVzcyBhZGRyZXNzIG1hcHBpbmcgbWVjaGFuaXNtIChJVkkpIGZv
ciBJUHY0L0lQdjYNCiAgIGNvZXhpc3RlbmNlIGFuZCB0cmFuc2l0aW9uLiAgSW4gdGhpcyBzY2hl
bWUsIHN1YnNldHMgb2YgdGhlIElQdjQNCiAgIGFkZHJlc3NlcyBhcmUgZW1iZWRkZWQgaW4gcHJl
Zml4LXNwZWNpZmljIElQdjYgYWRkcmVzc2VzIGFuZCB0aGVzZQ0KICAgSVB2NiBhZGRyZXNzZXMg
Y2FuIHRoZXJlZm9yZSBjb21tdW5pY2F0ZSB3aXRoIHRoZSBnbG9iYWwgSVB2Ng0KICAgbmV0d29y
a3MgZGlyZWN0bHkgYW5kIGNhbiBjb21tdW5pY2F0ZSB3aXRoIHRoZSBnbG9iYWwgSVB2NCBuZXR3
b3Jrcw0KICAgdmlhIHN0YXRlbGVzcyAob3IgYWxtb3N0IHN0YXRlbGVzcykgZ2F0ZXdheXMuICBU
aGUgSVZJIHNjaGVtZQ0KICAgc3VwcG9ydHMgdGhlIGVuZC10by1lbmQgYWRkcmVzcyB0cmFuc3Bh
cmVuY3ksIGluY3JlbWVudGFsIGRlcGxveW1lbnQNCiAgIGFuZCBwZXJmb3JtYW5jZSBvcHRpbWl6
YXRpb24gaW4gbXVsdGktaG9tZWQgZW52aXJvbm1lbnQuICBUaGlzDQogICBkb2N1bWVudCBpcyBh
IGNvbXByZWhlbnNpdmUgcmVwb3J0IG9uIHRoZSBJVkkgZGVzaWduIGFuZCBpdHMNCiAgIGRlcGxv
eW1lbnQgaW4gbGFyZ2Ugc2NhbGUgcHVibGljIG5ldHdvcmtzLiAgQmFzZWQgb24gdGhlIElWSQ0K
ICAgc2NlbmFyaW8sIHRoZSBjb3JyZXNwb25kaW5nIGFkZHJlc3MgYWxsb2NhdGlvbiBhbmQgYXNz
aWdubWVudA0KICAgcG9saWNpZXMgYXJlIGFsc28gcHJvcG9zZWQuDQoNClNlZSB0aGUgc2xpZGVz
IGZvciB0aGUgZGV0YWlscw0KVGhlIElWSSAoMToxKSBoYXMgYmVlbiBydW5uaW5nIGF0IENOR0kt
Q0VSTkVUMiBmb3IgbW9yZSB0aGFuIHR3byB5ZWFycw0KCU9wZW4gc291cmNlIGF2YWlsYWJsZQ0K
DQpEaXNjdXNzaW9ucw0KDQpQZWtrYSBTYXZvbGE6IElWSSBtaWdodCBiZWNvbWUgYSByZWxheSBs
aWtlIGFuIFNNVFAgb3BlbiByZWxheS4gTWlnaHQgYmUgYmxhY2sgbGlzdGVkLiBWNiBzZXJ2ZXIg
YWxsIG5lZWQgYSB2NCBhZGRyZXNzLg0KWGluZzogU2VjdXJpdHkgZm9yIHN0dWR5LiB2NCBhZGRy
ZXNzIHNoYXJpbmcgYmFzZWQgb24gZGlmZmVyZW50IHBvcnRzIHBvc3NpYmxlLg0KDQoNCg0KNS4g
V0cgU3RhdHVzIHJlcG9ydHM6ICBXRyBjaGFpcnMsIDMgbWluIGVhY2ggDQoNCkJNV0cgKEFsIE1v
cnRvbikNCglJUFNFQzogVGVybWlub2xvZ3ksIG1ldGhvZG9sb2d5IHNldHRsZWQsIGxhc3QtY2Fs
bCBjb21pbmcgc29vbg0KCVNJUCBuZXR3b3JraW5nIChuZXcgY2hhcnRlcikNCglNUExTIA0KDQpQ
TU9MIChBbCBNb3J0b24pDQoJT25seSB3b3JraW5nIG9uIHR3byBkcmFmdHM6DQoJCVNJUCBwZXJm
b3JtYW5jZSBtZXRyaWNzDQoJCUZyYW1ld29yayANCg0KRGltZSAoRGF2aWQpDQoJRmluaXNoaW5n
IHVwIHRoZSBjaGFydGVyIHdvcmsNCglUaGlua2luZyBvZiBuZXcgd29yaywgcmVjaGFydGVyDQoJ
CU1JQi4gTG9va2luZyBmb3IgcGVvcGxlIHdobyBpbXBsZW1lbnRlZCBEaWFtZXRlcg0KCQlBc2tp
bmcgZmVlZGJhY2sgZm9yIG5ldyB3b3JrIGl0ZW1zDQoNCk5ldENvbmYgKEJlcnQpDQoJUHVibGlz
aGVkIHRoZSBub3RpZmljYXRpb24gUkZDDQoJTmV3IHBvdGVudGlhbCB3b3JrIGl0ZW06IG5vdGlm
aWNhdGlvbiBjb250ZW50DQoJMyBpdGVtcyBvbiB0aGUgdGFibGU6IE1vbml0b3JpbmcsIE5ldGNv
bmYgb3ZlciBUTFMsIGFuZCBwYXJ0aWFsIGxvY2sNCg0KTmV0bW9kIChEYXZpZCBQZXJ0YWluKQ0K
CUZpcnN0IElFVEYgbWVldGluZw0KCURvY3VtZW50cyBjb3ZlcmluZyBhbGwgd29yayBpdGVtcyBl
eGNlcHQgb25lDQoNCklQSUZYIChKdWVyZ2VuIFF1aXR0ZWspDQoJQmFzZWQgcHJvdG9jb2xzIHB1
Ymxpc2hlZA0KCUluZm9ybWF0aW9uIG1vZGVsOiB3ZSBkZWZpbmVkIGEgTUlCIChhbG1vc3QgY29t
cGxldGUpDQoJVGhpbmtpbmcgb24gaG93IHRvIGNvbmZpZ3VyZSB0aGUgZGV2aWNlIHdpdGggTkVU
Q09ORg0KCVRoZSBORVRDT05GIGRhdGEgbW9kZWwgaXMgbm90IGNvbnNpc3RlbnQgd2l0aCB0aGUg
TUlCDQoJVHJhbnNsYXRpb24gZnJvbSBTTUkgdG8gWE1MOiB3aWxsIGl0IGJlIGNvbnNpc3RlbnQg
d2l0aCBZQU5HPw0KCVNoYXJvbjogaW50ZXJlc3RpbmcgcXVlc3Rpb24NCgkJTWF5IHJlcXVpcmUg
dHdvIGRhdGEgbW9kZWxzIChvbmUgZm9yIGNvbmZpZywgb25lIGZvciBtb25pdG9yaW5nKQ0KCQlN
aWdodCBiZSBhbiBpbnRlcmVzdGluZyBjYXNlIHN0dWR5DQoJRGFuIChjb250cmlidXRvcik6IG1h
eWJlIGl0P3MgdGltZSB0byBoYXZlIGEgbmV3IGZyYW1ld29yayANCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgIFRoaXMgaXMgYmVpbmcgd29ya2VkIG9uIGluIE9QU0FXRw0KICAgICAgICAgICAg
ICAgICAgICAgICAgICAgQWltZWQgYXQgb3RoZXIgV0dzLiBNdWx0aXBsZSBwcm90b2NvbHMgbmVl
ZGVkLiANCiAgICAgICAgICAgICAgICAgICAgICAgICAgIE11bHRpcGxlIGRhdGEgbW9kZWxzIG5l
ZWRlZCANCg0KT1BTQVJFQSBXRyAoU2NvdHQpDQoJT25lIGRvY3VtZW50IGluIElFU0cNCglNb3N0
IGludGVyZXN0aW5nIHRvcGljOiB3aGF0IGRvZXMgT0FNIG1lYW4/DQoJV2UgZG9uP3QgbWVhbiB0
aGUgc2FtZSB0aGluZyB3aGVuIElFVEYvSVRVIHNwZWFrIGFib3V0IG5ldHdvcmsgbWFuYWdlbWVu
dA0KCVdlIGRvbj90IG1lYW4gdGhlIHNhbWUgdGhpbmcgd2hlbiBJRVRGL0lUVSBzcGVhayBhYm91
dCBPJk0NCglFeGFtcGxlOiBNUExTIE9BTQ0KDQoNCg==

------_=_NextPart_001_01C8FD65.A0D4FABE
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area

------_=_NextPart_001_01C8FD65.A0D4FABE--


