30 Sep
2009
30 Sep
'09
6:05 p.m.
Actually, it would be RFC2616, not RFC2068.
Oops, my apologies!
Furthermore, we're actually doing this in the IETF HTTPbis Working Group.
Yes, I was aware of this activity.
So let's rephrase it... do you have an opinion whether an update to HTTP/1.1 *should* make this change?
I believe that the RFCs for XML media type should faithfully follow MIME and HTTP/1.1. When the first RFC for XML media types was created, I was told that neither MIME RFCs nor HTTP/1.1 can be changed here. Ten years have passed since then. I think that facts (ideally based on statistics of correct/incorrect charset) should be documented first and then a required change (if any) should be introduced. Cheers, -- MURATA Makoto <murata@hokkaido.email.ne.jp>