WG guidelines DRAFT!

[Erik Huizer <[e-mail]>]

Folks,

As a result of the Poised effort several parts of the new process will have
to be documented. We discussed this in the IESG, and came up with at least
three documentsthat need to be produced to document the new process:
- - RFC-1310 bis
- - Charter of IETF
and to complement these a simple document with WG guidelines. I volunteered
to write the latter one, which has just been published as an Internet draft
(see below). The I-D is trying to document the IETF WG process in such
a way that it isn't too strict (and thus resulting in bureaucratic
procedures) nor too lose (and thus leaving too many holes for
misunderstandings in the process). I hope it just states what needs to be
stated to avoid unnecessary miscommunications between WGs and the IESG etc.

Although this is an IESG document, the IESG certainly wants to invite
comments from the Poised WG, as to whether the interpretation of the process
in this I-D is correct. The document does not go into detail on the
standardsprocess itself (that's for RFC-1310bis) nor on the IETF
electionprocess etc (Charter of IETF), and is thus heavily depending on
these documents.

Looking forward to your comments

Erik

- ------- Forwarded Message

Date:    Wed, 13 Jan 93 10:15:56 -0500
From:    [e-mail]
To:      IETF-Announce:;
cc:      [e-mail]
Subject: ID ACTION:draft-ietf-iesg-wgguidelines-00.txt

- - --NextPart

A New Internet Draft is available from the on-line Internet-Drafts 
directories. This draft is a work item of the IETF Steering Group 
Working Group of the IETF.                                            

       Title     : IETF Working Group Guidelines and Procedures       
       Author(s) : E. Huizer
       Filename  : draft-ietf-iesg-wgguidelines-00.txt
       Pages     : 11

The Internet Engineering Task Force (IETF) has the primary 
responsibility for the development and review of potential Internet 
Standards from all sources. The IETF is organized into Working Groups 
(WG). This document describes the guidelines and procedures for 
formation and operation of an IETF Working Group. It describes the 
formal relationship between a WG and the Internet Engineering and 
Steering Group (IESG). The basic duties of a WG chair and an IESG Area
Director are defined.                                                 

Internet-Drafts are available by anonymous FTP.  Login with the	
username "anonymous" and password "guest".  After logging in,
Type "cd internet-drafts".
     "get draft-ietf-iesg-wgguidelines-00.txt".
 
Internet-Drafts directories are located at:	
	                                                
     o  East Coast (US)                          
        Address:  nnsc.nsf.net (128.89.1.178)	
	                                                
     o  West Coast (US)                          
        Address:  ftp.nisc.sri.com (192.33.33.22)
							
     o  Pacific Rim                              
        Address:  munnari.oz.au (128.250.1.21)	
	                                                
     o  Europe                                   
        Address:  nic.nordu.net (192.36.148.17)	
	                                                
Internet-Drafts are also available by mail.	
	                                                
Send a message to:  [e-mail]. In the body type: 
     "SEND draft-ietf-iesg-wgguidelines-00.txt".
							
For questions, please mail to [e-mail].
							

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the Internet Draft.

- - --NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

- - --OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="[e-mail]"

Content-Type: text/plain

SEND draft-ietf-iesg-wgguidelines-00.txt

- - --OtherAccess
Content-Type:   Message/External-body;
        name="draft-ietf-iesg-wgguidelines-00.txt";
        site="nnsc.nsf.net";
        access-type="anon-ftp";
        directory="internet-drafts"

Content-Type: text/plain

- - --OtherAccess--
- - --NextPart--


- ------- End of Forwarded Message