routing registry

 Daniel Karrenberg <Daniel.Karrenberg at ripe.net> writes:
  * 
  *   > dsj at merit.edu writes:
  *   > > As a side note, it would probably be beneficial to set up some sort o
  * f
  *   > > mail group for this sort of discussion.  It might only have a lifetim
  * e
  *   > > of a few weeks but who knows.
  * 
  * <rr-impl at ripe.net> has been created. 
  * 
  * I'll give a few quick answers.  Tony and Marten will fill in the gaps,
  * I'm sure. 
  *
Trying now ;-).
 
  *   > > (0) What checks are performed on the RIPE database.
  *   > >     For example,
  *   > >     (a) Policy conflicts such as AS X is announcing AS A to AS Y, but
  *  AS 
  *   > Y isn't
  *   > >         listening.
As dfk said prcheck does this and is run by the providers. We have
some plans to integrate this into the S/W when the PRIDE routines
and more generalised.

  *   > >     (b) Syntax checking on as-in, as-out and various address fields.
  *
Well actually, there is basic syntax checking which makes sure syntax
is correct but has no real knowledge of the semantics (prcheck has
this) as yet. As I said above it will be integrated in.
 
  * The tool prcheck does this.  At this point we leave it to the users
  * themselves to use the tools. 
  * 
  *   > > (1) How are checks performed on the RIPE database.
  *   > >     For instance, are there scripts which run out of cron to verify p
  * olic
  *   > y
  *   > >     conflicts, etc.
  * 
  * We do some regular checks on the database and store the results for
  * pickup with FTP.  Some of this is just syntax and not done too
  * regularly. 
  * 
  * We daily compare policy information with what we see in well connected
  * routers and flag the difference.  See ftp.ripe.net:ripe/as.  The
  * conflict output is sent to operational mailing lists once a week. 
  *
There is also a job which fully syntax checks the database and this is
mailed from time to time. The problem is in the old (totally
different) S/W we had a looser syntax check and some errors creeped in
before the new S/W.
 
  *   > > (2) What happens as a result of these checks?
  *   > >     For instance, if a problem is found with some "as-in" field, is e
  * mail
  *   > >     sent automically to someone?  And if so, to whom?
  * 
  * Not at this point. 
  *
Nope - awaits the integration of prcheck type routines into DB update
S/W.
 
  *   > > (3) What happens if I register a net twice?
  * 
  * The the present entry gets overwritten. 
  *
Yes - providing the changed field is newer.
 
  *   > > (4) Can we really send (on a short-term basis) _all_ our registration
  *  dat
  *   > a?
  *   > >     Will we break anything?
  * 
  * Not to our knowledge.  We will store the info with a separate source ID.
  * This will require some changes to the tools.  No big deal though. 
  *
It definately shouldn't. It is just a question of indexing a new
sourced database and away we go.
 
  *   > > (5) How does one go about unregistering a net from the RIPE db?  Just
  *  vi
  *   > >     the file from within my guardian account?
  * 
  * The network entry can be deleted by sending in an update with a pseudo
  * attribute "delete:". 
  * 
  * A net can be removed from a group (AS, community) by removing it from
  * the guardian file. 
  * 
  *   > > (6) What is the process for handing out new accounts?  How does a new
  *  net
  *   > work
  *   > >     service provider get an account on ftp.ripe.net to register his/h
  * er d
  *   > ata?
  * 
  * By sending a mail message to us at ncc at ripe.net. 
  * 
  *   > > (7) Is the only RIPE db input method by logging in and vi'ing some fi
  * les?
  *   > >     In other words, there doesn't exist an email interface, etc.
  * 
  * Updates and new entries can be sent by mail to <auto-dbm at ripe.net>. 
  * They will get processed automatically.  We process around 15k a month. 
  * Guarded *objects* and requests with user questions can be sent to
  * <ripe-dbm at ripe.net> and be processed manually (about 60/month). 
  * 
  *   > >     I remember hearing something about fax and phone in orders.  Does
  *  thi
  *   > s
  *   > >     really occur and if so, how often?
  * 
  * Thnakfully only for the Internet registry (address allocation) end of
  * the business. 
  * 
  * Daniel
  * 
  * 

-Tony.



-------- Logged at  Wed Feb 16 00:08:36 MET 1994  ---------