[eqvinox]

> …information RFC? He can’t stop that, right?

Informational RFCs still need to pass through the IETF consensus process, changing the intended status isn't a procedural bypass. However, the authors can just publish it elsewhere, it makes no difference at all for the codepoint allocations. Only distinction is that it doesn't get the somewhat intangible (but existent) "RFC sheen".

[ekr____]

This document actually is being advanced as Informational, though there are also non-IETF Informational RFCs (see upthread).