1995-09-04 - Re: ASN.1 and Kerberos version 5

Header Data

From: ethridge@Onramp.NET (Allen B. Ethridge)
To: cypherpunks@toad.com
Message Hash: 40ddeb3f31e37f6b311a28d92203071e3186ea4bf5bc15f7264602e4dc1849f3
Message ID: <v02130500ac6ff390c7a1@[199.1.11.217]>
Reply To: N/A
UTC Datetime: 1995-09-04 05:12:51 UTC
Raw Date: Sun, 3 Sep 95 22:12:51 PDT

Raw message

From: ethridge@Onramp.NET (Allen B. Ethridge)
Date: Sun, 3 Sep 95 22:12:51 PDT
To: cypherpunks@toad.com
Subject: Re: ASN.1 and Kerberos version 5
Message-ID: <v02130500ac6ff390c7a1@[199.1.11.217]>
MIME-Version: 1.0
Content-Type: text/plain


>I don't think that the concept of ASN.1 is as bad as Jeff makes out. If it
>worked
>then ASN.1 would be very very usefull. But is just plain don't.
>
>ASN.1 is worse than useless, it means that a very good idea is rendered
>unusable
>because of a baddly botched implementation.
>

I'm not familiar with ASN.1 except for the occasional short piece in various
books.  But i was under the impression that it was similar to the language used
to define TCAP and ROSE standards.  These standards are reasonably well defined.
I've gotten to the point where i get annoyed when working with protocols that
treat everything like abitrarily organized bits and bytes (like NA Cellular
protocols and PGP).

So, would use of the language used to define TCAP and ROSE applications be
a possibility?  I've occasionally thought about developing such a protocol
for PGP.

        allen







Thread