Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
draft-reschke-rfc2231-in-http-12
Yes
(Alexey Melnikov)
No Objection
(Adrian Farrel)
(Dan Romascanu)
(Gonzalo Camarillo)
(Lars Eggert)
(Ralph Droms)
(Robert Sparks)
(Ron Bonica)
(Stewart Bryant)
(Tim Polk)
Note: This ballot was opened for revision 12 and is now closed.
Alexey Melnikov Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
(was Discuss)
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
()
Unknown
Gonzalo Camarillo Former IESG member
No Objection
No Objection
()
Unknown
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Peter Saint-Andre Former IESG member
No Objection
No Objection
(2010-04-19)
Unknown
In Section 3.2, there appears to be confusion between the terms "mime-charset" and "ext-charset". Section 4.1 of this I-D states: Section 4.2 of [RFC2277] requires that protocol elements containing text are able to carry language information. Thus, the ext-value production should always be used when the parameter value is of textual nature and its language is known. In fact RFC 2277 states that "[a]ll human-readable text has a language" and appears to emphasize human-readable text. Although it's not truly clear if RFC 2277 makes a distinction between "text" and "human-readable text", it might be useful to incorporate that distinction here because many textual strings included in protocol elements are not intended for human consumption.
Ralph Droms Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
(2010-04-22)
Unknown
Sean Turner Former IESG member
(was Discuss)
No Objection
No Objection
(2010-04-18)
Unknown
Sec 3.3, Is the link to the WG ticket stable enough for a standards track document? Sec 4.1, r/should/SHOULD X2 Sec 4.2, r/recommended/RECOMMENDED
Stewart Bryant Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
No Objection
No Objection
(2010-04-19)
Unknown
In section 3.2: Producers MUST NOT use character sets other than "UTF-8" ([RFC3629]) or "ISO-8859-1" ([ISO-8859-1]). Extension character sets (ext- charset) are reserved for future use. ext-charset does not appear in the ABNF. Should it?