<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:ben@links.org">Ben Laurie</a><br><b>Sent: </b>Monday, November 13, 2017 1:09 PM<br><b>To: </b><a href="mailto:jamesd@echeque.com">jamesd@echeque.com</a><br><b>Cc: </b><a href="mailto:cryptography@metzdowd.com">Cryptography Mailing List</a><br><b>Subject: </b>Re: [Cryptography] Is ASN.1 still the thing?</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 13 November 2017 at 03:11, James A. Donald <jamesd@echeque.com> wrote:</p><p class=MsoNormal>>> Do JSON, Yaml, or protobuff allow representing data format in ways that give</p><p class=MsoNormal>>> a unique and well defined checksum, that will not be affected by endianess</p><p class=MsoNormal>>> or compiler options?</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>>JSON is a terrible interchange format, as I've been discovering to my</p><p class=MsoNormal>>cost with objecthash: https://github.com/benlaurie/objecthash - I</p><p class=MsoNormal>>should not have used JSON as the example.</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>>Most obvious problems: different capabilities in different languages,</p><p class=MsoNormal>>can't represent ints over 2^53, no way to transmit raw bytes natively.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>FWIW, there’s BSON (http://bsonspec.org/)...</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>=====[snip]=====</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>