RFC 3285 on Using Microsoft Word to create Internet Drafts and RFCs

RFC Editor <rfc-ed@ISI.EDU> Thu, 30 May 2002 23:29 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22126; Thu, 30 May 2002 19:29:54 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA11074 for ietf-123-outbound.10@ietf.org; Thu, 30 May 2002 19:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA10975 for <all-ietf@loki.ietf.org>; Thu, 30 May 2002 19:12:27 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21842 for <all-ietf@ietf.org>; Thu, 30 May 2002 19:12:01 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g4UNCQE08914; Thu, 30 May 2002 16:12:26 -0700 (PDT)
Message-Id: <200205302312.g4UNCQE08914@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3285 on Using Microsoft Word to create Internet Drafts and RFCs
Cc: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 30 May 2002 16:12:25 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 3285

        Title:	    Using Microsoft Word to create Internet Drafts and
                    RFCs
        Author(s):  M. Gahrns, T. Hain
        Status:	    Informational
	Date:       May 2002
        Mailbox:    mikega@microsoft.com, ahain@cisco.com
        Pages:      19
        Characters: 34556
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-hain-msword-template-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3285.txt


This document describes the steps to configure the Microsoft Word
application to produce documents in Internet Draft and RFC format.

This memo provides information for the Internet community.  It 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@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 Sandy Ginoza
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://ftp.isi.edu/in-notes/rfc3285.txt"><ftp://ftp.isi.edu/in-notes/rfc3285.txt>