Re: IETF chair's blog

Arturo Servin <aservin@lacnic.net> Mon, 25 February 2013 07:00 UTC

Return-Path: <aservin@lacnic.net>
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 5257E21F91F5 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:00:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNi6TEPLpnZT for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:59:59 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8C121F91ED for <ietf@ietf.org>; Sun, 24 Feb 2013 22:59:59 -0800 (PST)
Received: from minir2d2.local (unknown [IPv6:2001:df9:0:4017:e42c:c034:61ed:fff8]) by mail.lacnic.net.uy (Postfix) with ESMTP id DD451308424; Mon, 25 Feb 2013 04:59:40 -0200 (UYST)
Message-ID: <512B0BDE.8060700@lacnic.net>
Date: Mon, 25 Feb 2013 14:59:42 +0800
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.ch>
In-Reply-To: <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.ch>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 25 Feb 2013 07:00:00 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


	I meant outreach, not collaborate.

	In the case of collaboration I agree with you. Although today we use
webex that does not seem to open to me (at least not more than FB,
Google+ and twitter).

	In the case of outreach it does not matter to me if we are using
closed or open applications.

/as

On 25/02/2013 14:52, Brian Trammell wrote:
> Hi, Arturo, all,
> 
> It does not seem appropriate for a technical standards organization
> dedicated to making the Internet work better through the
> development of open standards to implicitly endorse "communication
> protocols" which are based on closed access to distributed
> databases through interfaces that can and do change at the whim of
> the organizations that control them, further where those
> organizations have demonstrated a willingness to assert editorial
> control over the content they disseminate.
> 
> If a social network were to emerge that allows open participation
> at _every_ level, based on an open application protocol therefor,
> that would be something different. I fear that network effects have
> already made  such a thing unlikely in this iteration of "Internet
> x.0".
> 
> (Aside: I myself have used all three listed networks to get
> attention for ISOC functions at the chapter level, though I'm
> uneasy about that. I won't dispute that they're great for outreach,
> and when you're doing outreach, you have to go where the people
> are. In my defense, though, I was advertising a talk wherein I
> discussed why it's a bad idea to rely on such closed platforms. :)
> )
> 
> Cheers,
> 
> Brian
> 
> On Feb 25, 2013, at 2:21 AM, Arturo Servin <aservin@lacnic.net>
> wrote:
> 
>> 
>> Why not?
>> 
>> I, my organization and many more (included ISOC) have found them
>> very useful for outreach activities. I do not see why the IETF
>> shouldn't. Please, tell me.
>> 
>> 
>> as
>> 
>> Sent from my iPad
>> 
>> On 25 Feb 2013, at 02:21, Marc Petit-Huguenin <petithug@acm.org>
>> wrote:
>> 
> On 02/23/2013 07:38 PM, Arturo Servin wrote:
>>>>> 
>>>>> Very good initiative.
>>>>> 
>>>>> Twitter, Google+, Facebook, etc. could be the next steps.
>>>>> Let's embrace new tools to collaborate.
> 
> Let's not.  Collaboration based on software running on servers run
> by the IETF or a contractor payed by the IETF is fine.  Using
> collaboration tools owned by the entities you listed, or similar
> entities, is not.
> 
>>>>> 
>>>>> Regards, as
>>>>> 
>>>>> On 22/02/2013 20:35, IETF Chair wrote:
>>>>>> Jari has created a blog as an experiment to see if would
>>>>>> be possible to provide periodic status reports and other
>>>>>> thoughts from the chair. Here's the link:
>>>>>> 
>>>>>> http://www.ietf.org/blog/2013/02/chairs-blog/
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlErC94ACgkQr8mvgVZWPglc7wD/ZpaDDjPL8QYgcZrQH0xX+KD/
WOypj8I57wHOnJcfGNcA/jErGblgtaJuhgde5og6u5SE80bqmJBqcyxXfxUv/WOK
=37Ql
-----END PGP SIGNATURE-----