Re: content-charset & checksums

I vote for checksum to be only defined for BASE64 (since it's the only
encoding which is allegedly bulletproof against munging), and for it to appear
as an attribute.

If it must appear in the data, it should be at the end of the data and have a
distinct syntax using a character that isn't in the BASE64 set.