Re: DNSEXT future

[bmanning@karoshi.com]

> For this reason we asked the meeting and our AD for guidance on what to do
> with the working group. The three options are
> 	A. keep the working group open
> 	B. Put the group to sleep/hibernate
> 	C. Close the working group
> 
> Options A and B require a new charter, the main reason for keeping the
> working group alive is to have an official place to take DNS ideas
> and have them processed (i.e. killed).
> A living working group (case A) may keep attacking work which is
> of limited value.
> A group in hyphenation state still has a chair and official mailing
> list it can process ID's as needed but does not meet.
> 
> The feedback that the chairs was that option A was not attractive to the
> people in the room.
> 
> Option B had supporters and is advocated by our AD.
> There are few people advocating option C as that sends the strongest
> message that changes to DNS and DNSSEC are done and there is nothing more
> to do.


	good summary.
	B has the downside that a single person(s) (WG chair) is chartered 
	to judge the worthiness of any proposed new work.  Such a gatekeeper
	is prone to abuse, neglect, etc.

	C, imho, is more properly characterized as "nothing more to do at this
	time" - leaving the Mailing list open, but the WG itself in a 
	dormant state (e.g. less than the "hyphenated" version of "B"
	is my prefered outcome.

	fending off bad ideas can be done by the retained DNS directorate.
	new ideas should be the result of a group, forming a charter and 
	having a specific task list to accomplish.

> 
> The purpose of this message is to gauge the mailing list as to which option
> they think is the most appropriate.
> 
> Draft charter for DNSEXT in hyphenated state:
>     The DNSEXT WG group will actively maintain the DNS protocol and is
>     available for advancing DNS protocol related RFCs on the standard
>     track, while defending against further enhancements of questionable
>     value.
> 
> 
> 	Olafur & Olaf 
> 
> 
> --
> to unsubscribe send a message to namedroppers-request@ops.ietf.org with
> the word 'unsubscribe' in a single line as the message text body.
> archive: <http://ops.ietf.org/lists/namedroppers/>

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>