IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Tue, 26 March 2019 17:25 UTC

Return-Path: <cabo@tzi.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 3748D120677 for <saag@ietfa.amsl.com>; Tue, 26 Mar 2019 10:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 fUdiT0rHkrcC for <saag@ietfa.amsl.com>; Tue, 26 Mar 2019 10:25:47 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FC8E1206B5 for <saag@ietf.org>; Tue, 26 Mar 2019 10:25:47 -0700 (PDT)
Received: from dhcp-8804.meeting.ietf.org (dhcp-8804.meeting.ietf.org [31.133.136.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 44TJ1k0YxdzycW; Tue, 26 Mar 2019 18:25:46 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20190326164951.GX4211@localhost>
Date: Tue, 26 Mar 2019 18:25:45 +0100
Cc: "Dr. Pala" <madwolf@openca.org>, "saag@ietf.org" <saag@ietf.org>
X-Mao-Original-Outgoing-Id: 575313943.723559-8726f619e367ee51da4d43b4fdee31fd
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BF013AF-DA67-45B0-9A06-9922EB07EAB5@tzi.org>
References: <21dec229-5b5c-8d52-6817-edac2e39ceec@openca.org> <20190326164951.GX4211@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/G0BQ41DcRy013xL1ab6WiaDArqE>
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:25:50 -0000

On Mar 26, 2019, at 17:49, Nico Williams <nico@cryptonector.com> wrote:
> 
> It's always easier to create new legacy than to deal with old legacy,
> even though new legacy very soon becomes old legacy, and so new legacy
> is invariably worse than old legacy, just not right away.  Few
> understand this.

Oh, it’s legacy when you already have typed it in.

But I’d still rather program in C++20 legacy than in FORTRAN II legacy.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email