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. Minor: The expansion for the acronym JSON should be given in the title and abstract. 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"? None of the Authors Addresses given includes a postal address. Thanks, Donald ============================= Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3 at gmail.com