5273: Mail Text #211
Description
@vdukhovni PTAL
Collecting some comments on an already merged PR:
45711d5#r169673166
45711d5#r169663242
fc32b30#r169674615
We're interpreting some tea leaves here since neither Joe nor I was one of the original authors:
We believe this section was trying to tell implementers to make messages conform to what 1) should have been in RFC 2986 but ended up in in s2.2 of RFC 5967 (application/pkcs10); 2) is in s3.5.2 of RFC 8551 (application/pkcs7-mime); — and 3) not multipart. I am hoping that if we reference massage in some references to RFCs 5967 and 8551 that would make it clearer?
On your other points:
- refer to correct parameter names: in light of above, we will attempt to clean up some of the language to make sure we refer to the correct parameters.
- file name requirement: pretty sure it was saying that you had to include some kind of value, i.e., you had to include the field and make sure it's not an empty string.
- As far as non-ASCII character support - you really got me!! Should this have been specified in the media type definitions? I'd personally lean toward prohibiting them.
We'll work on a PR.