IETF Logo Mail Archive

Re: [93attendees] Meeting schedule

Ted Lemon <ted.lemon@nominum.com> Tue, 21 July 2015 12:20 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: 93attendees@ietfa.amsl.com
Delivered-To: 93attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D338D1A1A43 for <93attendees@ietfa.amsl.com>; Tue, 21 Jul 2015 05:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Avvr1i-uT4-Y for <93attendees@ietfa.amsl.com>; Tue, 21 Jul 2015 05:20:49 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17A8C1A00C8 for <93attendees@ietf.org>; Tue, 21 Jul 2015 05:20:49 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id F13F6DA0089; Tue, 21 Jul 2015 12:20:48 +0000 (UTC)
Received: from [10.0.20.218] (71.233.41.235) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 21 Jul 2015 05:20:48 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_00C051D3-725E-4E2B-9C56-FB063E41BDB3"
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <19C73CC7-DEA0-49CB-9FB2-09109811B254@gmail.com>
Date: Tue, 21 Jul 2015 08:20:47 -0400
Message-ID: <FC521C48-C71D-4DCD-B345-634687ECD32F@nominum.com>
References: <p06240602d1d3231e977e@[130.129.14.251]> <alpine.OSX.2.01.1507201630210.60032@rabdullah.local> <D2E48F4F-CE89-4C1F-ACB4-85F219651A8C@juniper.net> <alpine.OSX.2.01.1507201650211.60032@rabdullah.local> <55ADCF31.20706@gmail.com> <A58586E3-63BA-431C-A85F-0DFCF913A328@gmail.com> <A022620E-DC2E-434C-83F3-78E76E0851CA@nominum.com> <19C73CC7-DEA0-49CB-9FB2-09109811B254@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.2102)
X-Originating-IP: [71.233.41.235]
Archived-At: <http://mailarchive.ietf.org/arch/msg/93attendees/KK2uL1hUMAKFIdWGJYrdW4XtweI>
Cc: "93attendees@ietf.org" <93attendees@ietf.org>
Subject: Re: [93attendees] Meeting schedule
X-BeenThere: 93attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 93 attendees that have opted in on this list. " <93attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/93attendees>, <mailto:93attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/93attendees/>
List-Post: <mailto:93attendees@ietf.org>
List-Help: <mailto:93attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/93attendees>, <mailto:93attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 12:20:51 -0000

On Jul 21, 2015, at 7:37 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> I don’t know how to answer that without a stated goal of what plenaries are supposed to accomplish.

The purpose of the plenaries is (1) to get the community all together and thinking about some problem relevant to the IETF (tech plenary) and (2) to get the community all together and thinking about how to run the IETF properly (admin plenary).

I think both could be streamlined and made more useful, and I actually think the tech plenary tends to be a missed opportunity—interesting, but not all that relevant to building connection within the IETF or making IETF participants aware of what other IETF participants are working on.   That’s a shame.

v2.8.7 | Report a Bug | By Email