People get burned when they think of IETF as means of legitimizing industry support for their particular approach. The IETF is *NOT* that. Most RFCs turn out to be worthless summarily ignored by real world in spite of all process hoops jumped through by WG participants and reviews.
Much better outcomes are realized when IETF is viewed not as a "standards committee" rather as a service no different than github... where instead of developing your own standards process you simply use IETF leeching off existing structure, facilities, recognition, meeting spaces... while not perfect it may well be better and or cheaper than rolling your own.
This means if you want to succeed you need a working implementation first and foremost, actual users in the real world ... "working code" without interested users and or industry partners IS NOT going to cut it. Then finally go to the IETF with your I-D + LEGION of faithful consensus building followers who support your ideas.
The IETF is like a country of mostly autonomous states (WGs) ... Some WG's are oppressive dictatorships taxing oxygen you breath while others are utopias of cooperation where consensus is not merely defined by whatever the chairs want to see... Unfortunately overall governance is not all that great. One of the running jokes for me is appeals process. Having subscribed to IETF announce a millennia ago have never once read or heard of even a single appeal that was ever upheld...ever. This has grown into something of a game to be careful to check before pushing delete in the off chance hell may some day actually freeze over.
In short if you come looking for the IETF to instill legitimacy upon your idea or approach you WILL leave disappointed.
If you come to the IETF from a position of strength willing to put up with some process bullshit you stand a chance of coming out ahead.