Re: [Ianaplan] What's happening at ICANN?

Actually a high percentage of the CCWG proposal has been about what happens
when a board member is asked to vacate his/her position (or perform some
other action) by the community and such board member doesn't want to.

There is really no believe that a board member asked to leave on valid
reasons could comply in respect of existing process. That is what I think
is the difference with IETF which hold trust as a strong virtue in its
processes. If MS was highly based on legal formalities, I wonder whether if
it would have survive this long.

Some could say it's perhaps because one counts money than the other.

Cheers!
Sent from my Asus Zenfone2
Kindly excuse brevity and typos.
On 13 Oct 2015 19:56, "Bob Hinden" <bob.hinden@gmail.com> wrote:

> Avri,
>
> > On Oct 13, 2015, at 11:05 AM, Avri Doria <avri@acm.org> wrote:
> >
> > Hi,
> >
> > One essential difference is that IETF has an appeal mechanism on process
> > to the Internet Society Board of Trustees.
> > This is the backstop for the IETF.
>
> The Internet Society Board of Trustees is the last step in the multi-step
> IETF appeals process.  The IETF appeals process is documented in RFC2026.
>
>    https://www.rfc-editor.org/rfc/rfc2026.txt
>
> The IETF appeals process is actually used periodically.  Appeals and their
> resolution are listed at:
>
>    https://www.ietf.org/iesg/appeal.html
>    https://www.iab.org/appeals/
>
> On a related topic, the procedure to recall sitting IESG, IAB, and IAOC
> members is defined in RFC7437.  See:
>
>    https://tools.ietf.org/html/rfc7437
>
> These processes seem to work (that is, "are running code” so to speak).
> They might serve as a model for other organizations as I think they are a
> good example for multi-stakeholder self-governance.
>
> Bob
>
>
>
> >
> >> From what I have learned in the ICANN Accountability process, the most
> > legal training I have ever had, the IETF as the IETF might have trouble
> > suing anyone given that is is not a legal person.  Fortunately the IETF
> > does not live in an environment where suits, of either kind, are the
> norm.
> >
> > avri
> >
> > On 10-Oct-15 12:57, Soininen, Jonne (Nokia - FI/Espoo) wrote:
> >> Hi Brian,
> >>
> >> like Bernard and Dave said, part of the story is the press tries to spin
> >> an interesting story. Partly the story is that there are strong emotions
> >> in play at the ICANN in this topic.
> >>
> >> So, the topic is ICANN accountability. The claim is that as long as
> there
> >> was the NTIA contract on IANA there has been a backstop on ICANN's
> >> decisions, especially the board's. The theory is that if ICANN (the
> staff
> >> and the board, not the community) would do something silly NTIA could at
> >> least threaten to take IANA away and pressure ICANN to reconsider the
> >> decision get to the right path. However, with the IANA stewardship
> >> transition there would be no backstop anymore and potentially a future
> >> board could go rogue and do whatever they want disregarding the
> community.
> >> Therefore, there needs to be new accountability mechanisms.
> >>
> >> The main accountability mechanisms discussed have been spilling the
> >> complete board, removing a board member and control/veto the ICANN
> budget
> >> and bylaws changes. There is pretty much consensus that in some form or
> >> another these are reasonable requirements. However, the discussion is
> >> about what is the right enforceability mechanism. Enforcement means how
> >> can you legally enforce ICANN/board do something - basically, how can
> you
> >> sue ICANN if the board/staff doesn't do what the community expects it to
> >> do.
> >>
> >> In the IETF, we have a bit different approach to these things. I
> wouldn't
> >> think we would have ever the discussion the IETF community should be
> able
> >> to take the IESG or IAB to court. Interesting thought, though... ;)
> >>
> >> I hope this helps.
> >>
> >> Cheers,
> >>
> >> Jonne.
> >
> >
> > ---
> > This email has been checked for viruses by Avast antivirus software.
> > https://www.avast.com/antivirus
> >
> > _______________________________________________
> > Ianaplan mailing list
> > Ianaplan@ietf.org
> > https://www.ietf.org/mailman/listinfo/ianaplan
>
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>
>