[Internal-cg] consensus building

[Joseph Alhadeff]

Jari

Just to note that it's best to discuss a process solution before a controversy emerges so I think that time spent now is advisable...

Joe

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----

From: Martin Boyle [Martin.Boyle at nominet.org.uk]
Received: Saturday, 06 Sep 2014, 12:35AM
To: Jari Arkko [jari.arkko at piuha.net]; WUKnoben [wolf-ulrich.knoben at t-online.de]
CC: Coordination Group [internal-cg at icann.org]
Subject: Re: [Internal-cg] consensus building

I think that this is very sensible, Jari.  I still think it will be worth noting "... a *small* minority disagree..."

-----Original Message-----
From: internal-cg-bounces at icann.org [mailto:internal-cg-bounces at icann.org] On Behalf Of Jari Arkko
Sent: 05 September 2014 17:20
To: WUKnoben
Cc: Coordination Group
Subject: Re: [Internal-cg] consensus building

I think the dedicated voting thresholds make the process too rigid and formal. I think the explanation of making an attempt to reach consensus or at the very least having only a minority disagree is sufficient. At the end of the day, rather than pure numbers the actual situation has to be taken into account and a decision has to be made.

My meta comment is also that we're spending a lot of time in designing the process for the controversial situations, when it is quite obvious that if we fail to reach broad consensus on the proposal the NTIA will in any case observe that their requirements have not been fulfilled.

(I do believe we will likely get _some_ controversy no matter how perfect the solution will be. But it is a different thing to have a couple of extreme opinions vs. significant parts of the communities having a problem.)

Jari

_______________________________________________
Internal-cg mailing list
Internal-cg at icann.org
https://mm.icann.org/mailman/listinfo/internal-cg