Re: IETF chair's blog

Carsten Bormann <cabo@tzi.org> Mon, 25 February 2013 17:58 UTC

Return-Path: <cabo@tzi.org>
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 4EF0621E804B for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 09:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.138
X-Spam-Level:
X-Spam-Status: No, score=-106.138 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 id7B3sLpOlGE for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 09:58:14 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 73C9621F92DF for <ietf@ietf.org>; Mon, 25 Feb 2013 09:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id r1PHw0pN015280; Mon, 25 Feb 2013 18:58:00 +0100 (CET)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CCE233955; Mon, 25 Feb 2013 18:58:00 +0100 (CET)
Subject: Re: IETF chair's blog
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
X-Priority: 3 (Normal)
In-Reply-To: <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
Date: Mon, 25 Feb 2013 18:58:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <039FF5C1-3BCE-40F6-BAC5-FD856AC98084@tzi.org>
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> <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
To: jari.arkko@piuha.net
X-Mailer: Apple Mail (2.1499)
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 17:58:28 -0000

On Feb 25, 2013, at 17:33, jari.arkko@piuha.net wrote:

> A tools-login required for posting comments?

In a ~ 20-year IETFer, it evokes a bit of a smirk to see the IETF now starting to define its social media strategy...

The answer to the question depends on whether you want to engage IETFers only or a larger public.

If it is IETFers only, this mailing list is fine.
(The tools login is an even narrower group.)

A blog can be useful for addressing a larger public.  
It's going to be far cry from Obama's tweets, but it's better than posting to an internal mailing list.

If this is supposed to be two-way communication and you want to get input from the larger public, be prepared for some loss of control.

Spammers aren't really the problem these days; there is pretty good software to minimize their impact.

People who genuinely want to engage you but are adding more noise than signal are the real problem.

We have enough experience with people who live in a completely different reality than most of us do.  Imagine running an appeals process through this blog.
(There are also people within the IETF that are well-respected for their technical input but still live in a slightly different reality from the rest of the world; their statements can become off-message for you quickly.)
So there needs to be a policy when comments are hidden or even deleted (no, that's not censorship), and this policy may need to be made known.  It will be debated.
There also need to be people who maintain response times within some reasonable latency while you are out skiing -- a response, maybe not the final solution.

Reaching out from an organization into social media tends to become a pretty big operation quickly, if it is done in a professional way.
But it may be worth it.
At least you don't have the SEC coming after you if you happen to make the wrong kind of statement.
Doing this with an appropriately personal touch may be the natural approach for us, but most of the work items do remain.

Grüße, Carsten