Re: Updating BCP 10 -- NomCom ELEGIBILITY

Brian Trammell <ietf@trammell.ch> Fri, 13 February 2015 21:50 UTC

Return-Path: <ietf@trammell.ch>
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 775171A1A87 for <ietf@ietfa.amsl.com>; Fri, 13 Feb 2015 13:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-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 Z6KsfsBnf_kz for <ietf@ietfa.amsl.com>; Fri, 13 Feb 2015 13:50:55 -0800 (PST)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id C29C11A0AFE for <ietf@ietf.org>; Fri, 13 Feb 2015 13:50:54 -0800 (PST)
Received: from [IPv6:2001:470:26:9c2::7ea] (unknown [IPv6:2001:470:26:9c2::7ea]) by trammell.ch (Postfix) with ESMTPSA id 7EEF31A02FA; Fri, 13 Feb 2015 22:50:53 +0100 (CET)
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_49DC2752-3797-4066-B161-B883D7569C48"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b4
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <CABmDk8m1KuSs8os9V7fcYOJC2O4yMb6dRFer+nEPBTTSHtey9Q@mail.gmail.com>
Date: Fri, 13 Feb 2015 22:50:53 +0100
Message-Id: <31891031-4628-49CD-B66C-38A3BD787B70@trammell.ch>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <6025.1423672358@sandelman.ca> <CAL0qLwYtE618sA99hgXP-5wk+BYdcXLbiZqd_36OreYQ1LB7hQ@mail.gmail.com> <54DBD71C.20101@joelhalpern.com> <26803.1423772214@sandelman.ca> <tsla90ikh85.fsf@mit.edu> <37661D4B-1842-4890-88FB-2A7B13CDC884@nominum.com> <CABmDk8m1KuSs8os9V7fcYOJC2O4yMb6dRFer+nEPBTTSHtey9Q@mail.gmail.com>
To: Mary Barnes <mary.h.barnes@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/OHESh48Bue2GBHVeN53TNNVbChU>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Sam Hartman <hartmans-ietf@mit.edu>, ietf <ietf@ietf.org>
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: Fri, 13 Feb 2015 21:50:57 -0000

hi Mary, all,

> On 13 Feb 2015, at 22:30, Mary Barnes <mary.h.barnes@gmail.com> wrote:
> 
> On Fri, Feb 13, 2015 at 2:58 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> On Feb 12, 2015, at 3:27 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> > In the past I've been nervous about giving remote participation too much
> > power in part because I'm worried about how that impacts meeting fees
> > and in part because I value cross-area involvement.
> 
> It's possible that we could collect meeting fees from remote attendees, offering a hardship exemption for those who can't afford it.   That would depend on remote attendance working better than it does now, I think, but it would be unfortunate if the main impediment to making remote attendance work well were that we didn't want to lose meeting revenue.
> 
> [MB] I totally agree on this latter point.  I'm very conflicted about charging for remote participation, but perhaps something nominal.  It's also quite possible that if we improve the quality, we will get more remote participants.

A requirement (at least at first) to allocate n% of remote participation fees directly to expenses related to the improvement of remote participation would make this a lot more feasible.

Cheers,

Brian

>  And, I obviously, would be perfectly happy for IETF to cut back (or do away with) all the food and possibly beverage and not worry, for example about providing IETF breakfast in cases where it's not part of the room rate.    I know that the model is complex in terms of cost of meeting rooms being based frequently on  the amount of food and beverage provided, so I'm not suggesting this is simple or would have a huge impact on overall cost.  And, yes, I know that there would be a huge uprising about this, but we could request the hotels to setup carts, etc. where people can purchase snacks and drinks during breaks as they often do for lunches and perhaps the potential revenue that they can get from that could be factored into the contract to offset the reduced catering request.
> [/MB]
>