I think I triggered off the last round of extended-charset-header debate
some time back. (Cannot be sure - have not read everything in the 300
messages since then....)
I have now come to an opposite opinion to what I had then:
- RFC-XXXX should be finished WITHOUT a mechanism for extending headers.
Reason: 6 months (or whatever needed) more of this discussion before
RFC-XXXX is "cast in concrete" is TOO LONG.
Also my opinion:
- There seems to be general agreement that the issue IS important, and
may be addressed by a separate RFC issued at a later date.
This means that the issue will not be forgotten (I hope), which was one
important reason for calling it a SHOW-STOPPER.
So, let's get on with publishing, implementing and managing RFC-XXXX SOON!
Harald Tveit Alvestrand
Speaking for myself