DB consistancy checking tools

  With reference to:

>From: stephenb at uk.uu.net
>Date: Tue, 11 Jan 2000 11:49:34 +0000 (GMT)
>Subject: DB consistancy checking tools
>To: lir-wg at ripe.net
>
>Hi
>	After making a number of NEWBLOCK requests and recieving the
>	information back of the errors in the DB for the previous block,
>	i would like to make the suggestion to the RIPE NCC the we are
>	allowed accuess to this most useful tool. This way we could do
>	the consitancy checks and get our house in order before making
>	the NEWBLOCK request, lessening the load on RIPE and speeding
>	up the allocation of more CIDR.
>
>If there is enough interest can we add this as a point of discussion at
>the LIR working group, or should it be in the DB group.
>
>BTW i do like the new web site.
>
>Regards,
>-- 
>----------------------------------
>E-Mail: stephenb at uk.uu.net 
>Phone: +44 (0)1223 581051

  I've got one tech Q and one org Q:
  
  Tech: Would you want to propose a "public release" of the tool (e.g. to
        be able to deploy it in a local environment), or would it be
	useful / sufficient to be able to trigger the tool (for a given
	address range) and to have access to the result?
	I'm aware of the fact that there might be access and/or security
	related issues requiring a solution, but we might be able to solve
	that as soon as we know what to look for....
	
  Org.: Where is this to go? LIR or DB? Preferences?
        ( In general I prefer a path where the goals and application
	  requirements emerge from an "application WG" and the
	  implementation is then passed on to the DB-WG. )
	  
  Wilfried.