RFC1640 on POISED WG Report

"Joyce K. Reynolds" <jkrey@isi.edu> Thu, 09 June 1994 21:35 UTC

Message-Id: <199406092132.AA26219@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1640 on POISED WG Report
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 09 Jun 1994 14:33:05 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1640:

        Title:      The Process for Organization of Internet Standards
                    Working Group (POISED)
        Author:     S. Crocker
        Mailbox:    crocker@TIS.COM
        Pages:      10
        Characters: 21,780
        Update/Obsoletes:  none


This report, originally prepared in January 1993 provides a summary of
the POISED WG, starting from the events leading to the formation of
the WG to the end of 1992.  Necessarily, this synopsis represents my
own perception, particularly for the "prehistory" period.  Quite a few
people hold strong views about both the overall sequence and specific
events.  My intent here is to convey as neutral a point of view as
possible.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-REQUEST@NIC.DDN.MIL.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
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.

ftp://ds.internic.net/rfc/rfc1640.txt"><ftp://ds.internic.net/rfc/rfc1640.txt>

RFC1640 on POISED WG Report Joyce K. Reynolds