Re: Updating BCP 10 -- NomCom ELEGIBILITY

Avri Doria <avri@acm.org> Sat, 10 January 2015 16:50 UTC

Return-Path: <avri@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A363A1A01C6 for <ietf@ietfa.amsl.com>; Sat, 10 Jan 2015 08:50:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no
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 ZbwrlntIPcfF for <ietf@ietfa.amsl.com>; Sat, 10 Jan 2015 08:50:15 -0800 (PST)
Received: from atl4mhob11.myregisteredsite.com (atl4mhob11.myregisteredsite.com [209.17.115.49]) by ietfa.amsl.com (Postfix) with ESMTP id DB8011A00FF for <ietf@ietf.org>; Sat, 10 Jan 2015 08:50:14 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t0AGoD4i016462 for <ietf@ietf.org>; Sat, 10 Jan 2015 11:50:13 -0500
Received: (qmail 7816 invoked by uid 0); 10 Jan 2015 16:50:13 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 10 Jan 2015 16:50:13 -0000
Message-ID: <54B15842.9040905@acm.org>
Date: Sat, 10 Jan 2015 11:50:10 -0500
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <54B02B51.1070308@cs.tcd.ie> <5237.1420905553@sandelman.ca>
In-Reply-To: <5237.1420905553@sandelman.ca>
Content-Type: multipart/alternative; boundary="------------030300090908040202040704"
X-Antivirus: avast! (VPS 150110-0, 01/10/2015), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2uLRh_dHaihtCGIGHu-vPRt5-Rw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2015 16:50:17 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi,
On 10-Jan-15 10:59, Michael Richardson wrote:
> But, if one totally looses eligibility, then the reason why I think one has
> to do more attendance in person is because things *do* change over
> time. 3-step vs 2-step.  Creation of IAOC.  Use of jabber+streamed mp3 vs
> meetecho vs using multicast and vat.  The rise of webrtc... How much
of this
> matters to the nomcom, is unclear; but one definitely gets more
> cross-polination by being in the hallway, than by being in the hallway
chat.

Agree with this.  As someone who stopped attending for a while and is
now attending again - at least intermittently, i did find changes that I
had not perceived while remaining active in a few online efforts.

While one can participate remotely, it is not the same and there is an
essential component of the IETF that is found only in meeting attendance.

avri

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
 
iQEcBAEBAgAGBQJUsVhCAAoJEOo+L8tCe36HkukIAIVtmHnIWFPhupPJbjBimwO/
6TK/NheV8YZ2/K2puAfoPEd4sp2GmdhE+UWVhNM26S8hZw/9Z8xZj70wDXMOjrV4
ekR3DEdvCwgq9qq/dOXXYlXcrWi5HbKnsw6QxrB0+yfHc49lrTCTO4E5g/b5Orx4
BlDxrCOsfp7p75DExSBk4YzyiwiXGiPf1WLbDyfH1O8X5I9PpbxaGwahRNrC8fPL
8ihMLLO2uXn0/VfDKzEt8zRBpCh48MCoNq760CeoonECpmek4Lbz5xvizGWYzH15
6z2xNS6gGU2/3umZY7tziZD1bVnTmzgqjK5iG61IlDkSWoujmOROn7RMD2+nqDo=
=1OHi
-----END PGP SIGNATURE-----