Re: [pkix] Identified Work Items and Discussion Summary (was: possible new pkix and/or smime work)

"John R Levine" <johnl@taugh.com> Fri, 01 April 2016 16:43 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55A4912D0CC for <pkix@ietfa.amsl.com>; Fri, 1 Apr 2016 09:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=FAv52VhN; dkim=pass (1536-bit key) header.d=taugh.com header.b=G2om66MG
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 0Wg9eQRVw0Aj for <pkix@ietfa.amsl.com>; Fri, 1 Apr 2016 09:43:33 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B6ED12D18E for <pkix@ietf.org>; Fri, 1 Apr 2016 09:43:29 -0700 (PDT)
Received: (qmail 5041 invoked from network); 1 Apr 2016 16:43:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=13b0.56fea530.k1604; bh=aK4BQ0OQ8QRx6INEL4g+wgrwXTUboiNt2vFMJJna6PI=; b=FAv52VhNk0mpGJLxbm0DYcW073PC3X3QwTgUUMi7gYgunLGP6XX3FHlDodUSE6s7oTm9U4YmZWcTAoIJ4ejVgqWXEI3I7TWrmgnaLEl0RfOlcJDLsECLXOQYHvxBzgqK7BjFlapMZgK+AWfnJxfW217EwBAINwyIAGNNqG+KNbzcwsfp4akNqqzclTEntbcnipHfb33BqBJdzgN1UIl+ZpQJOpYXL+tpITtHE0Nz3y1h+hYBcJlc+PFNJcaPGXlz
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=13b0.56fea530.k1604; bh=aK4BQ0OQ8QRx6INEL4g+wgrwXTUboiNt2vFMJJna6PI=; b=G2om66MG/3KDF7gji2pJngFfjKZAJ7c6QEX+8C2CfjwH+32+7HlqcJA7hHK7wj67rFp6CKVd/7ff1Ah4Ha9qHPnzn+tpDXwCoAFL8bdIZXzecrv7b8weOn/9Yx1l2sVFlBJz1zfaMOXcqa1DyRKOxbl0LnW8q2M02rU0vj4/BtyVo1vzytiwMwT3APlYpmuAJa8piaxWhR4ep777vhaVGqR12e1rAawguRVspVJWQMT4n9wxxShFwHjcjaWMgXXO
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 01 Apr 2016 16:43:28 -0000
Date: Fri, 01 Apr 2016 12:43:27 -0400
Message-ID: <alpine.OSX.2.11.1604011242410.58572@ary.lan>
From: John R Levine <johnl@taugh.com>
To: Tom Ritter <tom@ritter.vg>
In-Reply-To: <CA+cU71=umYrYfJfG8CQ0tf=P5FuvxW7W4JAcz+060g2VdsmAXg@mail.gmail.com>
References: <CAAFsWK1BDEFOALrcgjw9iHw5D9jZeLAp7bAurs3bqgQb0UxhrQ@mail.gmail.com> <CA+cU71=umYrYfJfG8CQ0tf=P5FuvxW7W4JAcz+060g2VdsmAXg@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/eGMw0trNJPoIl4k35Tg8FksT_J4>
Cc: PKIX <pkix@ietf.org>, IETF SMIME <smime@ietf.org>
Subject: Re: [pkix] Identified Work Items and Discussion Summary (was: possible new pkix and/or smime work)
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 16:43:35 -0000

> If people are unaware, protection of email headers (for PGP) is
> progressing at https://modernpgp.org/memoryhole/ (although it may be a
> bit stalled.)

This looks like the usual approach of wrapping the message in an outer 
message with all of the headers genericised.  Ned Freed has said this has 
severe patent problems.  I don't know the details.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.