On Tue, Dec 16, 2008 at 5:35 PM, Brian E Carpenter <[email protected]> wrote: >> Step 2. I ask each of you to propose eliminating one or more of the >> strategies. If I get a strong consensus then I'll remove >> that strategy. > > I don't think that "remove" is the right thing to do. I think that such > strategies should continue to be documented in a "roads not followed" > section of the draft, with a succinct explanation. Otherwise, you can be > sure, they will come back again and again.
Hi Brian, I concur. Rather than delete them, I'll move them to a section titled something along the lines of "rejected strategies," with perhaps sentence or two composed from the choicer comments. >> Step 3. I'll ask for weak consensus on forming IETF working groups to >> pursue specific strategy variants. Weak consensus means lots have >> something to say and more agree than disagree. I'll mark them >> accordingly in the document. My hunch is that two or three will pass >> this hurdle, but we'll see when the time comes. > > Wouldn't you also want to see at least one proof-of-concept proposal > for each? We have plenty of those around, so enumerating the ones that > match each strategy variant would probably make the weak consensus > more explicit. For the moment I want to err on the side of being inclusive. If that yields a consensus to move too many things forward, I'll back up and try a different approach. Also, bear in mind that I won't accept proposals in the form "Let's recommend a LISP working group." Rather, I'll ask folks to specify, "let's recommend a working group for a Strategy A system based on variants 1,2,3." That the variants were selected to match LISP is fine. And if the resuling WG's first order of business is to adopt LISP rather than consider other map-encap protocols with the same criteria, that's fine too. Regards, Bill Herrin -- William D. Herrin ................ [email protected] [email protected] 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004 _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
