Sam Hartman (hartmans) wrote,
Sam Hartman
hartmans

IESG, Consensus and Community Interaction

A while back I commented on concerns about the ISD proposals expressed by the IESG. We've created yet another stir by declining a request to assign an IANA codepoint. I was responsible for the most controversial part of that decision: we went beyond declining the request and actually recommended against bringing the request for IETF review. The reason was simple. We think we know the parties involved well enough to know that the proposal will not be received favorably. We don't think spending years reviewing the proposal and ultimately deciding against will be in anyone's interest.

Putting it mildly, some people are upset. There are a lot of reasons; here I'm going to focus on people who are upset because we made a specific recommendation. What puzzles me is that some of these people would have been happier if we had withheld our belief that the review effort would be a waste of time. It seems misleading to withheld this information: the requester might well assume that we were supportive of the request but just wanted broader review. Such an impression would create great frustration when years later after review, the request was declined. There's an impression that by expressing an opinion, the IESG will not fairly follow the process should the community try to take a different course. Some seem unwilling to believe that if the requester did actually want IETF review the IESG would follow a fair process in seeking that review. I can understand the idea that if the IESG has a strong opinion it might get in the way of fair process. However that's true regardless of whether we actually express the opinion. It seems important to express such opinions; it seems important not to give people the false impression that they should spend a lot of time on a proposal without giving them realistic estimation of their chances of success. We need to find a way to do that without causing those who decide to go against our recommendation to feel that we are being unfair.

Another current frustration is the idea that the IESG is not part of the community. Particularly on process issues, some have expressed the opinion that when looking for consensus the IESG should be discounted. That seems dangerous: you don't want to exclude the opinion of a reasonably large subset of the people active in working with the standards process when deciding how that process should work. Besides leading to bad solutions, it is personally frustrating to be told that no, you aren't worth listening to. I realize it comes with the job. That doesn't mean I have to like it.

Tags: ietf
Subscribe
  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 3 comments