A Media Type Structured Syntax Suffix for JSON Text Sequences
RFC 8091

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

(Ben Campbell) Yes

Comment (2016-12-14 for -02)
No email
send info
-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.

Alissa Cooper Yes

(Alexey Melnikov) Yes

Comment (2016-12-15 for -02)
No email
send info
Waiting for Expert Review from Ned Freed till the end of December 2016.

(Jari Arkko) No Objection

(Alia Atlas) No Objection

Deborah Brungard No Objection

(Benoît Claise) No Objection

(Spencer Dawkins) No Objection

(Stephen Farrell) No Objection

(Joel Jaeggli) No Objection

(Suresh Krishnan) No Objection

(Mirja Kühlewind) No Objection

Comment (2016-12-12 for -02)
No email
send info
Is it really needed to copy the whole security considerations section of RFC7464 in this doc?

And why was this not registered within RFC7464?

(Kathleen Moriarty) No Objection

Alvaro Retana No Objection