Minimal Instructions for Using the RFC Skeleton 

** NOTE: For instructions governing IGES Configuration Management
** please refer to "Operating Procedures and Life Cycle
** Documentation for the Initial Graphics Exchange Specification"
**

RFC Header information

These notes were formerly comments in the RFC Skeleton LaTeX file: 

%  Place entries inside of "{}" on lines indicated by "%% < comment>" 
%   For example... 
% 
% {666}   %% < RFC number>
% {B}    %% < RFC revision>
% 
% \RFCheader 
% 
% {April 2, 1988} %% < Revision date> 
% {UNITS CONSTANT GLOBAL}  %% < Title>
% {April 1, 1988} %% < Date of receipt>
% {Drafting}  %% < Custodian TC>
% {No}    %% < Gray page testing ("Yes" or "No")>
% 
% \RFCname
% {Dennette A. Harrod, Jr} %% < Author>
% {{\sc Wiz Worx}\\  %% < Company>
% 60 Thoreau Street, Suite 320\\ %% < Address (first line)>
% Concord, MA 01742}  %% < Address (second line)>
% {1-800-232-9679}  %% < Phone>
% {}    %% < FAX>
% {76234.510@compuserve.com} %% < E-Mail>
% 
%   Note that leading spaces and blank lines can have an effect on the
%   output. Do not remove blank lines.
%   Do not put leading spaces inside a "{}"
%

Problem and Solution Sections

Follow the usual TeX rules for these two sections. The RFC may be printed and circulated within committee at this stage.

Logging and Initial Distribution

As noted in the Skeleton comments, send the ready-for-distribution RFC LaTeX file to the Configuration Control Secretary:

parks@eeel.nist.gov 

or mail on floppy disk to:

     Curtis Parks
     NIST
     Bldg 225, Rm. A-053
     Gaithersburg, MD 20899
Enter the assigned RFC Number into the RFC header information, then e-mail the file to: 

iges@eeel.nist.gov
Or make arrangements with the secretary for the e-mail distribution following the assignment of the RFC Number. The file, at this point, should be labeled RFCxxx.TEX. The e-mail "subject" line also contains this label.

Integration

During an IPO meeting, or by request to the IGES Editor, the author must obtain the LaTeX files related to the RFC solution's location in the IGES document. Edit the appropriate changes into the file's text, marking each modified text/paragraph with a \CB{RFCxxx} just following the first change to the wording.

Attach the new document file text to the RFC. Delete the %ed lines (comments) in each of the lines of the skeleton file which create the "NOTE about entities numbers and form numbers being temporary...". LaTex-process your file to obtain a printed copy for distribution.

When the integrated RFC produces correct document text, check to make sure that the Solution Section of the RFC adequately describes the way the marked document was modified.

E-mail the file as above. The file (and the e-mail "Subject line) should be labeled SOLxxx.TEX.

Follow-Up

As author, you are initiating a series of steps and involving many people in the IGES/PDES Organization. Your integrated RFC must be approved for ballot, balloted, comments resolved, and approved for ECO status. The Editor then incorporates your integrated LaTeX files into the master document files. Throughout this process, your involvement will be required to keep the RFC moving.
From the IGES Project, "We'll help you all we can."

Curt (parks@eeel.nist.gov)