Re: [secdir] draft-ietf-appsawg-json-pointer-07 SECDIR Review

Mark Nottingham <mnot@mnot.net> Wed, 02 January 2013 05:20 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA61321E8049; Tue, 1 Jan 2013 21:20:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.765
X-Spam-Level:
X-Spam-Status: No, score=-103.765 tagged_above=-999 required=5 tests=[AWL=-1.166, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YnrP5JCzJVxN; Tue, 1 Jan 2013 21:20:32 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id BA4B821E8042; Tue, 1 Jan 2013 21:20:31 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.74.65]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 75034509B5; Wed, 2 Jan 2013 00:20:29 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAF4+nEGChp0KtUDf-RtGweTZhzKk1OEU-+4a+JJ4mMvuWN061w@mail.gmail.com>
Date: Wed, 2 Jan 2013 16:20:25 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <96188DBD-355B-4363-B8EA-C969EE6F6B77@mnot.net>
References: <CAF4+nEEDfhv=J_BnXJjj7q2_9tf16RCUpTHspQcky1+F_0JTzA@mail.gmail.com> <F8C63186-C869-46DC-8C05-EBCD5BEE8D13@mnot.net> <CAF4+nEGChp0KtUDf-RtGweTZhzKk1OEU-+4a+JJ4mMvuWN061w@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-appsawg-json-pointer.all@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] draft-ietf-appsawg-json-pointer-07 SECDIR Review
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 05:20:46 -0000

On 02/01/2013, at 4:18 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> Hi Mark,
> 
> On Tue, Jan 1, 2013 at 11:12 PM, Mark Nottingham <mnot@mnot.net> wrote:
>> Thanks for the review; replies below.
>> 
>> On 31/12/2012, at 2:11 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>> 
>>> I have reviewed this document as part of the security directorate's
>>> ongoing effort to review all IETF documents being processed by the
>>> IESG.  Document editors and WG chairs should treat these comments just
>>> like any other last call comments.
>>> 
>>> This draft describes two closely related syntaxes for pointers to
>>> objects within a JSON (JavaScript Object Notation) document. One is a
>>> JSON string syntax, the other is a URI fragment identifier for URIs
>>> defined to take such a fragment identifier.
>>> 
>>> Security:
>>> 
>>> I do not see any security problems with this document. The syntax
>>> appears to be unambiguously specified, including ABNF, and the
>>> Security Considerations Section is adequate and touches on the
>>> potential pit-falls that JSON pointers can contain NULs.
>>> 
>>> Miscellaneous:
>>> 
>>> I found significant ambiguity in the semantics of a JSON pointer
>>> string. Is the result of the successful evaluation ("evaluation" is a
>>> term used in the draft) of such a pointer string a structure that
>>> points into a JSON document or is it the objection pointed to? It
>>> mostly seems to be an object but it is specifically provided that
>>> array references could point beyond the end of an array and at least
>>> in that case perhaps some sort of pointer structure would be returned
>>> with the error condition. It probably doesn't matter, because these
>>> syntaxes are intended to be used in a variety of applications and it
>>> will be up to the application to clarify the semantics.
>> 
>> I think it's purposefully ambiguous, to accommodate a variety of applications.
> 
> OK.
> 
>>> Minor:
>>> 
>>> The expansion for the acronym JSON should be given in the title and abstract.
>> 
>> In SVN.
> 
> What does that mean? If you mean to say that you agree with the change
> suggested and that it will be in the next version posted, you should
> say that.

It does. Could it mean something else, I wonder?


>>> In the first line of the second paragraph of Section 6, I found the
>>> word "nominate" kind of odd. Why not "specify" or "select" or "use"?
>> 
>> In SVN.
> 
> Same response as above.
> 
>>> None of the Authors Addresses given includes a postal address.
>> 
>> Yes.
> 
> I think they should. I find that such corner cutting typically goes
> with other sloppiness.


Alternatively, it could mean that the authors don't wish to expose their postal addresses. Or, that they believe that their electronic addresses will be more stable than physical ones.


--
Mark Nottingham   http://www.mnot.net/