IETF Logo Mail Archive

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

David Leon Gil <coruus@gmail.com> Mon, 16 March 2015 22:14 UTC

Return-Path: <coruus@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 6E1A51AC3A5 for <openpgp@ietfa.amsl.com>; Mon, 16 Mar 2015 15:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.739
X-Spam-Level:
X-Spam-Status: No, score=-1.739 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, HTML_OBFUSCATE_05_10=0.26, 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 6vHrNTJ9VjMS for <openpgp@ietfa.amsl.com>; Mon, 16 Mar 2015 15:14:16 -0700 (PDT)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com [IPv6:2607:f8b0:4002:c01::22f]) (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 91A851AC39E for <openpgp@ietf.org>; Mon, 16 Mar 2015 15:14:16 -0700 (PDT)
Received: by yhjf44 with SMTP id f44so22457091yhj.3 for <openpgp@ietf.org>; Mon, 16 Mar 2015 15:14:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cbtVFlSDVz6713JlzCUZXMhGZCgjCZhofMUkP2DHwjI=; b=JFs7wKNmH6Wo4NwCFY7pqgKhtQoA2IcGFEKqsY7LlAjR9R2yeFIOUS8abUkTaj+cN+ mBHFa8QpalUnM5cIOse6UeakEWMH7KdplJWCnmieIadnJ3iFv3k0kaRq/0q1/AG/HpxS oSZrnVad0Xs0WJrLBCKr+17TBBefh8kHL0GajJqrWE13G1X+KH4oTHOOLVcK/HlpRcyP hbxDUDDP9ESuauYRMhZ+Tto6Ilnni3xOhcLCozFLvHC6ErFvJD/VtfHKTYLSgflah/j9 CIgxsAilXXSCT4ZpxC+wRA2TMAuqV11BLTyrHFkE9PhrC4tR5lWaDbyKcrzfr4/oKXji kjVA==
MIME-Version: 1.0
X-Received: by 10.236.221.228 with SMTP id r94mr64454421yhp.127.1426544055890; Mon, 16 Mar 2015 15:14:15 -0700 (PDT)
Received: by 10.170.125.80 with HTTP; Mon, 16 Mar 2015 15:14:15 -0700 (PDT)
In-Reply-To: <87zj7hvgzp.fsf@alice.fifthhorseman.net>
References: <878uf2iehi.fsf@vigenere.g10code.de> <alpine.LFD.2.10.1503120918110.21555@bofh.nohats.ca> <87zj7hvgzp.fsf@alice.fifthhorseman.net>
Date: Mon, 16 Mar 2015 15:14:15 -0700
Message-ID: <CAA7UWsV=A+riEY0Dgy=a2+gfDMitjdtGHCzdsvt8_+Tup0s19w@mail.gmail.com>
From: David Leon Gil <coruus@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Content-Type: multipart/alternative; boundary="001a11c2cc42b53af805116f2b44"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/Fw4kL3FLqqjAzrUKEIFlcz2PgAY>
Cc: "openpgp@ietf.org" <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: Mon, 16 Mar 2015 22:14:18 -0000

On Thursday, March 12, 2015, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
wrote:

> On Thu 2015-03-12 09:50:19 -0400, Paul Wouters wrote:
> > On Thu, 12 Mar 2015, Werner Koch wrote:
> fwiw, i'd consider a re-chartered wg to cover possible revisions or
> extensions to several RFCs, not just 4880:
>
>   https://tools.ietf.org/html/rfc4880   -- OpenPGPv4
>   https://tools.ietf.org/html/rfc3156   -- PGP/MIME
>   https://tools.ietf.org/html/rfc6637   -- ECC in OpenPGP
>
> To add an item to Werner's earlier list:
>
>  * i'd like to spec out an adjustment to PGP/MIME that provides
>    signature and encryption protection for RFC 822 headers.
>

 As a note: I consider figuring out something for RFC 822 headers a very
high priority. It is particularly difficult, because many '822' headers are
mainly intended for servers. (And are important for spam control.)

So it may be necessary, in some cases, to encrypt some of the 822 headers
only to the ultimate recipient, and some of them to the server as well.

v2.23.0 | Report a Bug | By Email