IETF Logo Mail Archive

Re: [saag] ASN.1 vs. DER Encoding

Volker Birk <vb@pep-project.org> Tue, 26 March 2019 17:29 UTC

Return-Path: <vb@pep-project.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2E91206C6 for <saag@ietfa.amsl.com>; Tue, 26 Mar 2019 10:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbY_agyqSEqX for <saag@ietfa.amsl.com>; Tue, 26 Mar 2019 10:29:17 -0700 (PDT)
Received: from dragon.pibit.ch (dragon.pibit.ch [94.231.81.244]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BF301206CC for <saag@ietf.org>; Tue, 26 Mar 2019 10:29:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by dragon.pibit.ch (Postfix) with ESMTP id B09BA171C06B for <saag@ietf.org>; Tue, 26 Mar 2019 18:29:07 +0100 (CET)
Received: from dragon.pibit.ch ([127.0.0.1]) by localhost (dragon.pibit.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3zaUtdkAfqLD for <saag@ietf.org>; Tue, 26 Mar 2019 18:29:05 +0100 (CET)
Received: from localhost (unknown [213.55.184.222]) by dragon.pibit.ch (Postfix) with ESMTPSA id D150E171C057 for <saag@ietf.org>; Tue, 26 Mar 2019 18:29:04 +0100 (CET)
Date: Tue, 26 Mar 2019 18:29:04 +0100
From: Volker Birk <vb@pep-project.org>
To: saag@ietf.org
Message-ID: <20190326172904.22g5luiuptdhmca3@pep-project.org>
Mail-Followup-To: saag@ietf.org
References: <21dec229-5b5c-8d52-6817-edac2e39ceec@openca.org> <20190326164951.GX4211@localhost>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="ffefddrxihvwro26"
Content-Disposition: inline
In-Reply-To: <20190326164951.GX4211@localhost>
X-PGP-Key: http://fdik.org/vb.key
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/JHF41nqZCC8Kwa_2_OtDjG2b028>
Subject: Re: [saag] ASN.1 vs. DER Encoding
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2019 17:29:19 -0000

On Tue, Mar 26, 2019 at 11:49:51AM -0500, Nico Williams wrote:
> However, it is true that BER/DER are pretty much the only encoding rules
> used in IETF documents, and that is mostly a result of lack of tooling.

p≡p is using PER and XER. We're using this Free Software tool for it:

http://lionet.info/asn1c/compiler.html

Yours,
VB.
-- 
Volker Birk, p≡p project
mailto:vb@pep-project.org
https://pep.software

v2.23.0 | Report a Bug | By Email