Internet DRAFT - draft-ietf-poised95-std-proc

draft-ietf-poised95-std-proc-3

Last Version:	draft-ietf-poised95-std-proc-3-06.txt
Date:	`09-Apr-2002`
Disposition:	RFC2026 (diff)
Previous Versions:	draft-ietf-poised95-std-proc-3-05.txt (diff) `- 10-Apr-2002` draft-ietf-poised95-std-proc-3-04.txt (diff) `- 10-Apr-2002` draft-ietf-poised95-std-proc-3-03.txt (diff) `- 10-Apr-2002` draft-ietf-poised95-std-proc-3-02.txt (diff) `- 10-Apr-2002` draft-ietf-poised95-std-proc-3-01.txt (diff) `- 10-Apr-2002` draft-ietf-poised95-std-proc-3-00.txt (diff) `- 10-Apr-2002`


        BCP 9:
        RFC 2026:

        Title:      The Internet Standards Process -- Revision 3
        Author:     S. Bradner
        Date:       October 1996
        Mailbox:    sob@harvard.edu
        Pages:      36
        Characters: 86,731
        Updates/Obsoletes:  1602

        URL:        ftp://ds.internic.net/rfc/rfc2026.txt


This memo documents the process used by the Internet community for the
standardization of protocols and procedures.  It defines the stages in
the standardization process, the requirements for moving a document
between stages and the types of documents used during this process.
It also addresses the intellectual property rights and copyright
issues associated with the standards process. This RFC is a product of
the Process for the Organization of Internet Standards '95 (Poised95)
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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should be sent
to RFC-DIST-REQUEST@ISI.EDU.

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 and Mary Kennedy
USC/Information Sciences Institute