Re: IETF chair's blog
Hector Santos <hsantos@isdg.net> Mon, 25 February 2013 18:59 UTC
Return-Path: <hsantos@isdg.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 BDF0921F9300 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 10:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.897
X-Spam-Level:
X-Spam-Status: No, score=-101.897 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, 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 amwSM9m7zG3E for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 10:59:13 -0800 (PST)
Received: from ftp.catinthebox.net (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3853621F91B0 for <ietf@ietf.org>; Mon, 25 Feb 2013 10:59:08 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3130; t=1361818742; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=rjqZpgz oFpWEkTy1pQ4cPK27aVc=; b=bYtW/MM9zxsVwvt/ozbBVDkaI48dSI9ZRpEA3XR g9GFb7BjxZ3rkh/vPYnevkRG0toPhnCogBhOUEKs7vQEW+zHPiH64c3Zfe3SJdfU gZ7Z28ZqwfDONU/ghakYtVX9mFZ3tUEupIindhjEaNvko5/V8spIycBFHvvx6eW0 VeEk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 25 Feb 2013 13:59:02 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 612489518.1761.3208; Mon, 25 Feb 2013 13:59:01 -0500
Message-ID: <512BB403.60900@isdg.net>
Date: Mon, 25 Feb 2013 13:57:07 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
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> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it> <512B74F7.5060506@gmail.com> <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
In-Reply-To: <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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 18:59:13 -0000
Its not really orthogonal if you are seeking a feature list. Will it be out-sourced, open source or in-house developed? That's the dilemma with most older establishments that do not wish to provide less support for its long time "customers" but need to also migrate and provide other methods as well. Overall, its a game of how much do you single source the publishing and the basic service communications with multiple portals I/O methods. You will get redundancy if you don't single source. Personally, you should start with single sourcing the web blog entries either with the IETF mail list or another "IETFBLOG" mailing list. Adding a tweet notification can be optionally provided, just don't focus on it as a principle method, at least not yet. I would consider RSS feeds as well. The follow-ups should perhaps begin within the list. There is also the archive view that can be done starting with blog mailing list entry. -- HLS On 2/25/2013 11:33 AM, jari.arkko@piuha.net wrote: > 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 >
- IETF chair's blog IETF Chair
- Re: IETF chair's blog Hector Santos
- Re: IETF chair's blog Alejandro Acosta
- Re: IETF chair's blog DM Abreu
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Brian Trammell
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Martin Sustrik
- Re: IETF chair's blog Fred Baker (fred)
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Brian E Carpenter
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog Michael Tuexen
- Re: IETF chair's blog Simon Pietro Romano
- Re: IETF chair's blog Brian E Carpenter
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Alejandro Acosta
- Re: IETF chair's blog Dale R. Worley
- Re: IETF chair's blog jari.arkko
- Vendor standardization (was: IETF chair's blog) SM
- Re: IETF chair's blog Simon Pietro Romano
- Re: IETF chair's blog Carsten Bormann
- Re: IETF chair's blog Hector Santos
- Re: IETF chair's blog Randy Bush
- Re: IETF chair's blog Marc Petit-Huguenin
- Re: IETF chair's blog Randy Bush
- Re: IETF chair's blog Arturo Servin
- Re: IETF chair's blog falsehood911
- Re: IETF chair's blog Carlos M. Martinez
- Meetecho archive down? / Availability of collabor… Simon Leinen
- Re: Meetecho archive down? / Availability of coll… Simon Pietro Romano
- Re: Meetecho archive down? / Availability of coll… Simon Leinen
- Re: Meetecho archive down? / Availability of coll… Simon Pietro Romano