Beta Testers Sought: New Update Scripts for RIPE Database

[Daniel Karrenberg <]

:-):-):-):-) WARNING: Highly Technical Stuff Below ! :-):-):-):-)


Hi Folks,

at long last the NCC have completed their latest programming job: 
the new update and consistency check scripts for the RIPE database. 
The update and consistency checking process is now completely controlled 
by a single configuration file. This file is included for your 
information and amusement. The long term plan is to have all the database
software including the whois server controlled by this file.

Operationally this means:

	- the NCC can now accept udpates including the new
	  "routing privilege" and "boundary gateway" objects.

	- it will be much easier to add new objects and attributes
	  to the database in the future

	- consistency checking of updates is much improved

	- local registries can use the scripts to check their own databases
	  (including local extensions) and their updates before sending
	  them to the NCC

	- running the updates at the NCC takes more computer and less 
	  people time (the way it should be)

	- updates will be acknowledged by individual mail messages 
	  containing detailed diagnostics as well as the offending objects


We are using the new software in production since today. In order to improve
the documentation and the usefulness for local registries we are seeking

	Beta Test Sites (local registries preferred)

for a one to three week beta test period. Please react only if you have time
and intention to at least install and try the software.

The config file below should we your appetite.

Daniel

#
# RIPE database update scripts config file
#
#  1.10 92/09/23
#

# the list of valid country names
#
COUNTRY AL al
COUNTRY AT at
COUNTRY BE be
COUNTRY BG bg
COUNTRY CH ch
COUNTRY CS cs
COUNTRY DE de
COUNTRY DK dk
COUNTRY EE ee
COUNTRY ES es
COUNTRY FI fi
COUNTRY FR fr
COUNTRY GB gb
COUNTRY GR gr
COUNTRY HR hr
COUNTRY HU hu
COUNTRY IE ie
COUNTRY IL il
COUNTRY IN in
COUNTRY IS is
COUNTRY IT it
COUNTRY LU lu
COUNTRY NL nl
COUNTRY NO no
COUNTRY PL pl
COUNTRY PT pt
COUNTRY RO ro
COUNTRY RU ru
COUNTRY SE se
COUNTRY SG sg
COUNTRY SI si
COUNTRY SU su
COUNTRY TN tn
COUNTRY TR tr
COUNTRY YU yu
COUNTRY	ZA za


# legal source attribute values
#
SOURCE LOCAL
SOURCE NSF
SOURCE SRI
SOURCE RIPE

DEFSRC	RIPE	# default source attribute, added if missing

# legal connect attribute values in alphabetic order
#
CONNECT ALT
CONNECT CIX
CONNECT CNR
CONNECT EASI
CONNECT EU
CONNECT FUNET
CONNECT GARR
CONNECT HEPNET
CONNECT ICS
CONNECT INFN
CONNECT IRIS
CONNECT IUNET
CONNECT JANET
CONNECT LOCAL
CONNECT NIKHEF
CONNECT NLNET
CONNECT NORDU
CONNECT NSF
CONNECT RCCN
CONNECT REDIRIS
CONNECT RENATER
CONNECT RIPE
CONNECT SARA
CONNECT SURF
CONNECT SWIP
CONNECT SWITCH
CONNECT TIP
CONNECT WCW
CONNECT WIN
CONNECT XLINK

# The list of valid attribute names themselves in short and long version
#
ATTR	ac	admin-c
ATTR	ad	address
ATTR	as	aut-sys
ATTR	au	authority
ATTR	bg	bdry-gw
ATTR	bl	bdrygw-l
ATTR	ch	changed
ATTR	co	connect
ATTR	cy	country
ATTR	de	descr
ATTR	di	dom-net
ATTR	dn	domain
ATTR	em	e-mail
ATTR	fx	fax-no
ATTR	gd	guardian
ATTR	gw	gateway
ATTR	in	inetnum
ATTR	lo	location
ATTR	na	netname
ATTR	nh	nic-hd
ATTR	nh	nic-hdl
ATTR	ni	nsf-in
ATTR	no	nsf-out
ATTR	ns	nserver
ATTR	ph	phone
ATTR	pn	person
ATTR	rl	routpr-l
ATTR	rm	remarks
ATTR	rp	rout-pr
ATTR	rz	rev-srv
ATTR	sd	sub-dom
ATTR	so	source
ATTR	tc	tech-c
ATTR	uf	u-from		# internal to update procedures
ATTR	ui	u-msgid		# internal to update procedures
ATTR	ue	*ERROR*		# internal to update procedures
ATTR	uw	WARNING		# internal to update procedures
ATTR	zc	zone-c

# attribute aliases (because they appear so often!)
#
ATTA	ch	change
ATTA	rm	remark


