Re: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 01 July 2016 18:28 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C91F12D5A2 for <openpgp@ietfa.amsl.com>; Fri, 1 Jul 2016 11:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 D4XypsP3e0vY for <openpgp@ietfa.amsl.com>; Fri, 1 Jul 2016 11:28:01 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 3FC3712B078 for <openpgp@ietf.org>; Fri, 1 Jul 2016 11:28:01 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id c34so61840338qte.0 for <openpgp@ietf.org>; Fri, 01 Jul 2016 11:28:01 -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:from:date:message-id :subject:to:cc; bh=25S7ta4r6kAAfDspxxxVmI9GizJ+WLlDge/tO7pO308=; b=LM4NaMVHYNjX472bLHbM8JQ3cjGIJ/u29wItB9qkKTBHkfpEMnMfYS18nJ7qOsevH/ wgV2yvm2K29qjNzSgdqEgDeNA5bKsZ53vkRlGB+8MIqoWHpB/tBP20augTvm9gPWEvD2 okp1a+RGbcVQtQVsXL62x1F8LbKXjg5TO6PQ/HRo3q5aYGQxnmNmC2gfA3g6Ef0gkdKP iVX12bNDhotigUVM2yawScX4CvEXmy0z+cXI6LY4ShN6si+dlO1tJqTbKAjQLaqSwl/m OS8/HVlWLbEz6RV1PA6mZKHOj3dxOEdUZJOvBUEjvc/P32CU1kb6JjCcNeodSViHqcDe FcNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=25S7ta4r6kAAfDspxxxVmI9GizJ+WLlDge/tO7pO308=; b=Yp05Xq4t3QmYxJlg5TmNXkoxj23Rdyy/d76Eehp7hGhASCjwZZYMNzeb4MMo29OWO6 LbmksY0H9wQffBY9jomGftnLhEDuTEME9ZbY7ejoeCaM8izM9kBov9YmFq78T+Ox6/p9 CymmNeKma2WTHLqNdj2KXn2KnwiCK/64pcZIzQCoTaJBddikA9qBRGXGjc8kgiCuv7WI 9jhgpagXpSLWKxKi2j+zOSItw2IRUVlTzdXVWISyFc5NXy/2R5D46lQTd+R+nus99iSF OSDbPeoGudRM31VsExZmdArN6FI1RWwomfmXwlschubzzwEWbRu7ze3aHgS2YeYr3mCq 7K3Q==
X-Gm-Message-State: ALyK8tKD0/cXaScHQmwj5ByiW3Cv/5gp55b7CfUOHbFA4p+1uaZQGzOG4aKiy8zOc1GCOdkXTOX5TeQ1Vh8M7Q==
X-Received: by 10.237.53.233 with SMTP id d38mr33118545qte.104.1467397680375; Fri, 01 Jul 2016 11:28:00 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.55.16.106 with HTTP; Fri, 1 Jul 2016 11:27:59 -0700 (PDT)
In-Reply-To: <CAMm+LwjGZeZTpUjOp_McDrp6cMQQn=Sy6Wp+Ti5M--V4vnMDqw@mail.gmail.com>
References: <20160701153304.332d2c95@pc1> <sjmwpl5qtqy.fsf@securerf.ihtfp.org> <CAMm+LwjGZeZTpUjOp_McDrp6cMQQn=Sy6Wp+Ti5M--V4vnMDqw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 01 Jul 2016 14:27:59 -0400
X-Google-Sender-Auth: cIB7VhO-0UoZbSZucRd7HLwtdHI
Message-ID: <CAMm+LwgX-U=wwdhdph41-pOGnY5Lv4fFWbv+tdgxqMDuKdfxfA@mail.gmail.com>
To: Derek Atkins <derek@ihtfp.com>
Content-Type: multipart/alternative; boundary="001a114024e67bae160536972512"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/ROoI64WJliWa3r0ugMkJLQEbPmE>
Cc: IETF OpenPGP <openpgp@ietf.org>, Hanno Böck <hanno@hboeck.de>
Subject: Re: [openpgp] Can the OpenPGP vs. S/MIME situation be fixed?
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 01 Jul 2016 18:28:03 -0000

Just a note to add that the way to get OpenPGP to work with S/MIME would be
for experts to get together and write drafts proposing a way to do it. If
we have drafts that have support from experts in both camps then getting
them through IETF process should not be a roadblock.

We don't need to charter or recharter before starting that type of work. We
only need to charter before we adopt it somewhere as a working group item.
The precondition for that being 'do you have a plan'.