Re: Selection Process

CASE@utkvx.utk.edu Wed, 25 November 1992 23:30 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10773; 25 Nov 92 18:30 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10762; 25 Nov 92 18:30 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa11593; 25 Nov 92 18:31 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10751; 25 Nov 92 18:30 EST
Received: from UTKVX2.UTK.EDU by CNRI.Reston.VA.US id aa11576; 25 Nov 92 18:31 EST
Received: from utkvx.utk.edu by utkvx.utk.edu (PMDF #3151 ) id <01GRKTSHBKSM96WDY8@utkvx.utk.edu>; Wed, 25 Nov 1992 18:29:49 EDT
Date: Wed, 25 Nov 1992 18:29:49 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: CASE@utkvx.utk.edu
Subject: Re: Selection Process
To: KLENSIN@infoods.mit.edu
Cc: poised@CNRI.Reston.VA.US
Message-id: <01GRKTSHBKSO96WDY8@utkvx.utk.edu>
X-VMS-To: IN%"KLENSIN@infoods.mit.edu"
X-VMS-Cc: IN%"poised@CNRI.Reston.VA.US",CASE
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-transfer-encoding: 7bit

I heartily support John's position, and the way he said it.

To refresh your memory, his key points were:
	1.  We shouldn't ever have to use a recall procedure.
	2.  It's unlikely we'll ever be forced to use it.
	3.  "It is probably better to have a recall procedure--and make it
	    hard enough to use, and at the end of enough procedures, that 
	    it will rarely if ever be triggered--than to be without such a
	    procedure.
	4.  The alternative (being without one) is too expensive.

I agree.

jdc