• Revised I-D Needed - Issue raised by WG
  • Awaiting Expert Review/Resolution of Issues Raised
  • Awaiting External Review/Resolution of Issues Raised
  • Awaiting Merge with Other Document
  • Author or Editor Needed
  • Waiting for Referenced Document
  • Waiting for Referencing Document
  • Revised I-D Needed - Issue raised by WGLC
  • Revised I-D Needed - Issue raised by AD
  • Revised I-D Needed - Issue raised by IESG
  • Doc Shepherd Follow-up Underway
  • Other - see Comment Log

IETF :: appsawg

Current state: Submitted to IESG for Publication

Viewing the last 20 entries. Show full log.

(System)

RFC published

(System)

RFC Editor state changed to AUTH48-DONE from AUTH48

(System)

RFC Editor state changed to AUTH48 from AUTH48-DONE

(System)

RFC Editor state changed to AUTH48-DONE from AUTH48

(System)

RFC Editor state changed to AUTH48 from RFC-EDITOR

Amy Vezza

State changed to RFC Ed Queue from Approved-announcement sent

(System)

IANA Action state changed to No IC

Amy Vezza

State changed to Approved-announcement sent from Approved-announcement to be sent

Amy Vezza

IESG has approved the document

Amy Vezza

Closed "Approve" ballot

Amy Vezza

Ballot approval text was generated

Barry Leiba

State changed to Approved-announcement to be sent from IESG Evaluation::AD Followup

Barry Leiba

[Ballot Position Update] Position for Barry Leiba has been changed to Yes from Discuss

Mark Nottingham

New revision available

Cindy Morgan

State changed to IESG Evaluation::AD Followup from IESG Evaluation

Barry Leiba

[Ballot discuss]
I'm putting a DISCUSS on to hold this for now while I have a bit of discussion with the authors about the arrays vs objects issue.

Barry Leiba

[Ballot Position Update] Position for Barry Leiba has been changed to Discuss from Yes

Benoit Claise

[Ballot comment]
- I consider this draft as poor in explaining the use cases and example for the JSON pointer.
In comparison, draft-ietf-appsawg-json-patch did a much better job.
The interaction, if any, with the JSON patch should be explained. It nothing else as a potential use case/example.
JSON-PATCH mentions:

Additionally, operation objects MUST have exactly one "path" member,
whose value MUST be a string containing a [JSON-Pointer] value that
references a location within the target document to perform the
operation (the "target location").

But JSON-POINTER doesn't even mention JSON-PATCH
So bad luck is someone starts by reading JSON-POINTER...

- For the record, I insert Dan Romascanu's OPS DIR review, stressing the need to reclassify RFC 4627 sooner than latter:

By now, if somebody makes a snapshot after these documents will be approved a rather odd situation shows up. Two (maybe more documents) which are standards track extend a base document which is Informational. Standards that extend non-standards. If 4627 was Standards Track we would have used 'Updates RFC 4627' in the meta-data, but of course we cannot do it now.

Nothing critical happens (I think) as long as things work OK - but probably the sooner reclassifying 4627 happens the better.

Benoit Claise

[Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise

Gonzalo Camarillo

[Ballot Position Update] New position, No Objection, has been recorded for Gonzalo Camarillo

Viewing the last 20 entries. Show full log.