Re: [ericas] IETF Meeting in South America

S Moonesamy <sm+ietf@elandsys.com> Fri, 24 May 2013 19:54 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ericas@ietfa.amsl.com
Delivered-To: ericas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B08B311E8105 for <ericas@ietfa.amsl.com>; Fri, 24 May 2013 12:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.774
X-Spam-Level:
X-Spam-Status: No, score=-101.774 tagged_above=-999 required=5 tests=[AWL=-0.504, BAYES_00=-2.599, NA_DOLLARS=1.329, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id caASk-lu9eSY for <ericas@ietfa.amsl.com>; Fri, 24 May 2013 12:54:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 05FFC11E80FB for <ericas@irtf.org>; Fri, 24 May 2013 12:54:01 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.152.207]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4OJrb85027594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 12:53:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369425230; bh=+ZEcD7GbVfbtY/kO7rEqoI6hXrxAl0H7dFuYC3YCS3Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FcPg4EZFCepOMNYqtoG93pe+93Jt1OSf18+72njdSIBGXxCHjM4EvCZS3n+zroUgX AGxc0fNNTn9eW+HVvx0Qn/pw48T3777HFQlDtwIeI6r7Ttm+Pl8b2rkbWXt0G/kp2h 829ob0Y4SVZBvrL1pJ47NoZSYSAEFa8VXqP5uuHI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1369425230; i=@elandsys.com; bh=+ZEcD7GbVfbtY/kO7rEqoI6hXrxAl0H7dFuYC3YCS3Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GYaoDw1RjjlkyBFkFWC92ZaZj2zCigdz7+MhnyMbNZde4YYEqz9rImF5nR6+dAkQo it3KtfFXU9iyTa3wxe9RXWa9jpJb1oMs0qQQhJl5rBc8Wxt8fCjh4YiQANMgmhYnn1 rhdKPP4Ojw9oWNZkqNUGoMuvIZAeTXG/JuEHG4kM=
Message-Id: <6.2.5.6.2.20130524112639.0dc47308@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 May 2013 12:18:26 -0700
To: Juliao Braga <juliao@braga.eti.br>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <519FA104.5020902@braga.eti.br>
References: <519FA104.5020902@braga.eti.br>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: j@braga.net.br, ericas@irtf.org
Subject: Re: [ericas] IETF Meeting in South America
X-BeenThere: ericas@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for \"Emerging Regions Internet Challenges And Solutions\" \(ERICAS\) " <ericas.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/ericas>, <mailto:ericas-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/ericas>
List-Post: <mailto:ericas@irtf.org>
List-Help: <mailto:ericas-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/ericas>, <mailto:ericas-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 19:54:02 -0000

Hi Juliao,
At 10:19 24-05-2013, Juliao Braga wrote:
>I'd like to remember that the Regional IETF Meetings not necessarily
>must to have the same format as Annual Meetings. The main concern is
>that they are (a) motivators for participation in the Annual Meetings,
>(b) strengthen and give more flexibility in the progress of WG (not that
>the progress is slow, currently), and (c) encourage participation in
>Annual Meetings, even remotely, including write drafts, doing reviews as
>Melinda said.

The IETF revenue from meeting registration fees is around three 
million US dollars.  IETF expenses are around five million US 
dollars.  ISOC contributes around two million US dollars to the IETF.

LACNIC's budget is about four and a half million US dollars.  ICANN's 
revenue is around 232 million US dollars.  ISOC's revenue is around 27 million.

Let's assume that there are four Regional IETF meetings and they cost 
around two million US dollars.  The IETF does not have money to pay 
that cost.  That cost is about half of LACNIC's budget.  As I know 
that I cannot suggest that LACNIC helps out with the cost.  I don't 
know whether ICANN or ISOC would help with the cost.  Let's assume 
that money is not a problem.  You still have to get at least the main 
WG participants at the meeting.  Each individual will have to spend 
about ten thousand US dollars per individual.  In my opinion a format 
which is a scaled-down version of an IETF (Annual) meeting is not workable.

There are interesting points in your message:

  (a) motivators for participation

  (b) helping people from South America participate in the IETF

Both points require money.  Somebody will have to have to convince 
organizations to give, for example, one million US dollars.  The next 
step would be to identify people who are motivated to 
participate.  The "helping people" is the most difficult part.  I 
think it is doable with a lot of effort.  It is more than one year to 
do all this.  Most of the effort will have to come from people from 
South America.

>Whenever possible I'm talking about the IETF in articles and lectures,
>as you know. I'm returning to my academic life and therefore will be
>more effective in spreading within the Brazilian Computer Society (SBC).

This is what could be described as "outreach".  You could try and 
convince LACNIC or CGI.br to help out.

>IETF will create a form and we can ask in the mailing list of SBC (and
>others). Who knows we can have numbers and others informations?

Could you ask the people from SBC to comment on this mailing list 
about the above?

In another message you mentioned that there is very low participation 
from Brazil.  There are one or two persons from Brazil who 
participate in DNS-related discussions.  That's like participating in 
two IETF working groups.  Most of the IETF work is not about DNS.  As 
a starting point I suggest asking people from Brazil to come and 
discuss on this mailing list if they need help in finding out which 
IETF working groups may be relevant to what they are interested in.

Thanks,
S. Moonesamy