Matthew Miller (JSON WG co-chair) is the document shepherd and Pete Resnick is
the responsible AD.
This document defines a profile of JSON (RFC 7159). This profile further
restricts characters, numbers, object members; it also provides additional
recommendations for protocol use.
This document is intended to be a Proposed Standard.
2. Review and Consensus
The WG discussion was not as extensive as for RFC 7159, but still broad. Two
major points were brought up in WG Last Call: defining a link relation profile
URI, and the use of base64 versus bsae64url.
It was suggested that a profile URI be defined as an alternative to defining a
media type or media type suffix (which is also not defined in this document).
However, the WG could not reach consensus on this change.
There was considerable debate over the use of base64 versus base64url. The WG
consensus was that binary data be encoded as some form of base64 but could not
reach any consensus on which specific variant. The document first specified
base64url and without consensus to change it, it remains the recommendation in
Overall, the consensus on publishing this document is rough. At least one
participant still questions its utility, although several participants have
brought up at least the JOSE WG's collection of normative documents as a user.
3. Intellectual Property
There was no WG discussion of IPR given that this document defines a subset of
a format for which there was no IPR statements in the first place.
4. Other Points
There are no normative downrefs.
There are no IANA considerations.