Community,
We had discussed at the plenary in IETF103 (as well as other venues) some potential improvements which may be made in the WG process of conflict resolution and obtaining consensus.
There will be a second draft with potential solutions to the issues that have been pointed out in the draft below.
Please let us know your thoughts.
Thanks,
Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360
Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360
----- Forwarded Message -----
From: "internet-drafts@xxxxxxxx" <internet-drafts@xxxxxxxx>
To: Nalini Elkins <nalini.elkins@xxxxxxxxxxxxxxxxxx>; Henning Schulzrinne <hgs@xxxxxxxxxxxxxxx>
Sent: Wednesday, December 5, 2018 8:19 AM
Subject: New Version Notification for draft-elkschul-conflict-problem-01.txt
A new version of I-D, draft-elkschul-conflict-problem-01.txt
has been successfully submitted by Nalini Elkins and posted to the
IETF repository.
Name: draft-elkschul-conflict-problem
Revision: 01
Title: Conflict Resolution within a Working Group: Problem Statement
Document date: 2018-12-05
Group: Individual Submission
Pages: 11
Abstract:
At the IETF, we currently use a set of methods to communicate a point
of view, to solicit input, to resolve conflict and attempt to obtain
consensus within the group.. These methods include: writing an
Internet Draft, discussion on email lists, discussion at face-to-
face, interim or virtual meetings, and design teams. At times, these
methods fall short. People become entrenched in their positions. A
Working Group may be split for a prolonged period wasting time and
energy. There may be a lasting impact. While the authors support
rough consensus, the collateral damage of this process, at times can
be considerable. This document discusses the benefits and drawbacks
of each of the current methods of communication focusing solely on
their efficacy at conflict resolution. A companion document will
propose some solutions including alternative methods of conflict
resolution.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat