Erik and all,
Thanks Erik, I shall pass this one in this response to others
that may have an interest.
Erik.Huizer wrote:
> Sorry for the delay, but here's the new charter based on the discussions in
> Orlando. unless there is substantial discussion I will send this to steve
> Coya early next week.
>
> Erik
>
> ------------------------------------------------------------------------
> Process for Organization of Internet Standards ONgoing (poisson)
>
> Last Modified: 18-feb-99
>
> Chair(s):
>
> Erik Huizer <[EMAIL PROTECTED]>
>
> General Area Director(s):
>
> Fred Baker <[EMAIL PROTECTED]>
>
> General Area Advisor:
>
> Fred Baker <[EMAIL PROTECTED]>
>
> Mailing Lists:
>
> General Discussion:[EMAIL PROTECTED]
> To Subscribe: [EMAIL PROTECTED]
> Archive: ftp://ftp.tis.com/pub/lists/poised/poised.yymm
>
> 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 is concerned with
> documenting issues relevant to 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 in 1999:
>
> - Review of copyright issues as described in RFC2026,
> that describes the Internet standards proces.
>
> - Drafting of a contract for registration and assignment of protocol
> parameters as performed by the IANA.
> The WG will focus on the operational and technical aspects of the
> contract. The IETF lawyer will be asked to add the necessary legal
> phrases.
>
> - Discuss the relationship between IETF and ICANN.
> Should IETF be part of ICANN? If so, as part of the ICANN PSO?
> Under which conditions?
> An RFC detailing the position will be published if the WG
> decides that the IETF should not be part of the ICANN PSO.
> RFC on proposed ICANN PSO bylaws will be produced if the WG
> consensus is in favor of joining the PSO. Furthermore, in the latter
> case an RFC will be produced that describes how ICANN PSO
> officers (on behalf of the IETF) are to be selected.
>
> 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).
>
> Last but not least, Poisson will serve as a generic platform where the
> IAB and IESG can discuss policy questions if there is the need for
> consensus polling.
>
> Goals and Milestones:
>
> Mar 99 Second version of proposed IANA contract
> Mar 99 Second version of drafts for ICANN PSO bylaws and
> IETF PSO officer selection, or first draft describing
> why IETF should not be involved with ICANN
> Mar 99 Internet-draft for IETF mailing list blocking
>
> Mar 99 Present ICANN related issues at IETF plenary
>
> Jun 99 Final version of all drafts
>
> Jul 99 Submit drafts to IESG
>
> Internet-Drafts:
>
> Bylaws for a Protocol Support Organization (45440 bytes)
> Procedures for IETF appointments to the Protocol Supporting Organization
> (6387 bytes)
>
> Request For Comments:
>
> IAB and IESG Selection, Confirmation, and Recall Process: Operation of the
> Nominating and Recall Committees (RFC 2282) (29852 bytes)
> IETF Working Group Guidelines and Procedures (RFC 2418) (62857 bytes)
Regards,
--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail [EMAIL PROTECTED]
Contact Number: 972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
