[Json] Ben Campbell's No Objection on draft-ietf-jsonbis-rfc7159bis-03: (with COMMENT)

Ben Campbell <ben@nostrum.com> Wed, 15 March 2017 00:52 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: json@ietf.org
Delivered-To: json@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EFFD11294AE; Tue, 14 Mar 2017 17:52:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ben Campbell <ben@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-jsonbis-rfc7159bis@ietf.org, Matthew Miller <mamille2@cisco.com>, jsonbis-chairs@ietf.org, mamille2@cisco.com, json@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148953916197.24379.5312613110015750797.idtracker@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 17:52:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/2A5LsyKvzkx3F9YKMjPaTzhpij0>
Subject: [Json] Ben Campbell's No Objection on draft-ietf-jsonbis-rfc7159bis-03: (with COMMENT)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2017 00:52:42 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-jsonbis-rfc7159bis-03: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- section 9: This allows limits for nesting depth, number range and
precision, and string length. Can you offer any guidance about what sorts
of limits might be reasonable? Or what limits might unreasonably impact
interoperability?

- 12, 2nd paragraph: This paragraph sort of buries the lede. I thought it
was going to talk about the implications of not being able to parse
certain JSON legal characters with eval(), but I understand it really
about the risk of arbitrary executable content. I suggest you say that in
the first sentence.