Re: Long-term IETF evolution thoughts
Ross Finlayson <finlayson@live555.com> Mon, 13 June 2016 20:47 UTC
Return-Path: <finlayson@live555.com>
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 A000F12DA04 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2016 13:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.316
X-Spam-Level:
X-Spam-Status: No, score=-3.316 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s6_FktTvJXg1 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2016 13:47:01 -0700 (PDT)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58AD412DA0A for <ietf@ietf.org>; Mon, 13 Jun 2016 13:46:38 -0700 (PDT)
Received: from [127.0.0.1] (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.15.2/8.14.9) with ESMTP id u5DKkbU0012053 for <ietf@ietf.org>; Mon, 13 Jun 2016 13:46:37 -0700 (PDT) (envelope-from finlayson@live555.com)
X-Authentication-Warning: ns.live555.com: Host localhost.live555.com [127.0.0.1] claimed to be [127.0.0.1]
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Long-term IETF evolution thoughts
From: Ross Finlayson <finlayson@live555.com>
In-Reply-To: <20160613183608.GA31629@gsp.org>
Date: Mon, 13 Jun 2016 13:46:36 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <68C4A95D-2948-4336-8F6B-64BFF818AC9D@live555.com>
References: <B937F6B4-248F-42B7-BBDB-C82B914C874C@ietf.org> <eb706622-69e6-2161-29d9-27e43d241030@acm.org> <20160613183608.GA31629@gsp.org>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K7Ps_WQ4HxSXFTf9KvDsYsI4uSY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Jun 2016 20:47:03 -0000
> That's because email is STILL the very best collaboration tool available: > nothing else even comes close. > > 1. It's low-bandwidth. > 2. It can be utilized offline. > 3. It's asynchronous. > 4. It can be used with the UI (mail client) of the participant's choice, > as long as that mail client is reasonably well-behaved. > 5. It automatically builds an archive. > 6. Individual participants can build their own archives. > 7. Which means that they can also search those archives with the > mechanism of THEIR choice rather than one forced on them. > 8. Which means that (taken as an aggregate) there are numerous ways > to ensure the completeness and integrity of the archives. > 9. It scales magnificently. > 10. Privacy/security issues are minimized. > 11. Attacks/abuse/etc. against it are well-understood and easy to handle. > 12. It's extremely fault- and delay-tolerant. > 13. It's push, not pull. > 14. It's highly portable, e.g., list-rehosting and list software upgrading > or changing are all relatively painless processes. > 15. There are some very good choices for well-supported, mature, > stable, open-source software to manage it. > 16. (more which I'll omit for now) > > Moving to web-based collaboration would be a massive downgrade: it's > a truly horrible idea. Absolutely. There’s no way in hell that I’m going to move from email to an ‘improved' system that would require me to have a web browser window open (or, more accurately, multiple web browser windows open - one for each ‘forum’ that I’m at least vaguely interested in), and hope that these windows update properly (without sending my browser’s CPU usage into the stratosphere) so that I don’t miss any notifications. Although many ‘hipsters’ these days might not like email, an email address seems like a very low bar to require for participation in the IETF. Ross.
- Re: Long-term IETF evolution thoughts Rich Kulawiec
- Re: Long-term IETF evolution thoughts Michael Richardson
- Re: Long-term IETF evolution thoughts Rich Kulawiec
- Re: Long-term IETF evolution thoughts Marc Petit-Huguenin
- Re: Long-term IETF evolution thoughts Michael Richardson
- Re: Long-term IETF evolution thoughts Dave Taht
- Re: Long-term IETF evolution thoughts Randy Bush
- Re: Long-term IETF evolution thoughts Dave Taht
- Re: Long-term IETF evolution thoughts Ross Finlayson
- RE: Long-term IETF evolution thoughts Adrian Farrel
- Re: Long-term IETF evolution thoughts Jaap Akkerhuis
- Re: Long-term IETF evolution thoughts Dave Taht
- Long-term IETF evolution thoughts IETF Chair
- Re: Long-term IETF evolution thoughts Marc Petit-Huguenin
- Re: Long-term IETF evolution thoughts nalini.elkins
- Under-represented communities [Re: Long-term IETF… Brian E Carpenter
- Re: Long-term IETF evolution thoughts Melinda Shore
- Re: Under-represented communities [Re: Long-term … nalini.elkins
- Re: Long-term IETF evolution thoughts Michael Richardson
- Re: Long-term IETF evolution thoughts Jari Arkko
- Re: Long-term IETF evolution thoughts Marc Petit-Huguenin