On Sep 18, 2017, at 6:15 PM, Ted Hardie <ted.ietf@xxxxxxxxx> wrote:Most of the text in RFC 3629 seems still on the mark, not that I'm an expert, but if we take it to be true, it has some advice. That says that you should forbid the use of U+FEFF as a signature when you have character encoding identification mechanisms, and that you can retain it otherwise. What do we think the case is here?
Well, presumably we are disabling FTP downloads since they aren't authenticatable, so in practice the http server can identify the text as text/utf8, which would mean that the RFC3629 advice to follow would be the first clause, not the second.
|