From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8133 invoked from network); 30 Jan 2021 23:21:25 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 30 Jan 2021 23:21:25 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 06D749C7C5; Sun, 31 Jan 2021 09:21:24 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 78D6B9C653; Sun, 31 Jan 2021 09:21:08 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ccil-org.20150623.gappssmtp.com header.i=@ccil-org.20150623.gappssmtp.com header.b="LDdyrkCU"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 874C79C653; Sun, 31 Jan 2021 09:21:07 +1000 (AEST) Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) by minnie.tuhs.org (Postfix) with ESMTPS id 6C9BB9C63D for ; Sun, 31 Jan 2021 09:21:06 +1000 (AEST) Received: by mail-qt1-f180.google.com with SMTP id v3so9603467qtw.4 for ; Sat, 30 Jan 2021 15:21:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PvMdGvjJdK2RDB4kJJv3rNuJuthuX/eAPxy3iWDnKh4=; b=LDdyrkCUG7ibOF/cyDz+mGg7t03++Gsk/x0K2fbx31L2rqL7/eRObqGHHEirpcIMox r8b/8NBxSWsAoJ0KsS9zXRCc53z6ADJ67LAQe6fbIrgWp/GMTfKLRFiY5ZAnZJCCd3AL P5btx1J1AxtJnChlgAAf/kI4aVrHBTgR4j4K4ovUaXht+37xkFpnRPDq1OgfP4obN6dU 8JB6dwuB/xGlTtZFmQu9GI64Gef+DLBQ+svxtJP+ofwhJynAIRClLaGiTmZMzmKXlrUA iASGpC1VOJwPoYRQ0qQd6GfiUFCkMxyl0ymsmBT14J+G9n6DkYDKdynqLe08F09E+gvO e1/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PvMdGvjJdK2RDB4kJJv3rNuJuthuX/eAPxy3iWDnKh4=; b=hgKmkJR/Uc8JDj8kdfTZTg+EAn1HzCiIa548bxWiw9gf2GqTBB25mRFxNTxHsVOuny 8Xp32Hdld/GRZMU1s/M0FXtSnIkS6AQyemun0BwzBLd0k/iF53pXHWYxm6ZQwe7EV7UJ A+cfNFN5ZPGHJUuodvqhBo+NX4pLS/cJEUtGQlzlpphHb2ELaQUkjrARNbw+NQUtXX4Z GoYjIgDNLWYn3kmXp48Mt7TvqiDfBBHEDusTDkdngoZf3XrjGLnnLL0vqPdDdl5dxB+X 9DzurVaKrgQb9GAUSASHUoOxOXEobX23oKqwBegatkwHJQOp0v4bWH6+Pwx/becbkUg/ tKBA== X-Gm-Message-State: AOAM5317AsFlCXPkpPGEttWxsjxnpZ3sWXHXdPL/x6+J0+uB4dmcU5Eq sVnGMU21xvPqvLYWJ1JE2n+lImqUzv59JbZekaO7USfYWylJkHIV X-Google-Smtp-Source: ABdhPJxhx0HD61D/xzxgx+DSpCKRORVQ6D+kSKXXFVaNmahr/f8KJruoDA0OyD1+JLgwe2R25JgN8xm+G0bS/wGwh0E= X-Received: by 2002:aed:20a8:: with SMTP id 37mr9926066qtb.362.1612048865561; Sat, 30 Jan 2021 15:21:05 -0800 (PST) MIME-Version: 1.0 References: <20210124183653.GD21030@mcvoy.com> <202101242045.10OKjDvA964774@darkstar.fourwinds.com> <20210124211100.GI21030@mcvoy.com> <202101242114.10OLEYGk966708@darkstar.fourwinds.com> <20210124212525.GJ21030@mcvoy.com> <202101242333.10ONXjcI974038@darkstar.fourwinds.com> <202101250021.10P0L3Z2976588@darkstar.fourwinds.com> <6557f782-ecb1-6476-1eda-e23f30f9bbea@bitsavers.org> In-Reply-To: From: John Cowan Date: Sat, 30 Jan 2021 18:20:53 -0500 Message-ID: To: Richard Salz Content-Type: multipart/alternative; boundary="000000000000fe209905ba265ff8" Subject: Re: [TUHS] tangential unix question: whatever happened to NeWS? X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000fe209905ba265ff8 Content-Type: text/plain; charset="UTF-8" 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. 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 cowan@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 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. > --000000000000fe209905ba265ff8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Those were just=C2=A0examples.=C2=A0 The har= d part is parsing schemas, especially if you're writing in C and don= 9;t know about yacc and lex.=C2=A0 That code tends to be horribly buggy.

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.=C2=A0 Easy-peasy, especially in a dynamically typed = language.

Once there was a per= son on the xml-dev mailing list who kept repeating himself, insisting on th= e superiority of ASN.1 to XML.=C2=A0 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 messag= e from that!=C2=A0 He took it in good part.



John Cowan =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0h= ttp://vrici.lojban.org/~cowan =C2=A0 =C2=A0 =C2=A0 =C2=A0cowan@ccil.org
Don't be so humble.=C2=A0 You= 're not that great.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 --Golda Meir


On Fri, Jan 29, 2021 at 10:52 PM Richard Salz <= ;rich.salz@gmail.com> wrote:<= br>
PER is not the reason for the hatred of ASN.1, it's more that the spec= s were created by a pay-to-play organization that fought against TCP/IP, th= e specs were not freely available for long years, BER was too flexible, and= the DER rules were almost too hard to get right.=C2=A0 Just a terse summar= y because this is probably off-topic for TUHS.
--000000000000fe209905ba265ff8--