Re: Media type for PGP message?
t.p. <daedulus@btconnect.com> Fri, 17 October 2014 08:25 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF231A9119 for <ietf@ietfa.amsl.com>; Fri, 17 Oct 2014 01:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_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 7Ns3cxsbfMNW for <ietf@ietfa.amsl.com>; Fri, 17 Oct 2014 01:25:41 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0705.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::705]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B1CA1A911A for <ietf@ietf.org>; Fri, 17 Oct 2014 01:25:40 -0700 (PDT)
Received: from pc6 (86.184.62.161) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.1049.19; Fri, 17 Oct 2014 08:25:17 +0000
Message-ID: <009401cfe9e3$93cf0620$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: Tim Bray <tbray@textuality.com>, John Levine <johnl@taugh.com>
References: <2684567.G0MAaMzsuj@kitterman-optiplex-9020m> <20141014005800.41663.qmail@ary.lan> <CAHBU6ivKTko2ToJF7WiQ4Vq7osmAvYjf74hKzxswPkdeLDHQew@mail.gmail.com> <CAHBU6itvCZfCG87Yesm8smXf4TtXE1BLx8kGq1ugDQ=+yMxqXQ@mail.gmail.com>
Subject: Re: Media type for PGP message?
Date: Fri, 17 Oct 2014 09:22:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.184.62.161]
X-ClientProxiedBy: DB4PR03CA0022.eurprd03.prod.outlook.com (25.160.39.160) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR07MB252;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Forefront-PRVS: 0367A50BB1
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(377424004)(199003)(189002)(13464003)(377454003)(51704005)(86362001)(575784001)(93916002)(23676002)(42186005)(15202345003)(116806002)(89996001)(19580395003)(47776003)(20776003)(84392001)(14496001)(19580405001)(92726001)(92566001)(97736003)(80022003)(46102003)(122386002)(31966008)(120916001)(101416001)(85852003)(99396003)(66066001)(102836001)(87976001)(76482002)(64706001)(87286001)(15975445006)(62236002)(44716002)(88136002)(21056001)(62966002)(85306004)(104166001)(50466002)(93886004)(81816999)(76176999)(81686999)(50986999)(77096002)(44736004)(61296003)(107046002)(106356001)(33646002)(4396001)(95666004)(40100003)(77156001)(50226001)(105586002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR07MB252; H:pc6; FPR:; MLV:sfv; PTR:InfoNoRecords; A:0; MX:1; LANG:en;
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PHI4IaXpAsCPuzOathF7CJcRfDw
Cc: IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Oct 2014 08:25:44 -0000
Tim I realise that the Applications Area is redundant and will soon be exterminated, but, perhaps, it just might linger on long enough to provide a home for a discussion of a new media type:-); the apps-discuss list could just do. Tom Petch ----- Original Message ----- From: "Tim Bray" <tbray@textuality.com> To: "John Levine" <johnl@taugh.com> Cc: "scott" <scott@kitterman.com>; "IETF-Discussion Discussion" <ietf@ietf.org> Sent: Thursday, October 16, 2014 9:51 PM Subject: Re: Media type for PGP message? A new version of I-D, draft-bray-pgp-message-00.txt has been successfully submitted by Tim Bray and posted to the IETF repository. Name: draft-bray-pgp-message Revision: 00 Title: The OpenPGP Message Format Document date: 2014-10-16 Group: Individual Submission Pages: 6 URL: http://www.ietf.org/internet-drafts/draft-bray-pgp-message-00.txt Status: https://datatracker.ietf.org/doc/draft-bray-pgp-message/ Htmlized: http://tools.ietf.org/html/draft-bray-pgp-message-00 “Real” HTML: https://www.tbray.org/tmp/draft-bray-pgp-message-00.html Abstract: RFC 4880 specifies the encoding for encrypted OpenPGP messages. This document registers an Internet Media Type for these messages. On Mon, Oct 13, 2014 at 6:32 PM, Tim Bray <tbray@textuality.com> wrote: > As I noted, there are many text-centric messaging channels that are in > wide use but are not in any sense email. > > Um, I’m suggesting registering a media type for a message format that is: > > - specified in a standards-track RFC (See RFC4880, sections 2.4 and 6) > - widely supported in software in a variety of programming languages > (references on request) > - currently being used in deployed apps (once again, see > https://www.youtube.com/channel/UCZYI0JHoJCILEegRJsWufXQ) > > Media types are supposed to be useful for dispatching payloads in > well-known formats to the appropriate software modules. Why is this > controversial? > > Anyhow, this discussion has revealed that there apparently isn’t a > registered media-type for this purpose, so I’ll write a draft and > we’ll have something concrete to argue about. > > > > On Mon, Oct 13, 2014 at 5:58 PM, John Levine <johnl@taugh.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> In article <2684567.G0MAaMzsuj@kitterman-optiplex-9020m> you write: >>>I went back and looked at a random sampling of the PGP encrypted mails I've >>>received over the last couple of years. 100% of them were multipart: >> >> You might want to check stuff that's PGP signed. In my experience, the >> majority is still ASCII armored, not MIME. >> >> R's, >> John
- Media type for PGP message? Tim Bray
- Re: Media type for PGP message? ned+ietf
- Re: Media type for PGP message? Måns Nilsson
- Re: Media type for PGP message? Tim Bray
- Re: Media type for PGP message? Scott Kitterman
- Re: Media type for PGP message? John Levine
- Re: Media type for PGP message? Tim Bray
- Re: Media type for PGP message? John C Klensin
- Re: Media type for PGP message? Scott Kitterman
- Re: Media type for PGP message? t.p.
- Re: Media type for PGP message? Måns Nilsson
- Re: Media type for PGP message? Alessandro Vesely
- Re: Media type for PGP message? Tim Bray
- Re: Media type for PGP message? t.p.
- Re: Media type for PGP message? Michael Richardson
- Re: Media type for PGP message? Tim Bray
- Re: Media type for PGP message? Alexey Melnikov
- Re: Media type for PGP message? Michael Richardson
- Re: Media type for PGP message? S Moonesamy