[147355] in cryptography@c2.net mail archive

home help back first fref pref prev next nref lref last post

Re: [Cryptography] encoding formats should not be committee'ized

daemon@ATHENA.MIT.EDU (Salz, Rich)
Mon Sep 30 18:35:17 2013

X-Original-To: cryptography@metzdowd.com
From: "Salz, Rich" <rsalz@akamai.com>
To: ianG <iang@iang.org>, "cryptography@metzdowd.com"
	<cryptography@metzdowd.com>
Date: Mon, 30 Sep 2013 14:22:29 -0400
In-Reply-To: <52493936.8060704@iang.org>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com

> Experience suggests that asking a standards committee to do the encoding format is a disaster.

That's over-stating it.  Sub-optimal, perhaps.

> Why can't we just designate some big player to do it, and follow suit?

Okay that data encoding scheme from Google protobufs or Facebook thrift.  Done.

	/r$

--  
Principal Security Engineer
Akamai Technology
Cambridge, MA
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography

home help back first fref pref prev next nref lref last post