[147479] 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 (Peter Gutmann)
Thu Oct 3 09:47:25 2013

X-Original-To: cryptography@metzdowd.com
Date: Thu, 03 Oct 2013 20:49:05 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: cryptography@metzdowd.com, leichter@lrw.com
In-Reply-To: <89A8C64E-F328-4061-889A-18DE9B3E63B1@lrw.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com

Jerry Leichter <leichter@lrw.com> writes:

>My favorite more recent example of the pitfalls is TL1, a language and
>protocol used to managed high-end telecom equipment.  TL1 has a completely
>rigorous syntax definition, but is supposed to be readable.

For those not familiar with TL1, "supposed to be readable" here means "encoded
in ASCII rather than binary".  It's about as readable as EDIFACT and HL7.

Peter.
_______________________________________________
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