RE: rfc2231 implementations?
Yuri Inglikov <[email protected]>
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <E1D42DFE30883B488A5BEFC1801FA2DC2AA27CCA65@DF-GRTDANE-MSG.exchange.corp.microsoft.com> |
Does anybody have insight why RFC2047 explicitly prohibits encoding parameter values and quoted strings? I am looking through archives but seems cannot find appropriate discussion. At some point using encoded words inside quoted strings was removed from the initial proposal and there should have been a good reason which I don't immediately see...
Ultimately I am curious why, instead of extending RFC2047 to parameters, we ended up with RFC2231?
+ An 'encoded-word' MUST NOT appear within a 'quoted-string'.
+ An 'encoded-word' MUST NOT be used in parameter of a MIME
Content-Type or Content-Disposition field, or in any structured
field body except within a 'comment' or 'phrase'.
--
Yuri Inglikov