# normalising network names
# 	in case of network name syntax errors, each left column character
#	will be replaced by the right column character and syntax checked
#	again, this solves most frequently occurring problems with netnames
# 
NAMNORM		a	A
NAMNORM		b	B
NAMNORM		c	C
NAMNORM		d	D
NAMNORM		e	E
NAMNORM		f	F
NAMNORM		g	G
NAMNORM		h	H
NAMNORM		i	I
NAMNORM		j	J
NAMNORM		k	K
NAMNORM		l	L
NAMNORM		m	M
NAMNORM		n	N
NAMNORM		o	O
NAMNORM		p	P
NAMNORM		q	Q
NAMNORM		r	R
NAMNORM		s	S
NAMNORM		t	T
NAMNORM		u	U
NAMNORM		v	V
NAMNORM		w	W
NAMNORM		x	X
NAMNORM		y	Y
NAMNORM		z	Z
NAMNORM		.	-
NAMNORM		_	-

# The database objects in terms of their attributes
#
# MAND  - these attributes are mandatory
# OPT   - these attributes are optional
# MULT	- these attributes can appear more than once per object
# SORTP	- sort order, single digit, lowest sorted first, 
#         in=0 is always sorted behind all others in internet number order
#

#	boundary gateways
#
OBJ	bg	MAND	ac au bg ch de gd lo so tc
OBJ	bg	OPT	
OBJ	bg	MULT	ac de lo tc ch
OBJ	bg	SORT	1

#	domains
#
OBJ	dn	MAND	ac ch de dn ns sd so tc zc 
OBJ	dn	OPT	di rm
OBJ	dn	MULT	ac ch de di ns rm sd tc zc 
OBJ	dn	SORT	4

#	networks
#
OBJ	in	MAND	ac co cy de in na so tc 
OBJ	in	OPT	as bl ch gw ni no rl rm rz 
OBJ	in	MULT	ac ch de rm rz tc 
OBJ	in	SORT	0

#	persons
#
OBJ	pn	MAND	ad ch ph pn so
OBJ	pn	OPT	em fx nh rm
OBJ	pn	MULT	ad ch em fx ph rm 
OBJ	pn	SORT	3

#	routing privileges
#
OBJ	rp	MAND	ac au ch de gd rp so
OBJ	rp	OPT	tc
OBJ	rp	MULT	ac de tc ch
OBJ	rp	SORT	2

#	Error messages
#	You can change the texts all you like, but do not change the
#       number of arguments!
#
MSG	blladd	*uw: missing blank line (object separator) added below
MSG	brdygw	*uw: boundary gateway, check!
MSG	chgadd	*uw: changed attribute missing, added 
MSG	chgfmt	*ue: illegal change date format "%s"
MSG	conunk	*uw: illegal connectivity attribute value "%s"
MSG	ctyunk  *ue: country code "%s" unknown
MSG	dshadd  *uw: bad range syntax, "-" added
MSG	dupatt	*ue: only one "%s" attribute allowed per object
MSG	dupent  *ue: duplicate entry above ?
MSG	invatt	*uw: invalid attribute in %s object "%s"
MSG	manatt	*uw: mandatory attribute "%s" missing in object
MSG	msgidp	ID: %s        
MSG	namchg	*uw: illegal network name "%s" changed to "%s"
MSG	namchr	*ue: illegal network name "%s"
MSG	namsyn	*ue: netname syntax error "%s"
MSG	netfmt  *ue: bad network number format "%s"
MSG	nethst  *ue: host or subnet part in network number "%s"
MSG	netnul  *ue: bad network number format "00" in "%s"
MSG	netsyn	*ue: inetnum attribute syntax error
MSG	oldupd	*ue: update is older than the current object in database
MSG	routpr	*uw: routing privilege, check!
MSG	souadd	*uw: source attribute "%s" added
MSG	soudef	*uw: source attribute value is "%s" should be "%s"?
MSG	souunk	*ue: source attribute value "%s" unknown
MSG	unkatt	*uw: unknown attribute ignored "%s"
MSG	unkobj	*ue: unknown object type in "%s"

# The command used to send the acknowledgement messages
#
MAILCMD rsh ncc.ripe.net /usr/lib/sendmail -t -v

# The fixed part of the header of an acknowledgement message
#
MHEADER	From: RIPE Database Update Service ripe-dbm@localhost
MHEADER	Subject: Acknowledgement of Your Update Request
MHEADER	Reply-To: ripe-dbm@localhost

# The standard body of an acknowledgement message
#
MAILMSG	This is to acknowledge processing of your RIPE database 
MAILMSG update request(s) which we received with the message IDs
MAILMSG listed below:

# Printed if no update from this source had either error or warning
# Champagne!
#
CONGRAT No errors were found in your update(s). Congratulations !!!

# Printed if errors or warnings found
# No champagne.
#
ERRBLRP	All objects returned to you above generated one or more diagnostic
ERRBLRP	messages.  Please re-submit corrected entries for these objects. 
ERRBLRP	Objects which caused *only* warning messages have been included in the
ERRBLRP	update run.  If an object caused one error message it has
ERRBLRP	*not* been included in the update run.

# Our signature
#
MAILGRT	Sincerely yours
MAILGRT				The RIPE Database Update Service

# File names used in update procedure


INMAILS /dbase/update/mails.in		# the concatenated update messages
CURDB   /dbase/ripe/ripe.db		# the current database (to be updated)
NEWDB	/dbase/ripe/ripe.db		# the new database (after the update)
STATS	/usr/spool/log/dbase		# the stats file (is appended)

ENDCONF		# do not remove!