Re: IETF chair's blog

Arturo Servin <aservin@lacnic.net> Mon, 25 February 2013 08:49 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 69BD021F91D5 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 00:49:08 -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 bx94VnE41TuX for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 00:49:08 -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 D099221F91B0 for <ietf@ietf.org>; Mon, 25 Feb 2013 00:49:07 -0800 (PST)
Received: from MiniR2D2.local (unknown [IPv6:2001:df9:0:4022:801e:caa:204d:5dbb]) by mail.lacnic.net.uy (Postfix) with ESMTP id DE237308469; Mon, 25 Feb 2013 06:48:57 -0200 (UYST)
Message-ID: <512B257A.3030902@lacnic.net>
Date: Mon, 25 Feb 2013 16:48:58 +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: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
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 08:49:08 -0000

Fred,

	I am not convinced that social nets (proprietary or not) are yet a good
tool to do IETF work. They are good to communicate one-way and some
informal two-ways, but that's all (at least for now)

	What I had in mind was something very simple such that the IETF chair
could do is to automatically post to twitter, facebook, etc whenever
there is a new post from his blog and receive from communication using
those tools (besides the comments in the blog). But that is all.
	
	About using an open social net approach	I think there could be some
value but not sure if we are there yet, I will give it some thoughts
anyhow and how it could be done.

Regard,
as

On 25/02/2013 15:05, Fred Baker (fred) wrote:
> Arturo, my suggestion: in some context, after discussion with the working-group-or-whatever-in-question, use one of the tools you mention to accomplish IETF work. Take careful notes of what proportion of the indicated community (if the IPv6 Operations WG, for example, the participants in v6ops) join the discussions, and what contribution those discussions make. Think about archives, focused issue discussion (what SMTP readers call "threads"), and so on. Then write a draft documenting the outcome of that.