Computer Old Farts Forum
 help / color / mirror / Atom feed
From: cym224 at gmail.com (Nemo Nusquam)
Subject: [COFF] Joys of ASN.1 [Was: Re: tangential unix question: whatever happened to NeWS?]
Date: Sat, 30 Jan 2021 21:47:26 -0500
Message-ID: <60161A3E.9040702@gmail.com> (raw)
In-Reply-To: <CAD2gp_T95Bt6VAF8M=Q4uc4mwgp1jzjqa6dOh2JKiwiQbpR+HQ@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]

Migration to COFF, methinks

On 30/01/2021 18:20, John Cowan wrote:
> Those were just examples.  The hard part is parsing schemas, 
> especially if you're writing in C and don't know about yacc and lex.  
> That code tends to be horribly buggy.
True but tools such as the commercial ASN.1 -> C translators are fairly 
good and even asn1c has come a long way in the past few decades.

N.

>
> But unless you need to support PER (which outright requires the 
> schema) or unless you are trying to map ASN.1 compound objects to C 
> structs or the equivalent, you can just process the whole thing in the 
> same way you would JSON, except that it's binary and there are more 
> types.  Easy-peasy, especially in a dynamically typed language.
>
> Once there was a person on the xml-dev mailing list who kept repeating 
> himself, insisting on the superiority of ASN.1 to XML.  Finally I told 
> him privately that his emails could be encoded in PER by using 0x01 to 
> represent him (as the value of the author field) and allowing the 
> recipients to reconstruct the message from that!  He took it in good part.
>
>
>
> John Cowan http://vrici.lojban.org/~cowan 
> <http://vrici.lojban.org/%7Ecowan> cowan at ccil.org <mailto:cowan at ccil.org>
> Don't be so humble.  You're not that great.
>   --Golda Meir
>
>
> On Fri, Jan 29, 2021 at 10:52 PM Richard Salz <rich.salz at gmail.com 
> <mailto:rich.salz at gmail.com>> wrote:
>
>     PER is not the reason for the hatred of ASN.1, it's more that the
>     specs were created by a pay-to-play organization that fought
>     against TCP/IP, the specs were not freely available for long
>     years, BER was too flexible, and the DER rules were almost too
>     hard to get right.  Just a terse summary because this is probably
>     off-topic for TUHS.
>



           reply	other threads:[~2021-01-31  2:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAD2gp_T95Bt6VAF8M=Q4uc4mwgp1jzjqa6dOh2JKiwiQbpR+HQ@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60161A3E.9040702@gmail.com \
    --to= \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Computer Old Farts Forum

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.vuxu.org/coff

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 coff coff/ https://inbox.vuxu.org/coff \
		coff@minnie.tuhs.org
	public-inbox-index coff

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.coff


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git