Re: [openpgp] How to re-launch the OpenPGP WG

Wyllys Ingersoll <wyllys@gmail.com> Fri, 20 March 2015 13:46 UTC

Return-Path: <wyllys@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 77D571B2D6A for <openpgp@ietfa.amsl.com>; Fri, 20 Mar 2015 06:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 8OwqHXKZQBXX for <openpgp@ietfa.amsl.com>; Fri, 20 Mar 2015 06:46:49 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (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 AD4751B2D63 for <openpgp@ietf.org>; Fri, 20 Mar 2015 06:46:49 -0700 (PDT)
Received: by obdfc2 with SMTP id fc2so78247228obd.3 for <openpgp@ietf.org>; Fri, 20 Mar 2015 06:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=4HtWhPjl/4EfZD1pe43E8Zsmh8DK5SID6IqiJR4GaAA=; b=JKPxGJs4ESqJBk7TtLqkuFtOh4+M14qPzDEUGC5kp9ZBK5DU+/aLW7t8XaonvuzGUV 3yvOanLVzfMhKVJPypECTyi2xQlYWlPC6Ejy+rgNMgh7XOLWkmaDzbzpi3/Y+UM/5gyT B+tremaXvkjsfNg2x4m2k1N5x9JV+2yadKj3b1/xvVkAvIQKpFasm1YMYbXFq7l8t9Pr uA4vpCTs+Yyg48qQzoZirwYMvu0KQOfmA4r6yadPDv0K8GOqJomX5fFMMm2g3dLqWNZ1 tt7iLzZ5DDODJvuX6iZvrnZdjhjhEXSwsAGIJ0qa58ilu4RBAUkuGUJRxgRD2xp/GYQF ZmOA==
X-Received: by 10.202.77.198 with SMTP id a189mr24017037oib.49.1426859209156; Fri, 20 Mar 2015 06:46:49 -0700 (PDT)
MIME-Version: 1.0
References: <878uf2iehi.fsf@vigenere.g10code.de> <1426218768.22326.80.camel@scientia.net> <874mppgyez.fsf@vigenere.g10code.de> <sjm3859nhe1.fsf@securerf.ihtfp.org> <1426564752.18487.35.camel@scientia.net> <5507E916.4040307@sumptuouscapital.com> <1426719900.4249.40.camel@scientia.net> <alpine.GSO.1.10.1503191359220.3953@multics.mit.edu> <1426788650.13059.16.camel@scientia.net> <alpine.GSO.1.10.1503191843080.3953@multics.mit.edu> <CAMm+Lwgsnb64ohAXL4=zP4vpW3==6U=vC+w9TsY-CBDNV-pHOg@mail.gmail.com>
In-Reply-To: <CAMm+Lwgsnb64ohAXL4=zP4vpW3==6U=vC+w9TsY-CBDNV-pHOg@mail.gmail.com>
From: Wyllys Ingersoll <wyllys@gmail.com>
Date: Fri, 20 Mar 2015 13:46:47 +0000
Message-ID: <CAHRa8=V1987kj9_1E+TBb1HwJbrYYv9LN8HE7RFKUGTUpY4rAw@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Benjamin Kaduk <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary="001a1134fdc84e70230511b88ce7"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/WHR1tnaQu02fy5A9cg4fN4vdImU>
Cc: Christoph Anton Mitterer <calestyo@scientia.net>, IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] How to re-launch the OpenPGP WG
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: Fri, 20 Mar 2015 13:46:51 -0000

MIME is fine for PGP over email, but do keep in mind that PGP is not
strictly used in email and using MIME is not necessarily helpful and is
possibly needlessly complicated in some of the other use cases (just
encrypting personal files and data at rest, for example).

And if we are going to start talking about "PGP/MIME", then I think
revising RFC-3156 should be part of the discussion at some point. As it is
stands today, it is impossible to craft a proper "PGP/MIME" message unless
your mail client directly supports 3156.  It requires special SMTP headers
that are usually set by the mail client and over which the user has no
control (and don't get me started on that extra "version 1" MIME
section...).

-Wyllys



On Thu, Mar 19, 2015 at 7:14 PM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

> As a branding issue, I would pick the name PGP/MIME for the working group
> and make the focus decrufting legacy bits of PGP and making a MIME based
> scheme the new common denominator for framing.
>
> If there was also a clearly defined strategy for interop with S/MIME
> credentials then such a specification could be positioned as the future
> upgrade path for OpenPGP and S/MIME.
>
> Since an S/MIME credential can be turned into a fingerprint pretty easily
> and the fingerprints are what people actually use in practice to exchange
> OpenPGP mail. This is not exactly a major problem.
>
> (Yes I know that there is a PGP/MIME mode at the moment. but that isn't
> the point).
>
> Think of it as embrace and extend...
> _______________________________________________
> openpgp mailing list
> openpgp@ietf.org
> https://www.ietf.org/mailman/listinfo/openpgp
>