Re: email standards

George Michaelson <ggm@algebras.org> Tue, 23 September 2014 23:20 UTC

Return-Path: <ggm@algebras.org>
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 64D101A88F1 for <ietf@ietfa.amsl.com>; Tue, 23 Sep 2014 16:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 wLG6ztfUQ7C9 for <ietf@ietfa.amsl.com>; Tue, 23 Sep 2014 16:20:37 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A89E1A88DA for <ietf@ietf.org>; Tue, 23 Sep 2014 16:20:34 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id r10so7405172pdi.40 for <ietf@ietf.org>; Tue, 23 Sep 2014 16:20:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Cx5Z9eWiXC0sXXnF8/Aik6ubYNrPBsnSA1WWSAs+9hc=; b=AntSzzgM829LZGU+PwjAq1Ye5GPALQVgh4z+APQethGr4VfGeyBk6Gt8zpZOQcJtLe HL8y+Zr7ziMbNL1dfPk/357bCU0YNsDe3mOohnYuD4QHxOZi1A6dtc8MtwyU2Hv7KMx1 m0oLO4bpGnwQXOz5JjB3FP2pJk2BOqtkY00bt2vyy63i2BO8K9rO58xvME0nMpPN++FR NtfBJm4lOqouLCJt6TP8TKF4xbDMX6aA5JqwCgbxCPqn+iDQbGZ82AETNl9uHUCHmfqH pJXkZude3gHwQqvUF9+3bf4nQg78jyCLPkFLMuh2k1lthIl2bTmwQh91qtrAOIhJmtij wFiQ==
X-Gm-Message-State: ALoCoQmly37mgXiBG1cpbM1mVuhzJWwTst/X6AKHCXqnHTrhd+2VWxEXHOjVRNPoWUFy6jZCbt/g
MIME-Version: 1.0
X-Received: by 10.68.164.164 with SMTP id yr4mr3634208pbb.57.1411514434085; Tue, 23 Sep 2014 16:20:34 -0700 (PDT)
Received: by 10.70.38.141 with HTTP; Tue, 23 Sep 2014 16:20:34 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:cd23:eedb:99de:6e2f]
In-Reply-To: <CAMm+Lwg_+CXGcHmYG_N4swwKb6jOdU6G75kr6FyeU9J2rvNepw@mail.gmail.com>
References: <E6D4B18F-9533-4EE1-A794-526094893D3C@ietf.org> <CAMm+Lwi8D0c_iWSbosXFrGsN1wtcmwu3oRc7FoQmwypk7Mi2ZA@mail.gmail.com> <2A9E2BF1C15CB41544C46E06@JcK-HP8200.jck.com> <p06240607d0476c96a946@99.111.97.136> <CAMm+LwjxOiFsWcCZoGcaqaF3fv6XBOK8LhQdzWJsigYvQQ4-kg@mail.gmail.com> <5421D7A2.8030309@dcrocker.net> <CAMm+Lwg_+CXGcHmYG_N4swwKb6jOdU6G75kr6FyeU9J2rvNepw@mail.gmail.com>
Date: Wed, 24 Sep 2014 09:20:34 +1000
Message-ID: <CAKr6gn1da3xNVoUEZo5gfdu=fV5UsNE+5vpWO8x2RQnEcXkqMA@mail.gmail.com>
Subject: Re: email standards
From: George Michaelson <ggm@algebras.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary="047d7b10c8b77080080503c3d06d"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/IV8V3kF5wPA8U_-ZVAvapGYfXyE
Cc: Dave Crocker <dcrocker@bbiw.net>, 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: Tue, 23 Sep 2014 23:20:48 -0000

where is CMS multipart in all this?

On Wed, Sep 24, 2014 at 7:56 AM, Phillip Hallam-Baker <phill@hallambaker.com
> wrote:

> On Tue, Sep 23, 2014 at 4:27 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> > On 9/23/2014 1:08 PM, Phillip Hallam-Baker wrote:
> >> I meant two secure email standards. Empirically we have two right now,
> >> S/MIME and PGP.
> >>
> >> Since I was talking about security, I thought it was obvious from the
> context.
> >
> >
> > It wasn't.
> >
> > And to be thorough, you also forgot PEM...
>
> No, I didn't because PEM (and MOSS) came first. The original point was
> that we might have done better with a facilitator in the room with
> both groups rather than both camps removing themselves to different
> rooms and throwing rocks at each other in the hallways.
>
> PEM did do one important thing and that is it acknowledged it had failed.
>
>
> > Anyhow, sometimes we need to let competitive efforts develop and then
> > let the market choose among them.  Artificially stifling serious
> > constituenies from pursuing credible alternatives is often poor
> > engineering and worse politics.
>
> Again the point was that we might have tried other means to resolve
> the fracture rather than give up without trying.
>
>
>
> > In this case, there really was significant effort to get some amount of
> > collaboration between the two groups -- the related MIME multipart
> > constructs were designed to allow some co-habitation -- but it didn't
> > get any traction.  (One of the groups was particularly political in how
> > it managed its activities, but neither group was all that flexible.)
> >
> >
> > FWIW, it's unlikely that the competition in this case has had anything
> > to do with the poor uptake of either mechanism.
>
> The two groups think they are Harry Potter and Lord Voldemort, that
> neither can live while the other survives.
>
> In practice the continued standards deadlock is allowing both camps to
> put off accepting the fact that they have not succeeded. They are both
> clinging to existence in the mistaken belief that they will take off
> as soon as the other is out of the picture.
>
> PGP has a monopoly on mindshare, S/MIME has a monopoly on deployment.
>
>
> Its like Betamax vs VHS. If we are going to get endymail deployed we
> have to get them to move to BluRay.
>
>