Update to MIME regarding "charset" Parameter Handling in Textual Media Types
RFC 6657
Yes
No Objection
Note: This ballot was opened for revision 02 and is now closed.
(Adrian Farrel; former steering group member) Yes
I struggled a bit with the escape clauses for the "SHOULD" statements, but I think I got it straight, and I support the publication of this document.
(Barry Leiba; former steering group member) Yes
(Pete Resnick; former steering group member) Yes
(Ron Bonica; former steering group member) Yes
(Benoît Claise; former steering group member) No Objection
(Brian Haberman; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Martin Stiemerling; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) (was Discuss) No Objection
(Russ Housley; former steering group member) No Objection
Please consider the editorial issues raise in the Gen-ART Review by Vijay Gurbani on 27-Apr-2012. The review can be found here: http://www.ietf.org/mail-archive/web/gen-art/current/msg07401.html
(Sean Turner; former steering group member) No Objection
(Stephen Farrell; former steering group member) No Objection
I'm a bit confused here, and would like to check how much:-) Old subtypes use ascii as a default but don't say that explicitly and will not be changed by this RFC. New subtypes SHOULD NOT define a default. So when I go look at the registry do I need to compare the date of registration vs. the date of this RFC to know what's what?
(Stewart Bryant; former steering group member) No Objection
(Wesley Eddy; former steering group member) No Objection