A Media Type Structured Syntax Suffix for JSON Text Sequences
draft-wilde-json-seq-suffix-03

Note: This ballot was opened for revision 02 and is now closed.

Alvaro Retana No Objection

(Alexey Melnikov; former steering group member) Yes

Waiting for Expert Review from Ned Freed till the end of December 2016.

(Alissa Cooper; former steering group member) Yes

(Ben Campbell; former steering group member) Yes

-4: Would it make sense to add something like "..., or any IESG designated successor." to the contact? The ART merger has recently shown that even area WG mailing lists do not live forever.

-5: I share Mirja's curiosity about why the security considerations from 7464 were copied rather than just referenced.

(Alia Atlas; former steering group member) No Objection

(Benoît Claise; former steering group member) No Objection

(Deborah Brungard; former steering group member) No Objection

(Jari Arkko; former steering group member) No Objection

(Joel Jaeggli; former steering group member) No Objection

(Kathleen Moriarty; former steering group member) No Objection

(Mirja Kühlewind; former steering group member) No Objection

Is it really needed to copy the whole security considerations section of RFC7464 in this doc?

And why was this not registered within RFC7464?

(Spencer Dawkins; former steering group member) No Objection

(Stephen Farrell; former steering group member) No Objection

(Suresh Krishnan; former steering group member) No Objection