Here's the proposed taxonomy addition that I'll be pitching in PSARC
next week.   I will keep you informed on their decision.

Thanks very much for your help in making "the right thing" happen.
This is to remove RFS from the s1093 release, so that
the months of effort we've put into this won't be wasted.

My plan is as follows:
  1/ describe my plan to Susanna P for agreement [DONE]
  2/ mention my plan on the EOL alias, for comment  [DONE]
  3/ present the taxonomy addition to PSARC next week, and get their approval
  4/ get PSARC's agreement that RFS falls into the newly-created category
4.5  Ensure SAC gets to hear
  5/ remove it from the source base
  6/ Use the time between then and 10/93 to complete the EOL plan.

   Peter

-------------------------------------------
Proposed addition to the Taxonomy document--

Obsolete
        Specification:		None
	Incompatible Change:	Minor release (.X.0)
	Examples:		RFS

	An interface no longer in general use.  An existing interface
	may be downgraded from some other status (such as Public or
	Standard) to Obsolete either through documented disuse or a
	standard proactive program to communicate the change in commitment
	to customers.

	A guideline for "general use" is usage by more than 5% of the
	customers who have access to a product containing the interface
	in question.

	Disuse (customer disinterest) should be demonstrated through
	a credible survey or other method of determining the use of a
	facility by customers.  

	The standard program to communicate a change in commitment
	requires:

	      -	Demonstration of support by the Steering Committee
		responsible for the deliverable(s) containing the
		interface.  Such support can be demonstrated by a
		change to strategy document or resolutions taken in
		meetings and documented in the minutes.

	      -	One year's notice to the customer base of the intended
		obsolescence of the interface.  The year must elapse
		prior to the delivery of a product that contains a
		change incompatible with the present status of the
		interface.

		Acceptable notice includes letters to customers on 
		support contracts, notices in product release notes
		or documentation, or announcements through various forums.

	Proposals to downgrade an interface through this mechanism should
	be brought to an ARC at the start of the year's notice (to ensure
	that no further commitments against the interface are created.)