Take [the ICANN Board Resolution] as a snapshot of the board's current thinking. It is vague (in some sense) because it is not a decree that changes any of the rules in practice _today_. But it does send a signal about the direction things perhaps should move in.
At one level, it means nothing, because it makes no changes to current practice. The resolution by itself does not eliminate the waiver.
What it is saying is that ICANN (as a community) should move to "include fees for all dojmains added, including domains added during the AGP"
Whether that actually happens (in reality) we won't know until the budget development process plays out (i.e., over the next few months). That is an open/public process, where everyone will have a chance to weigh in.
But I think you can read the resolution as saying the board would be inclined to support a change. I say "inclined" only because at the end of the day, the board will look at the specific proposal it is asked to approve, and weigh the overall pros/cons of that proposal.
What it is saying is that ICANN (as a community) should move to "include fees for all dojmains added, including domains added during the AGP"
Whether that actually happens (in reality) we won't know until the budget development process plays out (i.e., over the next few months). That is an open/public process, where everyone will have a chance to weigh in.
But I think you can read the resolution as saying the board would be inclined to support a change. I say "inclined" only because at the end of the day, the board will look at the specific proposal it is asked to approve, and weigh the overall pros/cons of that proposal.
If his interpretation is correct -- and you should read it yourself here -- ICANN won't impose the fee unless the ICANN community supports it and, even then, it won't go into effect until the next budget cycle, starting on 1 July 2008.
