Re: IETF chair's blog

jari.arkko@piuha.net Mon, 25 February 2013 16:33 UTC

Return-Path: <jari.arkko@piuha.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 C9EB421F9370 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level:
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 HPpPud2x+SDq for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:33:51 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 746CD21F94A2 for <ietf@ietf.org>; Mon, 25 Feb 2013 08:33:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6584A2CC4A for <ietf@ietf.org>; Mon, 25 Feb 2013 18:33:47 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mr6PVzF5-Ttg for <ietf@ietf.org>; Mon, 25 Feb 2013 18:33:46 +0200 (EET)
Received: from www.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3B48C2CC3B for <ietf@ietf.org>; Mon, 25 Feb 2013 18:33:46 +0200 (EET)
Received: from 114.123.150.111 (SquirrelMail authenticated user jarkko) by www.piuha.net with HTTP; Mon, 25 Feb 2013 18:33:46 +0200
Message-ID: <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
In-Reply-To: <512B74F7.5060506@gmail.com>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it> <512B74F7.5060506@gmail.com>
Date: Mon, 25 Feb 2013 18:33:46 +0200
Subject: Re: IETF chair's blog
From: jari.arkko@piuha.net
To: "ietf@ietf.org" <ietf@ietf.org>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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 16:33:52 -0000

Thanks everyone for the feedback, on and off list.

We did the blog primarily as a means to convey more thoughts and encourage
discussion. That's the content part. We'll see later how that works out.

The medium part is orthogonal, but interesting. For this stage we thought
that an IETF-server based web system would work nicely, even if we could
have done all on pure e-mail mode as well. I do have a question mark on
how to handle comments, however. It seems that open blog commentary on web
system will invite plenty of spam, so where does that leave us? Ask for
comments to be sent on this list, i.e., e-mail commentary? We seem to be
in that mode already... Or should we implement some specific spam
protection scheme that will save me and the secretariat from manual work
in checking postings? A tools-login required for posting comments? Or
something else, what?

Going further, you asked about social media and material on external
systems. This is not on the agenda for the current blog experiment (except
in a small way, see below). But it is something that we should find an
answer to eventually.

I am of the opinion that long-term, the IETF can not stay away from the
collaboration and discussion tools that majority of the Internet users are
using, including social media. But we need to control how this happens,
and I do worry about being able to own our own content and providing
everyone an equal access to it. I'd like to make a separation between
spreading information from the IETF across multiple media, hosting that
information in the external medium, and making an external medium the only
way to participate. I think we should stay away from the latter two
approaches. But the first one is benign, I think. As an example, we were
planning to send out a tweet from the IETF tweeter account about the
creation of the blog, with an URL back to the IETF site. (If I had even
the beginnings of an Internet connection I could check if that went out. I
also don't know if this e-mail will go out.)

Jari