Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)

Phillip Hallam-Baker <phill@hallambaker.com> Sat, 14 June 2014 15:26 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5B761B293B for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 08:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 MZWI7w9yvzCO for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 08:26:37 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0F291A038B for <ietf@ietf.org>; Sat, 14 Jun 2014 08:26:37 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id b13so3777547wgh.26 for <ietf@ietf.org>; Sat, 14 Jun 2014 08:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PbilKTiYCKcY6JFrjoP7O9h83HQsK5pH2vmvfuMmmzA=; b=Hz/mGLBEzN7ziH5EP787zxXxX9TFXRgVY8+8Jy8Ucoys+USnF9UpxtVOqiIbsn49ca NXtDO6T7BF/pm+Hh+9SjBZ6WxEVWKQpd4sWzURxzqZxCWoIDfCnXrgVJP3ogMRFVgkew oL5bEoq91ZsjNYHi3UOC4+6DNBc3UtCgBU9PZQSIgnOthxAHSPWvsPDvtEQWrN1HOuXd K7q2j9uo6g57jmP2vlNAeLzSEJGJ24TVQFXYjjGu7d2za3y97MYjP0OmiVQM0PE+D3pj geazDQrH6D4cNP+zcAex5V10s4MJrE+7nT6spaY+3MJNvulITo8jsljs7/NXlI4BTOki Y+jA==
MIME-Version: 1.0
X-Received: by 10.180.207.9 with SMTP id ls9mr13307465wic.32.1402759596084; Sat, 14 Jun 2014 08:26:36 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Sat, 14 Jun 2014 08:26:36 -0700 (PDT)
In-Reply-To: <539C5ED6.7080708@meetinghouse.net>
References: <CAMm+LwjsgmMQu+emxcHnun_XGnzTYn23pv6rSVL3EKUWNHD7mA@mail.gmail.com> <20140611170004.5D75E1AD4D@ld9781.wdf.sap.corp> <CAMm+Lwi2Bc3Cv=tyU+aJUteSK7zopxju=ZcSCu4NrMkJzgbMoA@mail.gmail.com> <5399B704.5090007@dcrocker.net> <9DAFD7B8DAA49A1629E4CC7E@JcK-HP8200.jck.com> <CAMm+LwhakExz_wAnWy3eizvhC8Lzs1RhZWmJK+-Yp5d9zHPwOA@mail.gmail.com> <539BF66B.3020404@bbiw.net> <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com> <539C5ED6.7080708@meetinghouse.net>
Date: Sat, 14 Jun 2014 11:26:36 -0400
X-Google-Sender-Auth: Zu-itkNO9giTL_QusF1fVqNSNWk
Message-ID: <CAMm+LwhTtwfFtfXQjha95gY-tp6DQbuwudMg1ZXOBuGuJ7zirA@mail.gmail.com>
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary="001a11c3cdc06e15a404fbcd6bea"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pF5jxc55PbCu3k_2LRaer2bShks
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 14 Jun 2014 15:26:39 -0000

On Sat, Jun 14, 2014 at 10:40 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Phillip Hallam-Baker wrote:
>
>>
>> It is the mode used by the majority of mail users today. Which makes it
>> rather more than just technology from a deployment point of view.
>>
>
> That's almost certainly not true, or it's certainly highly questionable.
>
> Two words:
> 1. Outlook
> 2. Smartphones


Well it all depends on whether you measure users or uses. People who use
mail a lot are more likely to use a dedicated client.

But from a deployment point of view smartphones are and always will be
limited lifetime devices because of their mode of use. If Apple adds a new
feature today, 90% of the Apple smartphones in regular use will support it
in three years. Because even if development of phones stops, any device you
carry with you every day is going to see a lot of wear and tear.


But even taking this as a given, it seems that every time that I go to a
blog with a comments form on using my iPhone the provider is trying to push
a 'stream reader' app at me. It might be that these people will only push a
proprietary app but I think it likely that they would be interested in an
open standard if one was on offer.


You may be right of course that change is impossible, it is certainly
difficult. But it does have a better chance of achieving the desired goal
of a decent discussion mechanism that supports the desired capabilities,
access modes, etc. than sitting in the sea and bidding the DMARC tide turn.