Re: Confused on "IETF Consensus"
"Theodore Y. Ts'o" <tytso@mit.edu> Thu, 13 June 1996 04:18 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06839; 13 Jun 96 0:18 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06832; 13 Jun 96 0:18 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa01211; 13 Jun 96 0:18 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06812; 13 Jun 96 0:18 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06751; 13 Jun 96 0:13 EDT
Received: from SOUTH-STATION-ANNEX.MIT.EDU by CNRI.Reston.VA.US id aa01155; 13 Jun 96 0:14 EDT
Received: from DCL.MIT.EDU by MIT.EDU with SMTP id AA00745; Thu, 13 Jun 96 00:12:04 EDT
Received: by dcl.MIT.EDU (5.x/4.7) id AA14281; Thu, 13 Jun 1996 00:13:42 -0400
Date: Thu, 13 Jun 1996 00:13:42 -0400
Message-Id: <9606130413.AA14281@dcl.MIT.EDU>
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Fred Baker <fred@cisco.com>
Cc: Robert Elz <kre@munnari.oz.au>, ietf@CNRI.Reston.VA.US
In-Reply-To: Fred Baker's message of Wed, 12 Jun 1996 18:22:58 -0700, <v02140b57ade51756a9b4@[171.69.128.114]>
Subject: Re: Confused on "IETF Consensus"
Address: 1 Amherst St., Cambridge, MA 02139
Phone: (617) 253-8091
Source-Info: From (or Sender) name not authenticated.
Date: Wed, 12 Jun 1996 18:22:58 -0700 From: Fred Baker <fred@cisco.com> Flip side of that is that, quite frankly, those who have been involved in writing the document are in most cases the best technical staff we have on that particular job, and the ones that are going to live with the consequences of their consensus (assuming it indeed exists). Those individuals have "paid their dues" so to speak; they have gone through the effort to do the Right Thing, and Get It Right. They have documented, implemented, argued, interoperability tested, and in some cases spent nights on their customer's premises making sure it worked for real people who are really depending on it. They have frequently put not only blood, sweat, and tears into it, they have put significant money in as well. While this works well for technical issues such as defining a protocol, it's not clear how well it works when the same "best technical staff" are inventing policy. The problem is that the wg may not include everyone who must "live with the consequences of the decision" in the wg, since the IETF in general has a disproportionate number of engineers over normal network users --- not surprising, really, given our charter. To give an example other than the one which sparked this whole discussion: Suppose you have a wg where one or two developers decide they wanted to be lazy and allow the use host tables in IPV6 implementations. This would have made a complete hash of the requirement it be easy to renumber the addresses IPV6 hosts. The problem was that people who would have to live with the consequences of that decision -- the users --- weren't represented in the working group! As I understand the history, this particular controversy had to bubble all the way up the IESG before it could be resolved sanely. The bottom line is that working groups *do* need checks and balances, becuase often times the interests of the implementers --- which are the majority of the people in most well-functioning working groups --- do not always reflect the best interests of the IETF or the Internet as a whole. It would be wise for us not to forget this. - Ted
- Re: Confused on "IETF Consensus" Scott W Brim
- Re: Confused on "IETF Consensus" Noel Chiappa
- Re: Confused on "IETF Consensus" Dave Crocker
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" Bob Hinden
- Re: Confused on "IETF Consensus" Fred Baker
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" Noel Chiappa
- Re: Confused on "IETF Consensus" Fred Baker
- Re: Confused on "IETF Consensus" Perry E. Metzger
- Re: Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" Perry E. Metzger
- Re: Confused on "IETF Consensus" Paul A Vixie
- Re: Confused on "IETF Consensus" Valdis.Kletnieks
- Re: Confused on "IETF Consensus" Bob Hinden
- Re: Confused on "IETF Consensus" Scott W Brim
- Re: Confused on "IETF Consensus" Robert Elz
- Re: Confused on "IETF Consensus" Perry E. Metzger
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" Greg Minshall
- Re: Confused on "IETF Consensus" Fred Baker
- Re: Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Steve Deering
- Re: Confused on "IETF Consensus" Robert Moskowitz
- Re: Confused on "IETF Consensus" Craig Partridge
- Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" SubSolar
- Re: Confused on "IETF Consensus" Fred Baker
- Re: Confused on "IETF Consensus" Joerg Heitkoetter
- Re: Confused on "IETF Consensus" Dave Crocker
- Re: Confused on "IETF Consensus" John Lekashman
- Re: Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Dave Crocker
- Re: Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Steve Deering
- Re: Confused on "IETF Consensus" Theodore Y. Ts'o
- Re: Confused on "IETF Consensus" Tim Bass
- Re: Confused on "IETF Consensus" Lixia Zhang
- Re: Confused on "IETF Consensus" Scott Bradner
- Re: Confused on "IETF Consensus" Craig Partridge
- Re: Confused on "IETF Consensus" Dave Crocker
- Re: Confused on "IETF Consensus" Masataka Ohta
- Re: Confused on "IETF Consensus" Robert Elz
- Re: Confused on "IETF Consensus" Noel Chiappa
- Re: Confused on "IETF Consensus" Philip J. Nesser
- Re: Confused on "IETF Consensus" Masataka Ohta
- Re: Confused on "IETF Consensus" Noel Chiappa
- Re: Confused on "IETF Consensus" Robert Elz