Date: Fri, 02 Feb 96 16:48:00 PST
To:  RAIL Workgroup
Fr:  Donald Telian, Intel
Dt:  2/2/96
Re:  Process for changing the RAIL spec

Now that we've established a 1.0 spec, we need a process for spec changes.  (I 
was asked for this at the IBIS face-to-face).  I've selected a process similar 
to the IBIS "BIRDs", but feel we should use another name to eliminate confusion 
with IBIS Open Forum issues.  So, how about...

RAIL ROAD, or
RAIL Revision Or Appendage Document

This process is intended to be used only for issues that would alter the 
RAIL Specification (for example, anything going into 2.0 will use this process).
General discussion topics will still be entertained on the reflector without
this level of rigor.

The general format of a ROAD follows below:


NOTE:  All text in french brackets is for explanation only and should be 
deleted/replaced by your text.
----------------------------   cut here    -----------------------------------

                    RAIL Revision Or Apendage Document  (ROAD)


ROAD ID#:      {don't fill in, will be filled in later for tracking}
ISSUE TITLE:   {one line description of your issue}
REQUESTOR:     {your name and company}

DATE SUBMITTED:                       {date you sent to reflector}
DATE ACCEPTED BY RAIL WORKGROUP:      {will be filled in when accepted}

*******************************************************************************
*******************************************************************************

STATEMENT OF THE ISSUE:

      {Place a short description of your issue here.  People should be able
       tell by reading this if they care about this in less than 1 minute.}

*******************************************************************************

STATEMENT OF THE RESOLVED SPECIFICATIONS:

      {For new keywords, write the text EXACTLY AS IT SHOULD APPEAR in a 
       future RAIL specification.  If this is a change, state the old text
       and the new text again EXACTLY AS IT SHOULD APPEAR.  Be sure to give
       intended location in the specification.}

*******************************************************************************

ANALYSIS PATH/DATA THAT LED TO SPECIFICATION:

      {There are many "experts" reviewing this document.  Your reasons,analysis,
       and justifications must be precise and well documented, or your ROAD will
       be sent back to you.  Use this section to show that you've done your 
       homework, and answer all questions that will undoubtedly be asked.  If
       your issue is a change instead of an enhancement, document how backward 
       compatibility is to be addressed.}

*******************************************************************************

ANY OTHER BACKGROUND INFORMATION:

      {These documents will be archived, so use this section to carry any detail
       that is not essential to the previous section, but should not be lost.}


*******************************************************************************