[Trans] Comments on RFC6962

Phillip Hallam-Baker <hallam@gmail.com> Mon, 10 March 2014 19:25 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 00BFE1A0538 for <trans@ietfa.amsl.com>; Mon, 10 Mar 2014 12:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id slj0LBZxtcdc for <trans@ietfa.amsl.com>; Mon, 10 Mar 2014 12:25:32 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id E0DD51A048A for <trans@ietf.org>; Mon, 10 Mar 2014 12:25:18 -0700 (PDT)
Received: by mail-la0-f53.google.com with SMTP id b8so4882805lan.40 for <trans@ietf.org>; Mon, 10 Mar 2014 12:25:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DR7gzMSPBvwPsMOP5GTIbcV3TkcSxh55fbBcrblszwg=; b=TiUn1MMJYuJDYcnnGAWjbdBc6fIiEH8bl+b5GjMUsM8e3zk9ou4bo3CUxcwRxRq1TA 28bTMIH5i7z+FlhEGF9MF9rlAoP1F2eJVaGhI2c55QxsQ/MTCprwbFTcL7MBpJoQNd32 PW41nsB1Y0e06gQ3k7lOWma3Qf7C3aTdwGD5bzmMHZxPAem8FPWMWY/18fHWqpl/x5gg xbWQVxKYfD/uI/mi9Y9P5niaXE/xJ7mFacNxW9Bwd92M5L4aZTQfDZKyOnkQ20U7WZC/ DVnW+E1qDiJ9tI56Iyuun4GCfWT5saNhVaq4NsgWTYI+PmbUYpIEhSWkrxAOPzreQzuv dtQw==
MIME-Version: 1.0
X-Received: by with SMTP id ri10mr23283193lbb.9.1394479512803; Mon, 10 Mar 2014 12:25:12 -0700 (PDT)
Received: by with HTTP; Mon, 10 Mar 2014 12:25:12 -0700 (PDT)
Date: Mon, 10 Mar 2014 15:25:12 -0400
Message-ID: <CAMm+LwiYZi=+dPFecO7GHQc5=-d=tWenkQ-igMJtfpq0PenN9w@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "trans@ietf.org" <trans@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c25dea01de6c04f445901e"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/ySxKSFcsimLlsonGM7s5qlTdV50
Subject: [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: Mon, 10 Mar 2014 19:25:34 -0000

I am currently working on entering RFC6962 into my protocol compiler. This
has 'certain ideas' about regularity and conformance which is of course the
point of the exercise.

Some issues arising:

[Page 17]
      extensions:  An opaque type for future expansion.  It is likely
         that not all participants will need to understand data in this
         field.  Logs should set this to the empty string.  Clients
         should decode the base64-encoded data and include it in the

I have no idea why this would be needed. JSON allows any object to be
extended with arbitrary additional tags. I have no idea how this would be
used as well. There isn't a mechanism to tell the receiver what type of
data to expect.

If we did need to extend a message the way to do it would be to extend the
object with a new tag. JSON rules require the tag be ignored.

There is an open question on how to manage JSON extensibility. Some folk
are proposing going the XML route and an equivalent of the xmlns tag.
Reserved words are yucky and unnecessary though. If we want to use URIs as
a mechanism for describing an extension we can do that by using the URI as
a tag:

If the original message looks something like:

{ "a" : 1,
  "b" : 2 }

We can add a new tag for the FOO extension with unique identifier
urn:iana:someregistry:FOO as follows:

{ "a" : 1,
  "b" : 2,

Website: http://hallambaker.com/