[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [openpgp] Another candidate pgp wg item: Media type



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 04/14/2015 10:56 PM, Werner Koch wrote:
> On Tue, 14 Apr 2015 22:43, dominik@xxxxxxxxxxxxxxxxxxxx said:
> 
>> Where is it specified that "application/pgp-encrypted" can also 
>> directly contain the data? Please point me to the line in the
>> RFC.
> 
> You are right, it is not formally specified:
> 
> MIME media type name: application MIME subtype name: pgp-encrypted 
> Required parameters: none Optional parameters: none
> 
> Encoding considerations:
> 
> Currently this media type always consists of a single 7bit text 
> string.
> 
> but I see no strong reason not to use it for amored data unless it
> is enclosed by multipart/encrypted.
> 
> We could update rfc-3156 to formally define an OpenPGP container
> or improve the defintion of this media type.

Yes we should do that. Again: We need a MIME type for _non_-armored
data, so if we would use "pgp-encrypted" we would definitely not
follow RFC3156.

I am also not convinced that it is a good idea to use "pgp-encrypted"
for anything other than the version, it would require a parser to
differentiate "pgp-encrypted" with version-only and "pgp-encrypted"
with data.

So I would propose (following Tim Bray): pgp-message as a new MIME
type for data-only.

Regards
Dominik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJVLYoHAAoJEHGMBwEAASKCwiMIAJFqyK5sxXlnfnHO9JAsaZe7
lo4megd3mRVijyT07D9UUOZYjnZZ9RGY3is/dt4dT9rmm/Mgy+Zz6wpth3RMg58v
Dsb+fp2SMj1ESF4zCkrwjgtN4NC9F5m4UtLnq9XKvIfEDDrQ+wzUhynOfoRxJAri
s5v3qem21j9QQumX5aHqR+byOJZZMSXTrYUKmU3P4VxKAlG+v2FOQFqKL30EwpUq
vNz33wocWSja7EJcoJrokW5MjxR981Y/N6lDui0CxHOFJbz/l1HlLjKwOswUn30X
pU56gECsco3hBLpr/CnUsjJBlss/lesHo1MaUrPydtUsLjq4zRzPd+WWuwTgtKs=
=0ta+
-----END PGP SIGNATURE-----

_______________________________________________
openpgp mailing list
openpgp@xxxxxxxx
https://www.ietf.org/mailman/listinfo/openpgp