Re: Too many changes?

William Allen Simpson <bill.simpson@um.cc.umich.edu> Tue, 10 November 1992 22:00 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13176; 10 Nov 92 17:00 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13167; 10 Nov 92 17:00 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa19907; 10 Nov 92 17:01 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13152; 10 Nov 92 17:00 EST
Received: from Angband.Stanford.EDU by CNRI.Reston.VA.US id aa19897; 10 Nov 92 17:01 EST
Received: from via.oak1.merit.edu by Angband.Stanford.EDU (5.65/inc-1.0) id AA26134; Tue, 10 Nov 92 14:01:16 -0800
Date: Tue, 10 Nov 1992 13:16:30 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: William Allen Simpson <bill.simpson@um.cc.umich.edu>
Message-Id: <900.bill.simpson@um.cc.umich.edu>
To: poised@CNRI.Reston.VA.US
Reply-To: bsimpson@angband.stanford.edu
Subject: Re: Too many changes?

> From: Gary Scott Malkin <gmalkin@xylogics.com>
> every document.  This doesn't mean that an assigned reviewer might
> not feel the need for others in his group to read a potentially
> controversial draft.  So by starting "high level" review sooner,
> we can reduce the risk of a last minute surprise.
>
Most of your other points have already been addressed, so I will hit
this one.

Your analysis here assumes we need a "high level" review, and that the
"high level" reviewer has some special knowledge or qualifications which
make his review better than the WG and Area level.

We've already clearly debunked that myth.  Read the archives.

The salient advantage of the Crocker/Malamud structure is that it limits
technical review to the WG and Technical Board, and no further.  Process
Board (nee IAB) review occurs only when there is a formal protest
(probably no more than once a year), and is limited in scope.

Many, if not all, folks have expressed a desire for this change.  No
proposal will fly without it.

Bill.Simpson@um.cc.umich.edu