Last Call Review of draft-ietf-json-i-json-05
review-ietf-json-i-json-05-opsdir-lc-schoenwaelder-2015-01-06-00

Hi,

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
operational area directors.  Document editors and WG chairs should
treat these comments just like any other last call comments.

As far as I can tell, the document is ready to be published. Having a
well defined restricted profile of JSON maximizing interoperability
certainly has value.

Personally, I like that a rationale is given for most
recommendations. It remains, however, a bit unclear to me why
base64url encoding is recommended in section 4.4 - is I-JSON text
expected to be embedded into URIs? While I am a bit fan of RFC 3339
encodings, it again remains somewhat unclear to me what this
recommendation has to do with I-JSON? There is no text, for example,
how to encoding IP addresses in I-JSON (and frankly, I think this is
fine - I am just mentioning this here as an example while wondering
why date and time encodings are mentioned as part of I-JSON).

My understanding is that compliance to I-JSON means compliance to
section 2 of this document. Perhaps it makese sense to clarify this
(in particular if my interpretation is wrong).

Editorial nit:

- s/values in in ISO 8601/values in ISO 8601/

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <

http://www.jacobs-university.de/

>