DataMuseum.dk

top - metrics - download

    Length: 3414 (0xd56)
    Types: TextFile
    Names: »AUTHOR-INSTRUCT.TXT.2«

└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦this⟧ »EurOpenD3/documents/nic.ddn.mil/rfc/AUTHOR-INSTRUCT.TXT.2« 

TextFile

[ RFC:AUTHOR-INSTRUCT.TXT ]				[ FP, 11/86 ]


                   INSTRUCTIONS FOR AUTHORS OF RFCs


RFCs are distributed online by being stored as public access files, and 
a short messages is sent to the distribution list indicating the 
availability of the memo.

The online files are copied by the interested people and printed or 
displayed at their site on their equipment.  This means that the format 
of the online files must meet the constraints of a wide variety of 
printing and display equipment.

To meet these constraints the following rules are established for the 
format of RFCs:

   The character codes are ASCII.

   Each page must be limited to 58 lines followed by a form feed on a 
   line by itself.

   Each line must be limited to 72 characters followed by carriage 
   return and line feed.

   No overstriking (or underlining) is allowed.

   These "height" and "width" constraints include any headers, footers, 
   page numbers, or left side indenting.

Each RFC is to include on its title page or in the first or second 
paragraph a statement (titled "Status of this Memo") describing the 
intention of the RFC.  There are several reasons for publishing a memo 
as an RFC, for example, to make available some information for 
interested people, or to begin or continue a discussion of an 
interesting idea, or to make available the specification of a protocol.

   The following sample paragraphs may be used to satisfy this 
   requirement:

      Specification

         This RFC specifies a standard for the DARPA Internet community.
         Hosts on the ARPA-Internet are expected to adopt and implement 
         this standard.

      Discussion

         The purpose of this RFC is to focus discussion on particular 
         problems in the ARPA-Internet and possible methods of solution.
         No proposed solutions this document are intended as standards 
         for the ARPA-Internet.  Rather, it is hoped that a general 
         consensus will emerge as to the appropriate solution to such 
         problems, leading eventually to the adoption of standards.

      Information

         This RFC is being distributed to members of the ARPA-Internet 
         community in order to solicit their reactions to the proposals 
         contained in it.  While the issues discussed may not be 
         directly relevant to the research problems of the 
         ARPA-Internet, they may be interesting to a number of 
         researchers and implementers.

      Status

         In response to the need for maintenance of current information 
         about the status and progress of various projects in the 
         ARPA-Internet community, this RFC is issued for the benefit of 
         community members.  The information contained in this document 
         is accurate as of the date of publication, but is subject to 
         change.  Subsequent RFCs will reflect such changes.

   Of course these paragraphs need not be followed word for word, but 
   the general intent of the RFC must be made clear.

Each RFC is to also include a "distribution statement".  In general RFCs
have unlimited distribution.  There may be a few cases in which it is 
appropriate to restrict the distribution in some way.

Typically the distribution statement will simply be the sentence 
"Distribution of this memo is unlimited." appended to the "status of 
this memo" section.