Another twist on my proposal

[Mike O'Dell <[e-mail]>]

Instead of "Completely Random Application or Protocol", call the new
RFC class

	"Cannot Ever Be A Standard"

(CEBAS - pronounced "sea bass" - think of a better acronym if you wish)

To summarize my previously proposed rules

	If you can convince the IESG something is A Good Idea,
	it can go out "Informational".  The IESG reserves absolute
	right of refusal for anything to go Informational for any
	reason - suspected jiggery-pokery a very good reason. Another
	would be things we thing are Wrong for whatever reason moves
	us to concensus.

	If you cannot convince the IESG you have A Good Idea, the
	document can still be published as a CEBAS, but there is
	a profound consequence:  the protocol or technology described
	in the document will be barred from ever being introduced
	into the Standards Track "without fundamental revision or
	reformulation."  The IESG reserves the right to issue wavers
	of this limitation, but only if a minimum of 2 years has
	passed between issuance as a CEBAS and the request for the
	waver.


This restriction should materially deter anyone from using CBAS as a
way of "getting an RFC number" prematurely, especially if they have
designs on standards-status later on.

We retain an avenue-of-last-resort, which I think is a good idea, but
we put some teeth into what it means to use it.  

my comments about how to roll this out still apply.

Whacha think?

	-mo