title: Why there are difference while coding CBOR in Python libraries and RIOT OS C library?
body: <p>So I have this thing</p>
  <pre><code>{'apn': 'censored', 'support_data_mode': False, 'data_usr_name': 'censored', 'data_password': 'censored'} 
  </code></pre>
  <p>When read this data from system that uses NanoCBOR i get something like this</p>
  <pre><code>b'\xbfcapnjcensoredqsupport_data_mode\xf4mdata_usr_namedcensoredmdata_passworddcensored\xff'
  </code></pre>
  <p>and I can decode it in Python 3 and get correct result. But when I try to encode it back it is like this</p>
  <pre><code>b'\xa4capnjcensoredqsupport_data_mode\xf4mdata_usr_namedcensoredmdata_passworddcensored'
  </code></pre>
  <p>and system doesn't take it back as valid message.</p>
  <p>A tried all Python libraries cbor, cbor2 flynn and flunn.</p>
  <p>Documentation is sparse and I don't know what to do to encode it in the correct format.</p>