Re: [Trans] Comments on RFC6962
Bill Frantz <frantz@pwpconsult.com> Tue, 11 March 2014 19:48 UTC
Return-Path: <frantz@pwpconsult.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8191A07C6 for <trans@ietfa.amsl.com>; Tue, 11 Mar 2014 12:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 VJDN2_Qd0fj4 for <trans@ietfa.amsl.com>; Tue, 11 Mar 2014 12:48:21 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id E64AC1A07C1 for <trans@ietf.org>; Tue, 11 Mar 2014 12:48:20 -0700 (PDT)
Received: from [173.75.83.129] (helo=Williams-MacBook-Pro.local) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <frantz@pwpconsult.com>) id 1WNSes-0005J6-1i; Tue, 11 Mar 2014 15:48:14 -0400
Date: Tue, 11 Mar 2014 12:48:12 -0700
From: Bill Frantz <frantz@pwpconsult.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Priority: 3
In-Reply-To: <CAMm+Lwi5wUijNyLH+fGBTS4w3c57juCwRO+kh5mKK9sebR=txw@mail.gmail.com>
Message-ID: <r422Ps-1075i-E91B6AF7C1ED4B0ABB7930CEDC8535F1@Williams-MacBook-Pro.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.3.1 (422)
X-ELNK-Trace: 3a5e54fa03f1b3e21aa676d7e74259b7b3291a7d08dfec7925e6393b3f776fef311d5b681543adbb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 173.75.83.129
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/kohx_EqyUX2l6OwsIqOXhiIXGhE
Cc: trans@ietf.org
Subject: Re: [Trans] Comments on RFC6962
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Mar 2014 19:48:23 -0000
On 3/10/14 at 5:18 PM, hallam@gmail.com (Phillip Hallam-Baker) wrote: > On Mon, Mar 10, 2014 at 8:14 PM, Bill Frantz <frantz@pwpconsult.com> wrote: > > > On 3/10/14 at 12:25 PM, hallam@gmail.com (Phillip Hallam-Baker) wrote: > > > > There is an open question on how to manage JSON extensibility. > >> > > > > There's no problem here. JSON will not be extended. Doug Crockford, the > > inventor of JSON is adamant that there is only one version. Forever. > > You are misunderstanding me. > > The 'JSON extensibility' issue is not how to extend JSON encoding, the > issue is how to handle extensibility of the TRANS protocol that is encoded > in JSON. Oops - Sorry > Adding tags in JSON is straightforward and existing applications SHOULD > simply ignore them. But we should probably make some sort of explicit > statement. Indeed, being explicit is always best when writing standards. Cheers - Bill ----------------------------------------------------------------------- Bill Frantz |Security, like correctness, is| Periwinkle (408)356-8506 |not an add-on feature. - Attr-| 16345 Englewood Ave www.pwpconsult.com |ibuted to Andrew Tanenbaum | Los Gatos, CA 95032
- [Trans] Comments on RFC6962 Phillip Hallam-Baker
- [Trans] Fwd: Comments on RFC6962 Phillip Hallam-Baker
- Re: [Trans] Comments on RFC6962 Bill Frantz
- Re: [Trans] Comments on RFC6962 Phillip Hallam-Baker
- Re: [Trans] Comments on RFC6962 Rob Stradling
- Re: [Trans] Comments on RFC6962 Bill Frantz
- Re: [Trans] Comments on RFC6962 Jon Callas