IETF Logo Mail Archive

Re: [apps-discuss] update to rfc5965

"Murray S. Kucherawy" <superuser@gmail.com> Sun, 07 July 2013 07:42 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7844F21F9E5C for <apps-discuss@ietfa.amsl.com>; Sun, 7 Jul 2013 00:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehIrH5XKC3ku for <apps-discuss@ietfa.amsl.com>; Sun, 7 Jul 2013 00:42:29 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A01CF21F9E58 for <apps-discuss@ietf.org>; Sun, 7 Jul 2013 00:42:29 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id q56so2932048wes.3 for <apps-discuss@ietf.org>; Sun, 07 Jul 2013 00:42:27 -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=c420x2KNjf46yLByv6dQ8JNRJIylvITZgEr7Sfr37qE=; b=gTDUa+6WCNA4wEVJxzHO6Usrif0k6VMKrH6EnBdXAf+C2WygVrIS+T+rask8goX1m2 9Mc0sHl6EpDM4wcOYG+AX4NQTaeBm1nttSeWacD9s5iCOhftas6r/RahXEONUOH4zWhN 4R9+aGJoDXkxS+6Ek72wj7jjlM4aOJMh6ZYuYWtClzNncxAboF2d3Nzw6q03ltQE277+ Y2VGgh5skVxyvIHqbgyOFW/voVq3+2aEV467nQmKZfLdOfHfzlfgZ2a5SUrT2rf5YYCB +lcAoZ8Xo5lmRIlWJgN72hw9zx1J0TuwaO3UVG8JFMUzaVTi3ugLpE98QalJT+QFgkWL mlBQ==
MIME-Version: 1.0
X-Received: by 10.180.89.231 with SMTP id br7mr27048021wib.19.1373182947365; Sun, 07 Jul 2013 00:42:27 -0700 (PDT)
Received: by 10.180.90.16 with HTTP; Sun, 7 Jul 2013 00:42:27 -0700 (PDT)
In-Reply-To: <47488958.173803.1373149894362.JavaMail.zimbra@peachymango.org>
References: <769743608.173673.1373148450418.JavaMail.zimbra@peachymango.org> <47488958.173803.1373149894362.JavaMail.zimbra@peachymango.org>
Date: Sun, 07 Jul 2013 00:42:27 -0700
Message-ID: <CAL0qLwZaPrXhnCXcMPzE6gcif6akV2iKibvXPrqHREE0hXPFrg@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Franck Martin <franck@peachymango.org>
Content-Type: multipart/alternative; boundary="e89a8f3ba255ca1af304e0e711d0"
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] update to rfc5965
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jul 2013 07:42:30 -0000

Briefly:

On Sat, Jul 6, 2013 at 3:31 PM, Franck Martin <franck@peachymango.org>wrote:

> I suggest we add the possibility to send the complete email as
> message/rcf822 email within either an encrypted zip file or within a GPG
> symmetrically encrypted file, both using the common password "infected".
>
> The MIME type should be
> message/rfc822-zip-crypt for an encrypted zip file
> message/rfc822-gpg-crypt for the gpg encrypted file
>
> gpg and zip are widely used on many systems.
>
> I'm gathering comments, and will tentatively write a draft if no major
> block is received.
>
>
Has anyone implemented this?

It strikes me that putting a specific password in a standards document is
unlikely to fly.  It might be better to include a new media type parameter
to indicate the password used to create the encrypted form.

You'd also need to register the media types in your proposal.  You might
check with the media type reviewer for advice.  I think the new hotness
would be to use "+" where you have "-".

You might also be able to reuse existing stuff like what's in RFC3156.

-MSK

v2.23.0 | Report a Bug | By Email