No. You don't violate 27 years of practice based on any number of tests that this WG is capable of doing, just to avoid defining two content-types.
Sent from my iPhone > On Jan 31, 2018, at 2:25 PM, James Cloos <[email protected]> wrote: > > FWIW, I tried sending myself a gzip(1)ed json file using: > > Content-Type: application/tlsrpt+json; conversions=gzip > > It worked fine. And gnus even gunzip(1)ed it for me when > I asked it to inline the attachment. > > This was sent to another system which has a .forward file > pointing to my main address. So it went through at least > two instances of virus/trojan scanning w/o issue. > > (The file in question was not a tlsrpt, but it /was/ well- > formed json, and manually compressed with gzip(1).) > > So Viktor's suggestion works fine here, at least. > > Perhaps a wider test would be in order? > > -JimC > -- > James Cloos <[email protected]> OpenPGP: 0x997A9F17ED7DAEA6 _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
