Re: [vmeet] what's been working/failed/tried in hubs?

Vinayak Hegde <vinayakh@gmail.com> Tue, 11 October 2016 09:07 UTC

Return-Path: <vinayakh@gmail.com>
X-Original-To: vmeet@ietfa.amsl.com
Delivered-To: vmeet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F086F1297FC for <vmeet@ietfa.amsl.com>; Tue, 11 Oct 2016 02:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FoII2HhHERdu for <vmeet@ietfa.amsl.com>; Tue, 11 Oct 2016 02:07:18 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56DFB1297F9 for <vmeet@ietf.org>; Tue, 11 Oct 2016 02:07:17 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id x79so31726276lff.0 for <vmeet@ietf.org>; Tue, 11 Oct 2016 02:07:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IIUoM4ta2AobiDbEinAZ7HDIFUxKN1tQhiH0ScEs3oU=; b=c63d1OPlTyceXf8hQX1h7hqp9W58p7ZFg3esmS/JTPVCOW4dtvESWe1xBu7n8lk36B pYviUe3Ub0GoJ+lKP+hAhr1Ak3Af8EB4QUyS0wjIRZ+oxmFhbVBJgvELru2Qj/kj8DMc rHnTvSL42EgF6YhFwUxpkR5/5VzghN1f/0mBCzOWFGQtn8x+z1NVJD8i/oj6tkwcUrmR HyDYtxi32bt6r9F49bqXEeXIJVufP0Kpptq9tpzEAWWUvCm4SrSJ9ig10Mivo7Bdh5sF 7hKfZfSJIRgo1lUL+eVgencI1xnYUOtI/YkLQn1ne4+GgnyXnbC7+zfJwqIAlaCbRhd5 sy5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IIUoM4ta2AobiDbEinAZ7HDIFUxKN1tQhiH0ScEs3oU=; b=A+g3ohShb4RS+6Exgld1dGOeQb9PVXU80pblFkx+DjhSUpXivMetNWox9D27k9SIct azh9WHYeswxRpmha5R6Tl3NvbwvanJtvScmN042RQhqhqIJbMHpj3BtdJoBdQFoqwqoK Ca4Zrk7KYaUdCyG6xLia38K7fA3tcyJctpvMDLpdHVgluCr7FaKZ9nf8sQRcDt5hjSkh rcteMPV/bpu8ku4AGMhUNs90kYeumGRGgfdTPSzJPoWacPJ2YL2DN0gv0qU08+2nzIJI oMTpWOC1lT9vx0Lfxb80NSpv38x9JiGzxJTsARV/7OKD4eg9G8KJjJIkVQKvQRKa1z3X yrjQ==
X-Gm-Message-State: AA6/9RmnIA/iw6JUlHPpIwBO+hOM4sn/m4R5GIDAG/SO9xglBdMbae7+QH24mGSOx7ir8OPFCndoyFQ3QYnV/A==
X-Received: by 10.194.115.168 with SMTP id jp8mr3512766wjb.27.1476176830700; Tue, 11 Oct 2016 02:07:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.96.37 with HTTP; Tue, 11 Oct 2016 02:07:10 -0700 (PDT)
In-Reply-To: <20161010114451.GO94244@verdi>
References: <CAG4d1re1td4oaPpHMHn7Ka4OYT37B6QRsygM1uvWZhDTzqyJGA@mail.gmail.com> <CAB75xn79vU1xyv9Bk=5LHjDekRkO9ARwN9A8pCXRhuJF5Cm9vg@mail.gmail.com> <20161010114451.GO94244@verdi>
From: Vinayak Hegde <vinayakh@gmail.com>
Date: Tue, 11 Oct 2016 14:37:10 +0530
Message-ID: <CAKe6YvO2Kg-4oDHNc_2BLCycvQxEFCsFNEEt3hOrD_oyKj7XdQ@mail.gmail.com>
To: John Leslie <john@jlc.net>
Content-Type: multipart/alternative; boundary=001a1130d1f29ea1bc053e933322
Archived-At: <https://mailarchive.ietf.org/arch/msg/vmeet/EB84tEbNgJSGsI92vUeTc1mTYS4>
Cc: vmeet@ietf.org
Subject: Re: [vmeet] what's been working/failed/tried in hubs?
X-BeenThere: vmeet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF remote participation meeting services discussion <vmeet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vmeet>, <mailto:vmeet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vmeet/>
List-Post: <mailto:vmeet@ietf.org>
List-Help: <mailto:vmeet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vmeet>, <mailto:vmeet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2016 09:07:20 -0000

Hi John,

My draft with some observations has some answers to your questions. Also
some answers inline.
https://tools.ietf.org/html/draft-hegde-remote-hubs-india-01

On Mon, Oct 10, 2016 at 5:14 PM, John Leslie <john@jlc.net> wrote:

> Dhruv Dhody <dhruv.ietf@gmail.com> wrote:
> >
> > (1) WG champion: Having one or two WG champion at the Hub helped to set
> the
> > tone, go over the WG agenda in advance, answer questions and continue the
> > discussion after the WG meeting.
>
>    What time commitment is expected? (I assume the expertise expected is
> for a single Working Group.)
>

Not much. If you are alone with few people. Only time needed to attend the
WG meeting
and maybe some time to send out invites. The barrier (effort) for
participation is quite low.


> > (2) Discussions/Hot-Topics: Most participants can join remotely on their
> > own from home/work. We need to make it worthwhile for someone to travel
> to
> > the Hub, so it is important that we make sure that the hub can offer
> > something more.... This could be a lively discussion, networking, side
> > meetings on some HOT technology, tutorial etc.
>
>   What's your experience with folks who need to follow more than one
> stream?
> (I have had to remain near-home in order to cover everything I need to.
> Perhaps an academic setting could maintain 8 rooms; but essentially no
> workplace can do that.)
>

This works best when people are on the same academic campus or there is a
cluster
of offices in IT parks nearby. You can pick and choose sessions based on
your expertise
and specific interests in your remote group (mostly it will be areas like
Routing or Apps).
or it could be general like a Tech Plenary.


> > (3) Agenda - getting the IETF agenda early, would help a lot in making
> the
> > sub-set agenda for the hub based on interest/timezone etc.
>
>    What do you mean, early? Alia certainly has access to _premature_
> agendas;
> but I'm not sure they'd be helpful. And, of course, agendas _do_ change
> even
> after the start of an IETF week...
>

I think he was talking about WG areas but these are subject to change as
well.

Thanks
Vinayak