This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/cooperation-wg@ripe.net/
[cooperation-wg] Internet governance
- Previous message (by thread): [cooperation-wg] Internet governance
- Next message (by thread): [cooperation-wg] Internet governance
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
SM
sm at resistor.net
Tue Nov 19 14:17:23 CET 2013
At 00:53 19-11-2013, Roland Perry wrote: >For example, a meeting can agree the need for policy objectives in >respect of rolling out IPv6, but could get derailed if there's >protracted disagreement about whether to call it "deployment" or >"migration". So put that word in square brackets and move on to >agree the broad principles, while a subgroup works out which word >has, yes I'll use the word, consensus. At 01:23 19-11-2013, Nurani Nimpuno wrote: >I completely disagree with the comparison. Consensus is not about >spending more time finding the right wording that everyone can agree >on for that particular detail in that particular paragraph. >Consensus is a lot more pragmatic than that. But let's not get into >a long discussion about what consensus is. I'll rewrite the first (quoted) paragraph as: For example, a meeting can agree the need for policy objectives in respect of rolling out IPv6, but could get derailed if there's protracted disagreement about whether to call it "deployment" or "migration". So put that word in square brackets and move on to agree the broad principles, while a subgroup works out which word has, yes I'll use the word, [consensus]. Regards, -sm
- Previous message (by thread): [cooperation-wg] Internet governance
- Next message (by thread): [cooperation-wg] Internet governance
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]