IETF Logo Mail Archive

Re: [TLS] TLS grammar checker?

Bill Frantz <frantz@pwpconsult.com> Tue, 18 June 2013 22:20 UTC

Return-Path: <frantz@pwpconsult.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A498811E8113 for <tls@ietfa.amsl.com>; Tue, 18 Jun 2013 15:20:23 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CU586b8t+4Q7 for <tls@ietfa.amsl.com>; Tue, 18 Jun 2013 15:20:09 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 44A6411E8112 for <tls@ietf.org>; Tue, 18 Jun 2013 15:20:09 -0700 (PDT)
Received: from [173.75.83.226] (helo=Williams-MacBook-Pro.local) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <frantz@pwpconsult.com>) id 1Up4Fz-00033n-Iq; Tue, 18 Jun 2013 18:20:07 -0400
Date: Tue, 18 Jun 2013 15:20:07 -0700
From: Bill Frantz <frantz@pwpconsult.com>
To: Nico Williams <nico@cryptonector.com>
X-Priority: 3
In-Reply-To: <CAK3OfOgL=C0QOFM=SBU4rZm2_pnZkrBEoP8GzfjfO6eQtfULyw@mail.gmail.com>
Message-ID: <r422Ps-1075i-41C9ABE15E3C4284891C37A3920A0713@Williams-MacBook-Pro.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.3.1 (422)
X-ELNK-Trace: 3a5e54fa03f1b3e21aa676d7e74259b7b3291a7d08dfec79db3ec25924e9f3f09291541c58668128350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 173.75.83.226
Cc: tls@ietf.org
Subject: Re: [TLS] TLS grammar checker?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 22:20:23 -0000

On 6/18/13 at 10:36 AM, nico@cryptonector.com (Nico Williams) wrote:

>This would make it possible to use ASN.1 for
>specifying JSON schemas too, but no one who doesn't already have to
>use ASN.1 wants to use ASN.1, though I myself like ASN.1 -- I only
>hate its TLV encodings.

Given the history of serious security problems due to ASN.1 
parser bugs, I would feel better with a simpler format. (And 
yes, I'm one of the people who developed an allergy to ASN.1 
through use.)

Cheers - Bill

-----------------------------------------------------------------------
Bill Frantz        |The nice thing about standards| Periwinkle
(408)356-8506      |is there are so many to choose| 16345 
Englewood Ave
www.pwpconsult.com |from.   - Andrew Tanenbaum    | Los Gatos, 
CA 95032

v2.29.0 | Report a Bug | By Email | System Status