On 10/6/13 7:30 PM, Mark Nottingham wrote:
This is a VERY useful document, and I look forward to compelling my WG
participants to read it, with a pop quiz afterwards.
I've been exceedingly satisfied to hear this sort of thing from you and
the other folks who posted and talked to me about
On 10/6/13 4:34 PM, Mark Nottingham wrote:
> On 07/10/2013, at 11:03 AM, Dave Crocker wrote:
>> 1. in a natural state; without decoration or other treatment. "a
>> diamond in the rough"
>> 2. in difficulties. "even before the recession hit, the project was
>> in the rough"
> I think he's using it
On 07/10/2013, at 11:03 AM, Dave Crocker wrote:
>> Now, a conclusion of having only rough consensus relies heavily on
>> the good judgement of the consensus caller. The group must truly
>> consider and weigh an issue before the objection can be dismissed as
>> being "in the rough". The
This is a VERY useful document, and I look forward to compelling my WG
participants to read it, with a pop quiz afterwards.
The only issue I see is its length; while dedicated IETFers won't have a
problem reading such a lengthy document, the people who could benefit most -
new, potential or cas
+1. I've referred people to earlier versions already.
Review
Title:On Consensus and Humming in the IETF
draft-resnick-on-consensus-05
Reviewer: D. Crocker
Reivew data: 6 Oct 2013
Summary:
The draft discusses IETF processes for making group decisions,
especially in the face of disagreement. As the draft notes, th
i have found it quite useful in venues other than the ietf. go for it.
and thanks, pete.
randy
On 10/6/13 1:03 PM, Jari Arkko wrote:
> My goal is to publish it as an Informational RFC. It is an
> explanation of principles and how they can be applied to productively
> move IETF discussions forward. While there is no change to IETF
> processes or any presumption that guidance from this documen
The document talks about ways in which consensus processes can be successfully
run in the IETF. After the last few rounds of versions, I believe this document
is ready to move forward.
My goal is to publish it as an Informational RFC. It is an explanation of
principles and how they can be appl
