title: Encoding JSON in UTF-16 or UTF-32
body: <p>The <a href="https://www.rfc-editor.org/rfc/rfc4627#section-2.5" rel="nofollow noreferrer">JSON RFC, section 2.5</a>, says in part:</p>
  <blockquote>
  <p>To escape an extended character that is not in the Basic Multilingual
  Plane, the character is represented as a twelve-character sequence,
  encoding the UTF-16 surrogate pair.  So, for example, a string
  containing only the G clef character (U+1D11E) may be represented as
  &quot;\uD834\uDD1E&quot;.</p>
  </blockquote>
  <p>Assume I have a valid reason to encode JSON as UTF-16BE (which is allowed).  When doing so, is it still necessary to escape characters that are not in the Basic Multilingual Plane?  E.g., instead of this:</p>
  <pre><code>00 5C 00 75 00 44 00 38 00 33 00 34 00 5C 00 75 00 44 00 44 00 31 00 45
    \     u     D     8     3     4     \     u     D     D     1     E
  </code></pre>
  <p>which is the 24-byte UTF-16BE byte sequence for <code>\uD834\uDD1E</code>, is it legal to do this:</p>
  <pre><code>D8 34 DD 1E
  </code></pre>
  <p>i.e., use the 4-byte UTF-16BE values directly?</p>
  <p>Similarly, if I were to encode the same JSON string as UTF-32BE, could I simply use the code-point value directly:</p>
  <pre><code>00 01 D1 1E
  </code></pre>
  <p>?</p>