Dear Richard, a good idea, but wrong proposal format. Let's ask the Board to do such reports. -- Sergey Friday, March 15, 2013, 8:13:51 PM, you wrote: RH> Dear all, RH> this is the fifth suggestion: RH> RIPE will create a yearly list of all services it provides to RH> members or the general public RH> This list will include at least: RH> * Name of the service RH> * Cost in time and money of maintaining and possibly extending this service RH> * Cost in time and money of maintaining the backend needed for this RH> service; this is to catch stuff that relies on old and brittle infra RH> * Number of users if applicable/traceable per year RH> * Number of queries/transactions if applicable/traceable per year RH> * General usefulness of the service from RIPE's POV RH> * Status of service, such as "active, supported", "deprecated", or RH> "scheduled for decommissioning on YYYY-MM-DD" RH> * A suggestion for the future status of the service RH> If in doubt, RIPE will focus less on detailed interpretation and RH> analysis and more on giving out as many hard facts and stats as RH> possible. Interpretation will happen on the mailing lists anyway. RH> RIPE will implement this policy in a light-weight manner that is not RH> a drain on resources in and as of itself.