[147426] in cryptography@c2.net mail archive
Re: [Cryptography] encoding formats should not be committee'ized
daemon@ATHENA.MIT.EDU (Tony Arcieri)
Tue Oct 1 22:37:11 2013
X-Original-To: cryptography@metzdowd.com
In-Reply-To: <52493936.8060704@iang.org>
From: Tony Arcieri <bascule@gmail.com>
Date: Tue, 1 Oct 2013 17:56:21 -0700
To: ianG <iang@iang.org>
Cc: Crypto <cryptography@metzdowd.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
--===============8721854743914772248==
Content-Type: multipart/alternative; boundary=047d7b677afae81b0904e7b78a46
--047d7b677afae81b0904e7b78a46
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Sep 30, 2013 at 1:41 AM, ianG <iang@iang.org> wrote:
> Experience suggests that asking a standards committee to do the encoding
> format is a disaster.
>
> I just looked at my code, which does something we call Wire, and it's 700
> loc. Testing code is about a kloc I suppose. Writing reference
> implementations is a piece of cake.
>
> Why can't we just designate some big player to do it, and follow suit? Why
> argue in committee?
Well, the details are important ;)
If someone is particularly fond of arguing over certificate formats, ZeroMQ
is trying to design one. I'm also trying to design one as well! It would be
nice to consolidate efforts on an X.509 replacement, even if it's a limited
capacity one.
Here's the original email to the 0MQ list:
http://lists.zeromq.org/pipermail/zeromq-dev/2013-October/022975.html
Here's my response:
http://lists.zeromq.org/pipermail/zeromq-dev/2013-October/023009.html
--
Tony Arcieri
--047d7b677afae81b0904e7b78a46
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Mon, Sep 30, 2013 at 1:41 AM, ianG <span dir=3D"ltr">&l=
t;<a href=3D"mailto:iang@iang.org" target=3D"_blank">iang@iang.org</a>><=
/span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
Experience suggests that asking a standards committee to do the encoding fo=
rmat is a disaster.<br>
<br>
I just looked at my code, which does something we call Wire, and it's 7=
00 loc. =A0Testing code is about a kloc I suppose. =A0Writing reference imp=
lementations is a piece of cake.<br>
<br>
Why can't we just designate some big player to do it, and follow suit? =
Why argue in committee?</blockquote><div><br></div><div>Well, the details a=
re important ;)</div><div><br></div><div>If someone is particularly fond of=
arguing over certificate formats, ZeroMQ is trying to design one. I'm =
also trying to design one as well! It would be nice to consolidate efforts =
on an X.509 replacement, even if it's a limited capacity one.</div>
<div><br></div><div>Here's the original email to the 0MQ list:</div><di=
v><br></div><div><a href=3D"http://lists.zeromq.org/pipermail/zeromq-dev/20=
13-October/022975.html">http://lists.zeromq.org/pipermail/zeromq-dev/2013-O=
ctober/022975.html</a><br>
</div><div><br></div><div>Here's my response:</div><div><br></div><div>=
<a href=3D"http://lists.zeromq.org/pipermail/zeromq-dev/2013-October/023009=
.html">http://lists.zeromq.org/pipermail/zeromq-dev/2013-October/023009.htm=
l</a><br>
</div></div><div><br></div>-- <br>Tony Arcieri<br>
</div></div>
--047d7b677afae81b0904e7b78a46--
--===============8721854743914772248==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============8721854743914772248==--
