a.
Review
mechanisms
The group
considers review mechanisms to be mechanisms that assess the
performance and
relevance of processes or structures, and provide
recommendations (binding
or
not binding) [MW1] for improvement.
Examples
include:
-
Periodic
structural reviews of SOs and ACs (as currently mandated in the
ICANN Bylaws)
-
AoC-mandated
ICANN organizational reviews for Accountability and
Transparency; Security,
Stability, and Resiliency; WHOIS; and Competition and Consumer
Trust.
b.
Redress
mechanisms
The group
defines redress mechanisms as mechanisms that focus on assessing
the compliance
or relevance of a certain decision, and can conclude to its
confirmation,
cancellation or amendment. The output of such mechanism shall be
binding.
Examples
include:
-
Independent
Review (if it is considered to be binding)
-
State
of California or jurisdictions where ICANN has a presence Court
decisions
[MW1]Should
we
keep that ?
1. I think some of the mechanisms that are labeled "redress" are actually "review". See the definitions below, but basically, since mechanisms like ReconRequest and IRP and the Ombudsman are only making recommendations to the board to change its mind on a decision, and have no authority to set aside a decision on their own, they more appropriately categorized as "review" mechanisms (and not redress).
-- ***************************** Mathieu WEILL AFNIC - directeur général Tél: +33 1 39 30 83 06 mathieu.weill@afnic.fr Twitter : @mathieuweill *****************************