My draft with some observations has some answers to your questions. Also
some answers inline.
On Mon, Oct 10, 2016 at 5:14 PM, John Leslie <j...@jlc.net> wrote:
> Dhruv Dhody <dhruv.i...@gmail.com> wrote:
> > (1) WG champion: Having one or two WG champion at the Hub helped to set
> > 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
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
> > 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
> (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
of offices in IT parks nearby. You can pick and choose sessions based on
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
> > sub-set agenda for the hub based on interest/timezone etc.
> What do you mean, early? Alia certainly has access to _premature_
> but I'm not sure they'd be helpful. And, of course, agendas _do_ change
> after the start of an IETF week...
I think he was talking about WG areas but these are subject to change as
NOTE WELL: This list operates according to