The IETF procedures prior to publication of this BCP permitted such informational or experimental publication without IETF rough consensus. In 2007, the IESG issued a statement saying that no document will be issued without first conducting an IETF Last Call [IESG-STATE-AD
]. While this apparently improved the situation, when looking more closely, it made it worse. Rather than publishing documents without verifying that there is rough consensus, as the wording in [RFC 2026
] suggests, this had the IESG explicitly publishing documents on the IETF Stream that have failed to achieve rough consensus.
One could argue that there is a need for publishing some documents that the community cannot agree on. However, we have an explicit path for such publication, namely the Independent Stream. Or, for research documents, the IRTF Stream, which explicitly publishes minority opinion Informational RFCs.