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

Miles Fidelman <mfidelman@meetinghouse.net> Sat, 14 June 2014 14:40 UTC

Return-Path: <mfidelman@meetinghouse.net>
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 4C6E61B2914 for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-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 hXIRYO7iTAQJ for <ietf@ietfa.amsl.com>; Sat, 14 Jun 2014 07:40:33 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 608E51B2911 for <ietf@ietf.org>; Sat, 14 Jun 2014 07:40:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 72DD0CC082 for <ietf@ietf.org>; Sat, 14 Jun 2014 10:40:32 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KFun6M-txNpR for <ietf@ietf.org>; Sat, 14 Jun 2014 10:40:23 -0400 (EDT)
Received: from new-host-3.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A91E2CC07F for <ietf@ietf.org>; Sat, 14 Jun 2014 10:40:23 -0400 (EDT)
Message-ID: <539C5ED6.7080708@meetinghouse.net>
Date: Sat, 14 Jun 2014 10:40:22 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
MIME-Version: 1.0
CC: IETF <ietf@ietf.org>
Subject: Re: Webmail is implementation, not Internet architecture (was Re: Change the mailing list protocol, not DMARC.)
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>
In-Reply-To: <CAMm+Lwjr8tjR1-yaJdtG8GhNQ7+G5g5xCUDcNSSA6Qkd4JzW5A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TE-2fhx8_5G_lYxB9IV8HAOQ4D0
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 14:40:35 -0000

Phillip Hallam-Baker wrote:
>
> On Sat, Jun 14, 2014 at 3:14 AM, Dave Crocker <dcrocker@bbiw.net 
> <mailto:dcrocker@bbiw.net>> wrote:
>
>     On 6/12/2014 6:33 PM, Phillip Hallam-Baker wrote:
>     > On Thu, Jun 12, 2014 at 10:50 AM, John C Klensin
>     <john-ietf@jck.com <mailto:john-ietf@jck.com>
>     ...
>     >     (2) One of those changes --support for remote body parts-- was
>     >     incorporated into MIME in its very first version and contains
>     >     most of the mechanism needed to support what I understand PHB is
>     >     recommending for PUSH-PULL-PULL.  It has been implemented in
>     >     several places but has gotten very little traction in the mail
>     >     sending and receiving community.  IMO, it ought to be incumbent
>     >     on anyone proposing a different "get notification, then retrieve
>     >     mail from server" model explain why their ideas will be more
>     >     successful than that 20-odd-year-old MIME mechanism.
>     >
>     > In a word - WebMail.
>
>     This is a classic confusion between software implementation and
>     operation, vesus networking architecture.
>
>     Webmail is nothing more than a particular style of user interface,
>     integrated into the operations of a particular service. 
>
>
> 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


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra