Shepherd writeup
rfc6902-10

1. Summary

Murray Kucherawy is the Document Shepherd.
Barry Leiba is the responsible Area Director.

JSON Patch defines the media type "application/json-patch", a JSON
document structure for expressing a sequence of operations to apply
to a JSON document.

This document is requesting Proposed Standard status as it defines a standard
format and interpretation of a "pointer" string in the context of JSON.
Proposed Standard is the appropriate RFC type under Section 4.1 of RFC2026.

2. Review and Consensus

This draft and its companion (draft-ietf-appsawg-json-pointer) received
commentary from a number of participants.  The original author
was unable to complete the work so the current editor stepped in.
There was no controversy of import; good work was done here.

APPSAWG has a very broad participation base.  Accordingly, only a small
percentage has weighed in on this work, but I believe that subset is large
enough to be able to claim that the development and review work has been
broad enough to say we have consensus.

Many of the participants who contributed review comments are well
established in the IETF and W3C communities.  I believe the review
and participation was thorough and contained adequate (if not better)
expertise on the relevant topics.

Implementations are being tracked at
http://trac.tools.ietf.org/wg/appsawg/trac/wiki/JsonPatch.

3. Intellectual Property

The authors have affirmed that they know of no impending relevant IPR claims,
nor do they know of any that have been filed.

There was one claim of prior authorship reported to me and to the editors.
Details will be provided to the Applications Area Directors in short order.

4. Other Points

There is a downward normative reference to RFC 4627 (Informational).
RFC 4627 is in the downref registry.

This document registers a new media type using the template found in
Section 10 of RFC4288.  RFC4288 is about to be replaced by another
document, currently in the RFC Editor queue.  The registration template
is slightly different in the new version.  We can either ask the authors to
submit a new version of this draft using the revised template, or leave it
to the IESG and IANA to handle during the transition.
Back