Nadine,

For the benefit of others who may be remote, a link for this
session is now up on the Meetecho part of the remote
participation page.  To save time hunting for the link, it is
http://www.meetecho.com/ietf94/remotehubs

Simon (and team), thanks.
    john


--On Wednesday, November 04, 2015 04:39 +0000
[email protected] wrote:

> We have changed the room assignment for the Bar BOF in
> Yokohama to discuss the idea of Remote Hubs.  It will be in
> Room 301 so that we can have remote participants.   Have had
> interest from a number of people to participate remotely.  
> Time: Thursday, Nov. 5th 7:45am-8:45am.   
> Breakfast will NOT be provided.  (Sorry!)     Please let me
> know any questions you may have.  Agenda
> ------
> 1.  We come up with some templates for remote hubs in our
> meeting  2.  We have some goals for remote hubs for IETF95.
>  For example:  U.S. : 5 hubs Latin / South America: 5
> hubs India : 5 hubs  ... etc. 
> A hub can decide which remote hub template they want to use. 
> 3.  Sister hubs : hub-to-hub interaction.  Should this be
> done, if so, how? 4. We do an I-D describing our thoughts (due
> date: Jan. 1st, 2016)  5.  We post the I-D on the IETF
> discussion list for comments.  (Due date: Jan 10, 2016)  6.
>  We try to meet our goals for remote hubs!  (Due date:
> February 15, 2016)  Issues---------
> 1.  Many people cannot afford to attend IETF meetings live.
> 2.  It can be more interesting and useful to attend remote
> meetings as a group.  The face-to-face (F2F) interaction adds
> a great deal to the overall process. 3.  Some regions (Latin
> America, India) have already started remote hubs.  We can
> learn from each other.  4.  We are starting Regional
> Mentoring.  Such mentors can work with remote hubs.  Thanks,
> Nalini ElkinsInside Products, Inc.www.insidethestack.com(831)
> 659-8360




_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html.
https://www.ietf.org/mailman/listinfo/vmeet

Reply via email to