Re: Remote Hubs

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 10 March 2016 09:10 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E3B12D5D5; Thu, 10 Mar 2016 01:10:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 OwP8HUktBuh2; Thu, 10 Mar 2016 01:10:53 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D3DA12D5B7; Thu, 10 Mar 2016 01:10:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DDF5BBE5B; Thu, 10 Mar 2016 09:10:51 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-0hY0qTntZv; Thu, 10 Mar 2016 09:10:50 +0000 (GMT)
Received: from [10.87.49.100] (unknown [86.46.23.221]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7E992BE39; Thu, 10 Mar 2016 09:10:49 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1457601050; bh=3TaMcH6aFbRpPMYB7nK20HQE0XI5DaWKt/ZPIF9kWoI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=cpjNyoFJ4aD93eGgJSS6J7q4bStEBrqnosX/TZkJnsuCgYzIg+LEVeVD372rPzWHA 7o99GtjVgx9pYbuWHuGEhfOQyLLHVfF3MWMVowe8Esn8nG7FQtA3Tcc0SoyZ9ABE5K dC5AUto42L7pm0Gcwg+6LPHerLJBq9mAzAZQhweE=
Subject: Re: Remote Hubs
To: nalini.elkins@insidethestack.com, IETF Discussion List <ietf@ietf.org>, "vmeet@ietf.org" <vmeet@ietf.org>
References: <1022465394.3606828.1457568222041.JavaMail.yahoo.ref@mail.yahoo.com> <1022465394.3606828.1457568222041.JavaMail.yahoo@mail.yahoo.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56E13A19.8040800@cs.tcd.ie>
Date: Thu, 10 Mar 2016 09:10:49 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <1022465394.3606828.1457568222041.JavaMail.yahoo@mail.yahoo.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070103060406020306060700"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fL5Nb2MEj4ZHn6fqE98x7zC7Khw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Mar 2016 09:10:55 -0000

Hiya,

I had a read of those. I think we should encourage particularly
the organic kind of remote hub (a la Christian's draft). I'm
less sure of the benefits of trying for sponsored larger things,
as would seem to be implied by the iicb.org site. (Was that done
for IETF94 too or just 93?) Anyway, thanks for documenting this
and for the folks who're working on having hubs happen.

Two comments:

1. Christian's draft says:

"  3. Notify the IETF about your remote hub if you want it included in
   the public remote IETF WG Hubs list"

I wasn't aware that there's such a list. Seems like a fine thing
but even better if the WG chairs are told about it, say on the
Sunday of IETF week. I think the people in the room would be
interested to know that there are semi-organised sets of folks
remotely participating from places X, Y and Z. (I've no idea
what one might do with that information, but people often figure
out stuff if we let 'em know what's up:-)

2. If people want to use the IETF logo to advertise that you can
turn up somewhere and participate remotely in a session, and if
nobody's trying to make money from the punters, I think we should
allow and encourage such uses of the logo. I'd be happy to help
annoy the trust to try get 'em to write down what's ok there, if
that's not already being worked on by someone. (Or to encourage
people to just use the logo like that and ask for forgiveness
later:-)

Cheers,
S.



On 10/03/16 00:03, nalini.elkins@insidethestack.com wrote:
> All,
> 
> We have written a summary of the current thinking on Remote IETF hubs as well as what has been done in Latin America.  There is also quite a bit of activity in India with remote hubs. 
> They will be posting a draft soon.
> 
> We wrote these to serve as community memory and to serve as a starting point for discussion.  As our knowledge of how to do remote hubs increases, we will update the drafts.
> 
> Please view: 
> 
> https://datatracker.ietf.org/doc/draft-elkins-ietf-remote-hubs/
> 
> and
> 
> https://datatracker.ietf.org/doc/draft-oflaherty-ietf-remote-hubs-lac/
> 
> 
> Please let us know any comments or suggestions.
>  
> Thanks,
> 
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
> 
>