[Top][All Lists]

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


From: Davis Herring
Date: Thu, 10 May 2012 09:21:22 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110717 Lanikai/3.1.11

> 4.1.4.  Unrecognized Subtypes
>    Unrecognized subtypes of "text" should be treated as subtype "plain"
>    as long as the MIME implementation knows how to handle the charset.
>    Unrecognized subtypes which also specify an unrecognized charset
>    should be treated as "application/octet-stream". -- RFC 2046
> The word "should" in an RFC has a precise (and to many, surprisingly
> strong) meaning:
> 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
>    may exist valid reasons in particular circumstances to ignore a
>    particular item, but the full implications must be understood and
>    carefully weighed before choosing a different course. -- RFC 2119

As RFC 2046 doesn't contain the "are to be interpreted as described in
RFC 2119." verbiage (which is not surprising, since it's older!), it
doesn't seem so plain to me that the (lowercase) "should" in 2046/4.1.4
should (hah!) be interpreted so strongly.


This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during

reply via email to

[Prev in Thread] Current Thread [Next in Thread]