I am back. Here yet another document on how to write IETF standrads.
Carl-Uno
--->To: IETF-Announce:; >Cc: stdguide@midnight.com >From: Internet-Drafts@ietf.org >Reply-to: Internet-Drafts@ietf.org >Subject: I-D ACTION:draft-ietf-stdguide-ops-07.txt >Date: Thu, 21 May 1998 06:41:04 PDT >Sender: cclark@CNRI.Reston.VA.US > >A New Internet-Draft is available from the on-line Internet-Drafts directories. >This draft is a work item of the Guide for Internet Standards Writers Working Group >of the IETF. > > Title : Guide for Internet Standards Writers > Author(s) : G. Scott > Filename : draft-ietf-stdguide-ops-07.txt > Pages : 20 > Date : 20-May-98 > > This document is a guide for Internet standard writers. It defines > those characteristics that make standards coherent, unambiguous, and > easy to interpret. In addition, it singles out usage believed to > have led to unclear specifications, resulting in non-interoperable > interpretations in the past. These guidelines are to be used with > RFC 2223, 'Instructions to RFC Authors.' > > This version of the document is a draft. > >Internet-Drafts are available by anonymous FTP. Login with the username >"anonymous" and a password of your e-mail address. After logging in, >type "cd internet-drafts" and then > "get draft-ietf-stdguide-ops-07.txt". >A URL for the Internet-Draft is: >ftp://ftp.ietf.org/internet-drafts/draft-ietf-stdguide-ops-07.txt > >Internet-Drafts directories are located at: > > Africa: ftp.is.co.za > > Europe: ftp.nordu.net > ftp.nis.garr.it > > Pacific Rim: munnari.oz.au > > US East Coast: ftp.ietf.org > > US West Coast: ftp.isi.edu > >Internet-Drafts are also available by mail. > >Send a message to: mailserv@ietf.org. In the body type: > "FILE /internet-drafts/draft-ietf-stdguide-ops-07.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. >Content-Type: text/plain >Content-ID: <19980520154740.I-D@ietf.org> > >ENCODING mime >FILE /internet-drafts/draft-ietf-stdguide-ops-07.txt > ><ftp://ftp.ietf.org/internet-drafts/draft-ietf-stdguide-ops-07.txt> > Carl-Uno Manros Principal Engineer - Advanced Printing Standards - Xerox Corporation 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231 Phone +1-310-333 8273, Fax +1-310-333 5514 Email: manros@cp10.es.xerox.com