------_=_NextPart_000_01BDE597.EE7E33B4
Content-Type: text/plain;
charset="iso-8859-1"
FYI,
I new RFC has now been published for IETF Working Group Guidelines and
Procedures.
Enjoy,
Carl-Uno
-----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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
------_=_NextPart_000_01BDE597.EE7E33B4
Content-Type: message/rfc822
Content-Location: ATT-0-A886DCF5EC50D211A2BF00805F15CE85
To:
Subject:
Date: Mon, 21 Sep 1998 12:29:59 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: multipart/mixed;
boundary="----_=_NextPart_002_01BDE597.EE7E33B4"
------_=_NextPart_002_01BDE597.EE7E33B4
Content-Type: text/plain
------_=_NextPart_002_01BDE597.EE7E33B4
Content-Type: application/octet-stream;
name="ATT98736.txt"
Content-Disposition: attachment;
filename="ATT98736.txt"
Content-Location: ATT-0-A686DCF5EC50D211A2BF00805F15CE85-A
TT98736.txt
Content-type: message/external-body;
access-type="mail-server";
server="RFC-INFO@RFC-EDITOR.ORG"
Content-Type: text/plain
Content-ID: <980921104745.RFC@RFC-EDITOR.ORG>
RETRIEVE: rfc
DOC-ID: rfc2418
------_=_NextPart_002_01BDE597.EE7E33B4
Content-Type: message/external-body;
site="in-notes";
dir="rfc2418.txt";
mode="ftp.isi.edu";
access-type="anon-ftp"
Content-Location: ATT-1-A786DCF5EC50D211A2BF00805F15CE85-r
fc2418.url
------_=_NextPart_002_01BDE597.EE7E33B4--
------_=_NextPart_000_01BDE597.EE7E33B4--