The way the author uses "RFC" is that it's essentially a possibly very rough draft design document for some technical implementation. The "Comments" part is wha

The way the author uses "RFC" is that it's essentially a possibly very rough draft design document for some technical implementation. The "Comments" part is what is otherwise known as a "design review." My opinion is that what to do with feedback and final decision authority rests with the proposal owner except under certain circumstances. Some of these would be if a component of the proposal is particularly complicated, clearly not completely understood by the team (e.g. there are dependencies on other teams that need more clarity), or contentious (e.g. major rewrites, switching to new frameworks or data storage and pipelines, etc.). In the latter I require consensus especially: proliferation of languages, data store solutions, and frameworks is a real problem and rarely a good solution.