Re: Draft 0 of proposed charter
Jeffrey Altman <[email protected]> Tue, 11 May 2004 17:29:16 -0400
| Newsgroups | gmane.ietf.cat |
|---|---|
| Organization | No Longer Affiliated with Columbia University in the City of New York |
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------070700050701030807010705 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I do not believe this proposed charter is too long. It does indicate that there are a lot of work items which the KITTEN working group would be expected to complete. In order to gain permission for the BOF we should put together a document for the IESG containing an executive summary of each of the proposed charter items. I think a relative priority associated with each item would also be useful. With a list this long the two things we are going to have to demonstrate to the IESG is that there are enough participants interested in performing the work; as well as the will to get the work done in a timely manner. Jeffrey Altman Sam Hartman wrote: >Here's a proposed charter. I realize that it's too long for a real >charter. For now I'd like to have an exaustive list of all the work >we plan to do so we can evaluate whether our scope is too extensive. >I'd appreciate suggestions on how to actually organize things for a >normal length charter. > > --------------070700050701030807010705 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <font face="Bitstream Cyberbit">I do not believe this proposed charter is too long. It does indicate that there<br> are a lot of work items which the KITTEN working group would be expected<br> to complete.<br> <br> In order to gain permission for the BOF we should put together a<br> document for the IESG containing an executive summary of each of the<br> proposed charter items. I think a relative priority associated with each<br> item would also be useful. With a list this long the two things we are<br> going to have to demonstrate to the IESG is that there are enough <br> participants interested in performing the work; as well as the will to get<br> the work done in a timely manner.<br> <br> Jeffrey Altman<br> <br> <br> Sam Hartman wrote:<br> </font> <blockquote cite="[email protected]" type="cite"> <pre wrap=""><font face="Bitstream Cyberbit">Here's a proposed charter. I realize that it's too long for a real charter. For now I'd like to have an exaustive list of all the work we plan to do so we can evaluate whether our scope is too extensive. I'd appreciate suggestions on how to actually organize things for a normal length charter. </font></pre> </blockquote> </body> </html> --------------070700050701030807010705-- -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to [email protected]