Simon Josefsson wrote:
If a proposal from the IETF is in conflict with the terms of the Trust
Agreement or the law then a Trustee has the obligation to veto it (a
fairly academic possibility, I believe).
I don't see how that is related to step 4 above. There is plenty of
mechanisms left for the Trust to veto changes to become effective -- for
example, you can just refuse to approve the change -- however my point
is about having the trust be able to cancel the process to modify the
TLP even before it has been subject to community discussion. That
approach appears contrary to the concept that the Trust carries out the
wishes of the IETF and not the other way around.
I don't see how this is possible: If the community believes that a
change should be made, the Trust has to (at least) review it and
explain why it believes that this is not a good idea. This brings
us to phase 5, community discussion, where one can discuss the
arguments for not making the change.
At this point several things can happen. One possibility is that the
community really wants the change but the Trust doesn't. In that
case, there is an possibility for appeal.
Henk
--
------------------------------------------------------------------------------
Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre http://www.xs4all.nl/~henku
P.O.Box 10096 Singel 258 Phone: +31.20.5354414
1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445
The Netherlands The Netherlands Mobile: +31.6.55861746
------------------------------------------------------------------------------
Belgium: an unsolvable problem, discussed in endless meetings, with no
hope for a solution, where everybody still lives happily.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf