title: JSON Specification and usage of BOM/charset-encoding
body: <p>I've been reading up on the <a href="https://www.rfc-editor.org/rfc/rfc4627" rel="nofollow noreferrer">RFC-4627</a> specification, and I've come to interpretation:</p>
  <p>When advertising a payload as <code>application/json</code> mime-type,</p>
  <ol>
  <li>there <strong>MUST</strong> be no <code>BOM</code>s at the beginning of properly encoded JSON streams (based on section &quot;3. Encoding&quot;), and</li>
  <li>no media parameters are supported, thus a mime-type header of <code>application/json; charset=utf-8</code> does <strong>not</strong> conform to <a href="https://www.rfc-editor.org/rfc/rfc4627" rel="nofollow noreferrer">RFC-4627</a> (based on section &quot;6. IANA Considerations&quot;).</li>
  </ol>
  <p>Are these correct deductions? Will I run into problem when implementing web-services or web-clients which adhere to this interpretations? Should I file bugs against web browsers which violate the the two properties above?</p>