Re: [openpgp] "OpenPGP Simple"

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 18 March 2015 23:33 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2FEF1A913E for <openpgp@ietfa.amsl.com>; Wed, 18 Mar 2015 16:33:01 -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 Nv64hTnsnoJm for <openpgp@ietfa.amsl.com>; Wed, 18 Mar 2015 16:33:00 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E30811A913F for <openpgp@ietf.org>; Wed, 18 Mar 2015 16:32:59 -0700 (PDT)
Received: by lbnq5 with SMTP id q5so13015820lbn.0 for <openpgp@ietf.org>; Wed, 18 Mar 2015 16:32:58 -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=i0MsLZnykaj9u95ZbYKoRwcBI3MUEPH8bvTLtBdQAHg=; b=BNyLkfBLIpsuyaRCy4hv9ffRPgVXFayhzrv20INEqPi/Go0R158QtgttK+1u6Jo2dF bc6mdN1qe4Z4j5uc+IK23PtcNsWKyi3i8km8An3te4pPuDHr9lVYAjEENoZIPOSixod4 Q4DJ24GIh7RChCTrsrAxYATc9URN8OsZUcl/vQqFVDeXvJ82IwTIOmm0WI5po2yUl/At Wl5wnU7Kh4sA4cR4+VfKnT6xSO7GuQuxXbdZrYh73YjysgsN3SFl2y3tjAVYzF0UwhiM RVAUgwhDAH/3/Cu7PRYxAdabhAKO4evyaf2DcTkqepZ61kS6tqzSJ6x5AnXpSl2i3AtB Fz7Q==
MIME-Version: 1.0
X-Received: by 10.152.120.8 with SMTP id ky8mr64017590lab.118.1426721578429; Wed, 18 Mar 2015 16:32:58 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.45.203 with HTTP; Wed, 18 Mar 2015 16:32:58 -0700 (PDT)
In-Reply-To: <1426719109.4249.28.camel@scientia.net>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB3823@uxcn10-5.UoA.auckland.ac.nz> <088CD5E6-CDB9-44E3-8762-DA51E3D7A294@jabberwocky.com> <AC983DBE-79DA-4106-A901-98478EC8BC29@gmail.com> <1426719109.4249.28.camel@scientia.net>
Date: Wed, 18 Mar 2015 19:32:58 -0400
X-Google-Sender-Auth: emQTTB3WUmMC5OWC1_H8FMrOZTw
Message-ID: <CAMm+LwiFmOL-5VKTs0K8wnH7V=YMa1H_kcgwqe3yBWkj+KkgfQ@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Content-Type: multipart/alternative; boundary="089e0122aef8e035520511988006"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/vqH9dXHHOvopQAD7y1bS6Je2YbI>
Cc: IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] "OpenPGP Simple"
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2015 23:33:01 -0000

On Wed, Mar 18, 2015 at 6:51 PM, Christoph Anton Mitterer <
calestyo@scientia.net> wrote:

> On Tue, 2015-03-17 at 10:30 -0400, Phill wrote:
> > Do not build OpenPGP around assumptions based on SMTP continuing
> > forever.
> +1, especially since I there are still many people here mentioning
> mail/SMTP and their restrictions/issues/problems quite often.
>
> A future OpenPGP (core) standard should try to avoid solving the
> issues/limitations of any other standard/protocols.
>
>
> That being said, I also don't like the idea of mail header
> signing/encryption.
> It's simply not OpenPGP's task and one should rather create an amendment
> for the mail standards or MIME which describes how an OpenPGP
> signed/encrypted headers would be embedded in an mail.
>

I think that it is now widely agreed that if SMTP was to be revised, it
would be separated into two layers with the message routing headers in one
section and the content meta-data in another.

Subject, To, From, Content-Type, etc. are all content headers. They have
nothing to do with SMTP. They are only used by the MUA.

As a general rule, if a fix works for S/MIME and OpenPGP, then we can
probably be fairly confident it will work for SMTPvNext as well.