Re: Confused on "IETF Consensus"

Robert Moskowitz <rgm3@chrysler.com> Thu, 13 June 1996 11:03 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13110; 13 Jun 96 7:03 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13097; 13 Jun 96 7:03 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa06047; 13 Jun 96 7:03 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13064; 13 Jun 96 7:03 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12964; 13 Jun 96 6:59 EDT
Received: from [204.189.94.35] by CNRI.Reston.VA.US id aa05974; 13 Jun 96 6:59 EDT
Received: by pilot.firewall.is.chrysler.com; id GAA03978; Thu, 13 Jun 1996 06:58:52 -0400
Received: from clhubgw1-le0.is.chrysler.com(172.29.128.203) by pilot.is.chrysler.com via smap (g3.0.1) id sma003974; Thu, 13 Jun 96 06:58:30 -0400
Received: from rgm3 by clhubgw1-nf0.is.chrysler.com (8.7.5/SMI-4.1) id HAA23817; Thu, 13 Jun 1996 07:01:42 -0400 (EDT)
Message-Id: <2.2.32.19960613105710.00bb194c@pop3hub.is.chrysler.com>
X-Sender: t3125rm@pop3hub.is.chrysler.com
X-Mailer: Windows Eudora Pro Version 2.2 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 13 Jun 1996 06:57:10 -0400
To: Craig Partridge <craig@aland.bbn.com>, Tim Bass <bass@linux.silkroad.com>
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Robert Moskowitz <rgm3@chrysler.com>
Subject: Re: Confused on "IETF Consensus"
Cc: Craig Partridge <craig@aland.bbn.com>, fred@cisco.com, ietf@CNRI.Reston.VA.US
Source-Info: From (or Sender) name not authenticated.

At 03:52 PM 6/12/96 -0700, Craig Partridge wrote:
>
>Dissenter is someone who disagrees and may object to promotion of the document
>for technical or social reasons which are at least somewhat independent
>of their self interest (and, I would hope, tries to offer alternative
>solutions that address his or her concerns).
>
I would like to add a 'real world' example to a previous event that had
decension.

RFC1597 begat RFC1627 (think I got the #s right).  Until RFC1918 came out
they were both used in the community, 1597 to explain how to do it, and 1627
to explain why it might be a bad idea.

Disenters have a voice, it is publish.

Of course, that was back in the old days before everyone was using the
'right to publish' as an end-run around wgs.  A considered disenting
document (much like what 1627 (or is it 47, oh well, too early in the
morning after a big community wedding)) helps everyone.  The flames against
this document should never be publish as an RFC, as they do not add value.


Robert Moskowitz
Chrysler Corporation
(810) 758-8212