Submission of charter for POISON

["Erik Huizer (SURFnet ExpertiseCentrum bv)" <[e-mail]>]

Here's the charter for the folow-up of poised95, and the formal
request toi the IESG to review this and establish the WG.

I have named it POISON, for reasons stated in the charter. If the
name seems to excessively dangerous the alternative is: POISSON. In
this case do a general search and replace POISSON for POISON, and the
explanation paragraph becomes:

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.

Now here's the charter, would the IESG please consider this.

Erik

===========
Process for Organization of Internet Standards ONgoing (POISON)

Chair(s)

        Erik Huizer <[e-mail]>

General Area Director(s):

        Fred Baker <[e-mail]>

Mailing List Information

        General Discussion:[e-mail]
        To Subscribe: [e-mail]
        Archive: ftp://ftp.tis.com/pub/ietf/poised/poised.mbox

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. POISON will
concern itself with extending the set of RFC documents that describe
the IETF process.

The danger 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. Like poison, you
need to find the maximum allowable dose, hence the name of the WG.

The POISED WG will work on the following items:
- 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. The POISON WG will concern itself with
  reviewing of this document in light of the other poised documents.

- IESG Charter; This document will be written by the IESG. Again the POISON WG
  will concern itself with reviewing of this document in light of the other
  poised documents.
- IAB Charter; The IAB needs to revise its charter (RFC1601). The POISON WG
will
  concern itself with reviewing of this document in light of the other poised
  documents.
- ISOC Bylaws and Articles of Incorporation; These need to be published as
  RFC(s). The POISON WG will make sure that ISOC publishes these documents as
  RFCs.

- 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 essentially a 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 a static document. It needs to be continually updated and adapted to
  current practices. The POISON WG will update the document in light of recent
  developments in the standards process. The POISED WG will also work on a
  proposal for a new and coherent document 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. If this is the case, the
  POISON WG will take it upon itself to update the document. Proposed editor:
  Jim Galvin
- Code of conduct; based on the Internet-draft:
  draft-odell-code-of-conduct-00.txt the POISON WG will produce a code of
  conduct for the IETF. proposed editor: Mike O'Dell

As befits an international organization, POISON will meet in Montreal, San
Jose and Memphis to try and gauge a rough consensus on these issues and
develop guidelines and drafts for the appropriate documents.


Goals and milestones

Jun 96          draft IETF charter posted
                ISOC bylaws submitted for RFC publication
                Meeting in Montreal

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
                IESG charter 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


=========