Submission of charter for POISON
"Erik Huizer (SURFnet ExpertiseCentrum bv)" <Erik.Huizer@sec.nl> Fri, 19 July 1996 15:38 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09474; 19 Jul 96 11:38 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09470; 19 Jul 96 11:38 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09397; 19 Jul 96 11:38 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09461; 19 Jul 96 11:38 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09457; 19 Jul 96 11:38 EDT
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa09392; 19 Jul 96 11:38 EDT
Received: from surah.surfnet.nl by survis.surfnet.nl with SMTP (PP) with ESMTP; Fri, 19 Jul 1996 17:37:11 +0200
Received: from surfnet.nl (actually host surah.surfnet.nl) by surah.surfnet.nl with SMTP (PP) with ESMTP; Fri, 19 Jul 1996 17:38:06 +0200
Subject: Submission of charter for POISON
To: Fred Baker <fred@cisco.com>
Cc: IESG <iesg@CNRI.Reston.VA.US>, poised@tis.com
Organisation: SURFnet ExpertiseCentrum bv
Address: Radboudburcht, P.O. Box 19115, 3501 DC Utrecht, NL
Phone: +31 302 305 305
Telefax: +31 302 305 329
X-url: http://www.sec.nl/persons/huizer/
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8371.837790681.1@surfnet.nl>
Date: Fri, 19 Jul 1996 17:38:02 +0200
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Erik Huizer (SURFnet ExpertiseCentrum bv)" <Erik.Huizer@sec.nl>
Message-ID: <9607191138.aa09392@CNRI.Reston.VA.US>
Process for Organization of Internet StandardS ONgoing (POISSON) Chair(s) Erik Huizer <Erik.Huizer@sec.nl> General Area Director(s): Fred Baker <fred@cisco.com> Mailing List Information General Discussion:poised@tis.com To Subscribe: poised-request@tis.com Archive: ftp://ftp.tis.com/pub/lists/poised/poised.yymm (yy=year, mm=month) Description of Working Group The POISED working group in 1993-1994 established the basis of the IETF process in its current form. Poised95 established a base set of documents to describe the essentials of the IETF process. POISSON will concern itself with extending the set of RFC documents that describe the IETF process. The name POISSON The tricky part of describing the IETF process, certainly in the fast changing world of the Internet, is that when you describe the process in too much detail, the IETF loses its flexibility, when you describe to little it becomes unmanageable. This is therefore a slippery subject, hence the name POISSON, which is French for fish. The French word also serves to indicate the international aspect of the WG. Furthermore the IETF operates by concensus, which sometimes seems to have a POISSON distribution. The POISSON WG will work on the following items: - WG and Area procedures; This is to become a BCP document that describes the procedures that the IETF has for WG formation and operation, and for Area Directors. This is an essential formalisation and update of RFC1603. The document should additionally include issues like: - WG editor definition - WG chair (de)selection - WG ethics Proposed editors: Scott Bradner and Erik Huizer - Standards process; The standards process document as produced by Poised95 is not yet complete. The document needs to be updated with specific regard to the standards document structure categorization and publication. Proposed editor: Scott Bradner - Nomcom procedures; The Nomcom procedures document as produced by Poised95 may need updating as a result of nomcom experience early 1997. If this is the case, the POISSON WG will take it upon itself to update the document. If not the POISSON WG will not work on this. Proposed editor: Jim Galvin - Code of conduct; based on the Internet-draft: draft-odell-code-of-conduct-00.txt the POISSON WG will produce a code of conduct for the IETF. proposed editor: Mike O'Dell Furthermore, the POISSON WG will review documents that are related to the IETF standards process (but that will not be produced by the POISSON WG itself) when available. Such documents may include: - IETF Charter; This needs to be written by the IETF chair. It is essentially a short mission statement like document that contains references to other Poised documents for further details. - IESG Charter; This document will be written by the IESG. - IAB Charter; The IAB needs to revise its charter (RFC1601). - ISOC Bylaws and Articles of Incorporation; These need to be published as RFC(s). - The IRTF charter. As befits an international organization, POISSON will meet in Montreal (just outside the USA), San Jose (USA) and Memphis (USA) to try and gauge a rough consensus on these issues and develop guidelines and drafts for the appropriate documents. Goals and milestones Oct 96 draft of RFC1603bis published draft IESG charter published IETF charter published draft revision of standards process published draft-odell-code-of-conduct-01.txt published Dec 96 revised draft of RFC1603bis published revised draft of standards process published meeting in San Jose Mar 97 draft revision of Nomcom procedures published submission of code of conduct draft to IESG Apr 97 meeting in Memphis May 97 submission of standards process, nomcom procedures and RFC1603bis documents to IESG for publication as BCPs
- Submission of charter for POISON Erik Huizer (SURFnet ExpertiseCentrum bv)
- Re: Submission of charter for POISON John C Klensin
- Re: Submission of charter for POISON Brian Carpenter CERN-CN
- Re: Submission of charter for POISON John C Klensin
- Re: Submission of charter for POISON Fred Baker
- Submission of charter for POISON Erik Huizer (SURFnet ExpertiseCentrum bv)
- Re: Submission of charter for POISON Keith Moore
- RE: Submission of charter for POISON Jim Browning
- Re: Submission of charter for POISON Erik Huizer (SURFnet ExpertiseCentrum bv)
- RE: Submission of charter for POISON Scott Bradner