IETF Logo Mail Archive

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

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 19 March 2015 23:14 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 85CB01A0013 for <openpgp@ietfa.amsl.com>; Thu, 19 Mar 2015 16:14:04 -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 UwyQcq1r1y0M for <openpgp@ietfa.amsl.com>; Thu, 19 Mar 2015 16:14:03 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::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 589571A000A for <openpgp@ietf.org>; Thu, 19 Mar 2015 16:14:03 -0700 (PDT)
Received: by ladw1 with SMTP id w1so74523310lad.0 for <openpgp@ietf.org>; Thu, 19 Mar 2015 16:14: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:date:message-id:subject :from:to:cc:content-type; bh=5+vD93b14XGmiQ7vZA1bMBPCUDxe1sPXo4bXEHOB+kY=; b=nk3XBttfA9dEuGE8XT+phqifTt+QuLKV8tK13KzyDV8MdAZ1hiGees8/0GXzEaH7fh 7jqJhImBncXTRvk/jOB4pETH770weEP7mgymRnCKM8uQsDlkjVL/MDYh1irAEi8BwHsd SB7KAVFROrC/5WG2zlJA6kPOMRu66Utds/km3xe/UmY/f59lxW+SF+lhJFWKmyFGtC+a C/rdXDJiiBzOiAePebt134KxYx9fOf5CJrOK/UTS3PwnbfxtOVu3FAZA38PG681DwoUZ jxCEAGs3tu8faNJVKR/IhwrgNjXzcdAW/mxrDHqMw0jVONTPyODaOXS4grzk0aa0Z9Dw sQNw==
MIME-Version: 1.0
X-Received: by 10.112.133.2 with SMTP id oy2mr18919707lbb.124.1426806841801; Thu, 19 Mar 2015 16:14:01 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.45.203 with HTTP; Thu, 19 Mar 2015 16:14:01 -0700 (PDT)
In-Reply-To: <alpine.GSO.1.10.1503191843080.3953@multics.mit.edu>
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>
Date: Thu, 19 Mar 2015 19:14:01 -0400
X-Google-Sender-Auth: NAK_mV3j-zW45GNOg05MEvrqm_Q
Message-ID: <CAMm+Lwgsnb64ohAXL4=zP4vpW3==6U=vC+w9TsY-CBDNV-pHOg@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary="047d7b3a8c9cf7ff900511ac5a9c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/VhRFofllIFqC-hNRqAhYy1uE6E0>
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: Thu, 19 Mar 2015 23:14:04 -0000

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...

v2.23.0 | Report a Bug | By Email