W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1998

FW: BCP 25, RFC 2418 on Working Group Guidelines

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Tue, 22 Sep 1998 13:45:09 -0700
To: WEBDAV WG <w3c-dist-auth@w3.org>
Message-ID: <001801bde669$e39fd7e0$d115c380@galileo.ics.uci.edu>
FYI -- I occasionally get asked questions on how IETF working groups
operate, and the roles of various positions within the working group.  This
document, along with RFC 2026, provides normative descriptions.

- Jim

-----Original Message-----
From: RFC Editor [mailto:rfc-ed@isi.edu]
Sent: Monday, September 21, 1998 10:51 AM
To: IETF-Announce: ;
Cc: rfc-ed@isi.edu
Subject: BCP 25, RFC 2418 on Working Group Guidelines

A new Request for Comments is now available in online RFC libraries.

        BCP 25:
        RFC 2418:

        Title:	    IETF Working Group Guidelines and Procedures
	Author(s):  S. Bradner
	Status:     Best Current Practice
	Date:       September 1998
        Mailbox:    sob@harvard.edu
	Pages:      26
        Characters: 62857
        Obsoletes:  1603

        URL:        ftp://ftp.isi.edu/in-notes/rfc2418.txt

The Internet Engineering Task Force (IETF) has responsibility for
developing and reviewing specifications intended as Internet
Standards. IETF activities are organized into working groups (WGs).
This document describes the guidelines and procedures for formation
and operation of IETF working groups. It also describes the formal
relationship between IETF participants WG and the Internet Engineering
Steering Group (IESG) and the basic duties of IETF participants,
including WG Chairs, WG participants, and IETF Area Directors.

This document is a product of the Process for Organization of Internet
Standards ONgoing Working Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute
Received on Tuesday, 22 September 1998 17:12:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:18 UTC