Week 1 Status Report

"Dale S. Johnson" <dsj at merit.edu> writes
 * ter
 * > interfaces on his net belonging to other ASes. This is a special case
 * > and away from the one net / one AS idea we have. This is not guarded 
> but should be used wherever possible.
 * 
 * Yes, we've looked at this here.  Is there a particular action item for
 * Merit, other than encouraging anyone who uses our copy of the database to
 * fill them in?  (Since we're using your software almost unmodified, we
 * automatically get this stuff for free, right?  Or do we need to add in
 * some code not yet in the beta release that we've picked up?)

No it is in the standard code for the db and the tools. Just to make
sure, below is the production configuration we are using, it has
community and some other things in there (clns object).

-Marten

#############################################################################
# 
# This is the RIPE database software main configuration file.
# Almost all tools that manage the databases use some parts of this
# config file, most of them do not use everything.
#
#############################################################################
# 
# Alter the pathnames below for your local environment
#
#############################################################################

# Run database sw in test mode?  Testmode will cause ALL mail acks and other
# mail messages to be send to DEFMAIL defined further below.

TESTMODE	0

# file to keep people that can make entries using the update daemon
# not in distribution yet.

# AUTHFILE	/nccfs3/dbase-beta/conf.auth

# help file for "whois help"

HELP	/nccfs3/dbase/etc/db-help

# default database to do lookups in

DEFLOOK	RIPE

# if all databases are selected

ALLLOOK	RIPE NIC MERIT NCC-AS-LIST ALTERNET

# Filenames associated with sources, more than one source can point to a file
# Make sure that all the databases you define below are available ...

DBFILE	RIPE	/nccfs3/dbase/data/ripe.db
DBFILE	MERIT	/nccfs3/dbase/data/nsf.db
DBFILE	NIC	/nccfs3/dbase/data/nic.db
DBFILE	NCC-AS-LIST	/nccfs3/dbase/data/asn.db
DBFILE	ALTERNET	/nccfs3/dbase/data/alter.db

# What sources can be updated ? Others will generate an error.

CANUPD	RIPE

# whoisd query log file

QRYLOG	/nccfs3/dbase/etc/qrylog/qrylog

# Error log file (if something really goes wrong ...)

ERRLOG	/nccfs3/dbase/etc/errlog

# authorization log (not yet used)
# AUTHLOG	/nccfs3/dbase-beta/etc/authlog

# this is where all update requests will be logged, this SHOULD be a
# directory, logged will be in file YYMMDD with EOF markers between
# messages

UPDLOG	/nccfs3/dbase/etc/updlog

# this is where all acknowledgements will be logged, this SHOULD be a
# directory, logged will be in file YYMMDD with EOF markers between
# messages

ACKLOG	/nccfs3/dbase/etc/acklog

# This is where the whoisd pid goes once started
# (default: /tmp/whoisd.pid)

PIDFILE	/nccfs3/dbase/etc/whoisd.pid

# This is the lock file basename for cleandb, to avoid rename/open race
# condition. The database name is appended to this basename, to create
# sperate lock files for all databases.
# (default: /tmp/CLEANDB.LOCK)

CLEANLOCK	/nccfs3/dbase/CLEANDB.LOCK

# TMPDIR is the tmp directory where various tools keep tmp files.
# (default: /tmp)

TMPDIR	/nccfs3/dbase/tmp

# DEFMAIL is the mailbox used when no mail notifications or acknowledgements
# both as to and from address in various places.

DEFMAIL	ripe-dbm at ripe.net

# What to display if no match was found

NOMATCH	No entries found for the selected source(s).
NOMATCH	
NOMATCH	If you would like to search on arbitrary strings,
NOMATCH	please use the WAIS server on wais.ripe.net or
NOMATCH	telnet to info.ripe.net for a WAIS client interface.
NOMATCH	The WAIS database name is ripe-database.
NOMATCH	This will only work for RIPE data.

# What to display if we got TOOMANY hits back

TOOMANY	The index search returned too many hits.
TOOMANY Please refine your search key.

# The list of valid attribute names themselves in short and long version
#
ATTR	ac	admin-c
ATTR	ad	address
ATTR	ai	as-in
ATTR	al	as-list
ATTR	an	aut-num
ATTR	am	as-macro
ATTR	ao	as-out
ATTR	as	aut-sys
ATTR	au	authority
ATTR	bg	bdry-gw
ATTR	bi	bis
ATTR	bl	bdrygw-l
ATTR	ch	changed
ATTR	cl	comm-list
ATTR	cm	community
ATTR	co	connect
ATTR	cy	country
ATTR	da	dom-name
ATTR	de	descr
ATTR	df	default
ATTR	di	dom-net
ATTR	dm	dom-in
ATTR	dn	domain
ATTR	do	dom-out
ATTR	dp	dom-prefix
ATTR	em	e-mail
ATTR	fx	fax-no
ATTR	gd	guardian
ATTR	gw	gateway
ATTR	ii	ias-int
ATTR	in	inetnum
ATTR	lo	location
ATTR	ma	maintainer
ATTR	na	netname
ATTR	nh	nic-hdl
ATTR	ni	nsf-in
ATTR	no	nsf-out
ATTR	ns	nserver
ATTR	ny	notify
ATTR	op	op-phone
ATTR	of	op-fax
ATTR	om	op-mail
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
#				Attributes with u* short names are special!
ATTR	ua	authorise	# very special
ATTR	ud	delete		# update operation
ATTR	ue	*ERROR*		# internal to update procedures
ATTR	uf	u-from		# internal to update procedures
ATTR	ui	u-msgid		# 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	fx	fax
ATTA	rm	remark
ATTA	ua	authorised
ATTA	ud	deleted

# object alias for template mode
#
ALIAS	in	network
ALIAS	in	netnum

# The database objects in terms of their attributes
#
# ATSQ  - all defined attributes in this object, also defines print order
# MAND  - these attributes are mandatory
# OPT   - these attributes are optional
# MULT	- these attributes can appear more than once per object
# SORT	- sort order, single digit, lowest sorted first
# UNIQ	- these attributes define the unique key
# KEYS	- these attributes define all possible keys
# REC	- these attributes must be looked up if referenced
# GRD	- these attributes are guarded
#

#	autonomous systems
#
OBJ	an	ATSQ	an de ai ao df gd ac tc rm ny ma ch so
OBJ	an	MAND	an de ac tc ch so
OBJ	an	OPT	ai ao df gd rm ny ma
OBJ	an	MULT	de ai ao df ac tc rm ch ny
OBJ	an	SORT	0
OBJ	an	UNIQ	an
OBJ	an	KEYS	an
OBJ	an	REC	ac tc


#	as macros
#
OBJ	am	ATSQ	am de al gd tc ac rm ny ma ch so
OBJ	am	MAND	am de al gd tc ac ch so
OBJ	am	OPT	rm ny ma
OBJ	am	MULT	de al tc ac rm ch ny
OBJ	am	SORT	8
OBJ	am	UNIQ	am
OBJ	am	KEYS	am
OBJ	am	REC	tc ac


#	boundary gateways
#
OBJ	bg	ATSQ	bg de lo au gd ac tc rm ny ma ch so
OBJ	bg	MAND	ac au bg ch de gd lo so tc
OBJ	bg	OPT	ny ma rm
OBJ	bg	MULT	ac de lo tc ch ny
OBJ	bg	SORT	1
OBJ	bg	UNIQ	bg
OBJ	bg	KEYS	bg
OBJ	bg	REC	ac tc

#	community
#
OBJ	cm	ATSQ	cm de au gd tc ac rm ny ma ch so
OBJ	cm	MAND	cm de au gd tc ac ch so
OBJ	cm	OPT	ny ma rm
OBJ	cm	MULT	de tc ac rm ch ny
OBJ	cm	SORT	6
OBJ	cm	UNIQ	cm
OBJ	cm	KEYS	cm
OBJ	cm	REC	ac tc

#	domains
#
OBJ	dn	ATSQ	dn de ac tc zc ns sd di rm ny ma ch so
OBJ	dn	MAND	ac ch de dn so tc zc 
OBJ	dn	OPT	di ns rm sd  ny ma
OBJ	dn	MULT	ac ch de di ns rm sd tc zc ny
OBJ	dn	SORT	4
OBJ	dn	UNIQ	dn
OBJ	dn	KEYS	dn
OBJ	dn	REC	ac tc zc

#	networks
#
OBJ	in	ATSQ	in na de cy ac tc co rl bl as cl ii ni no gw rz rm ny ma ch so
OBJ	in	MAND	ac ch cy de in na so tc
OBJ	in	OPT	as bl cl co ch gw ii ni no rl rm rz ny ma
OBJ	in	MULT	ac ch de ii rm rz tc ny
OBJ	in	SORT	5
OBJ	in	UNIQ	in
OBJ	in	KEYS	in na
OBJ	in	REC	ac tc
OBJ	in	GRD	bl rl as cl

GUARD	bl	/nccfs3/dbase/guarded/bdrygw	MULTIPLE
GUARD	rl	/nccfs3/dbase/guarded/routpr	MULTIPLE
GUARD	cl	/nccfs3/dbase/guarded/community	MULTIPLE
GUARD	as	/nccfs3/dbase/guarded/as	SINGLE

#	persons
#
OBJ	pn	ATSQ	pn ad ph fx em nh rm ny ma ch so
OBJ	pn	MAND	ad ch ph pn so
OBJ	pn	OPT	em fx nh rm ny ma
OBJ	pn	MULT	ad ch em fx ph rm ny
OBJ	pn	SORT	3
OBJ	pn	UNIQ	pn nh
OBJ	pn	KEYS	pn nh

#	routing privileges
#
OBJ	rp	ATSQ	rp de au gd ac tc rm ny ma ch so
OBJ	rp	MAND	ac au ch de gd rp so
OBJ	rp	OPT	tc ny ma
OBJ	rp	MULT	ac de tc ch ny
OBJ	rp	SORT	2
OBJ	rp	UNIQ	rp
OBJ	rp	KEYS	rp
OBJ	rp	REC	ac tc

#	clns object
#
OBJ	dp	ATSQ	dp da de bi dm do df ac tc gd ny ma ch so
OBJ	dp	MAND	dp da ac tc ch so
OBJ	dp	OPT	bi de dm do df gd ny ma
OBJ	dp	MULT	de bi dm do df ac tc ch ny
OBJ	dp	SORT	7
OBJ	dp	UNIQ	dp
OBJ	dp	KEYS	dp da
OBJ	dp	REC	ac tc

# MAILCMD is the command into which a composed e-mail is given as standard
# input, to be send as mail. The message piped into this command has ALL
# the necessary mail header to process the mail:
# From:
# To:
# Subject:
# The mail command should take the recipients from the actual message.
# Using sendmail it will be executed as: /usr/lib/sendmail -t < "messagefile"
# (default: /usr/lib/sendmail -t)

MAILCMD /usr/lib/sendmail -t

# The MAILTXT is the text that comes right after the headers in an email ack
# send by "dbupdate" when processing an email update (-M flag).
# In this text you can use 4 variables that will be expanded to the real
# values in the ack:
#
# $FROM		= "Reply-To:" or "From:" address in mail being processed
# $SUBJECT	= "Subject:" field                   ,,          ,,
# $MDATE	= "Date:" field	                     ,,          ,,
# $MSGID	= "Msg-Id:" field                    ,,          ,,

MAILTXT	
MAILTXT	Your e-mail:
MAILTXT
MAILTXT >   From:    $FROM
MAILTXT >   Subject: $SUBJECT
MAILTXT	>   Date:    $MDATE
MAILTXT	>   Msg-Id:  $MSGID
MAILTXT
MAILTXT has been processed by the automatic update procedure at the RIPE NCC.
MAILTXT Diagnostic output follows:
MAILTXT
MAILTXT ------------------------------------------------------------------------

# MHEADER The complete mailheader for the ack mail, you can include any
# mail header field, EXCEPT for the "To:" field which is added inside the
# ack sending program. Again you can use the 4 variables as specified in
# MAILTXT

MHEADER	From: RIPE Database Management <ripe-dbm at ripe.net>
MHEADER	Subject: Re: $SUBJECT
MHEADER Reply-To: ripe-dbm at ripe.net

# ACKERR is the message that will be displayed when errors or warnings were
# found in an update.

ACKERR
ACKERR Objects that just generated a WARNING have been updated as shown.
ACKERR
ACKERR Objects that generated an *ERROR* have NOT been updated as requested.
ACKERR Please re-submit corrected objects.

# ACKOK is message displayed when no error/warnings were found in an update

ACKOK	
ACKOK	No error/warnings were found in your database update.  Congratulations.

# Signature on the acknowledgement

ACKSIG ------------------------------------------------------------------------
ACKSIG
ACKSIG This acknowledgement was sent to you by the new RIPE database software.
ACKSIG
ACKSIG Please use 
ACKSIG
ACKSIG     <auto-dbm at ripe.net>     instead of  <ripe-dbm at ripe.net>   and
ACKSIG     <auto-assign at ripe.net>  instead of  <assign at ripe.net> 
ACKSIG
ACKSIG for fast turnaround times on all but guarded objects.
ACKSIG
ACKSIG If you have any question about an error or warning message, please
ACKSIG contact <ripe-dbm at ripe.net>.
ACKSIG
ACKSIG Sincerely Yours, 
ACKSIG
ACKSIG RIPE Database Maintenance Department (Automatic Section)

# NOTITXT Notification text used in notification messages.
# Same variables as in MAILTXT can be used here.

NOTITXT Dear Colleague,
NOTITXT
NOTITXT This is to notify you that some objects in which you are mentioned as
NOTITXT a notifier or guardian of one of the guarded attributes in this object
NOTITXT have been modified. The objects below are the NEW entries for these
NOTITXT objects in the database. In case of DELETIONS, the deleted object is
NOTITXT displayed. NOOPs will not be reported.
NOTITXT
NOTITXT The update causing these changes had the following mail headers:
NOTITXT
NOTITXT - From:    $FROM
NOTITXT - Subject: $SUBJECT
NOTITXT - Date:    $MDATE
NOTITXT - Msg-Id:  $MSGID
NOTITXT
NOTITXT RIPE Database Notification Department

# NHEADER The Header used for notification messages

NHEADER From: RIPE Database Notifications <ripe-dbm at ripe.net>
NHEADER Subject: Notification of RIPE Database changes
NHEADER Reply-To: ripe-dbm at ripe.net

# GRDCONFLICT - Text including header to be used in case of guardian
# conflicts. To field simply defaults to "guardian". It must be a
# local account/alias to mail to.

GRDCONFLICT From: RIPE Database Conflict Handler <ripe-dbm at ripe.net>
GRDCONFLICT Subject: Guarded attributes conflicts found
GRDCONFLICT 
GRDCONFLICT Dear Guardian,
GRDCONFLICT 
GRDCONFLICT One or more conflicts have been found regarding guarded
GRDCONFLICT attributes in the RIPE database. Some of the conflicts
GRDCONFLICT concern the guarded values you are a guardian for.
GRDCONFLICT 
GRDCONFLICT Please verify and correct the conflicts below.
GRDCONFLICT The guarded values for objects below have been set to
GRDCONFLICT the value they had in the database before this guarded
GRDCONFLICT attributes run.
GRDCONFLICT 
GRDCONFLICT Kind Regards,
GRDCONFLICT RIPE Database Conflict Department
GRDCONFLICT ------

# SPLITMSG - Message (including header) to be send when a block of
# network numbers has been split due to guarded attribute addition.
# The To field is always the email address that last changed the
# network block. Some variables to be used here as well:
# $BEGINADDRESS - first address of the block that was split
# $ENDADDRESS   - last address of the block that was split

SPLITMSG From: RIPE Database Management <ripe-dbm at ripe.net>
SPLITMSG Subject: $BEGINADDRESS - $ENDADDRESS has been split
SPLITMSG 
SPLITMSG 
SPLITMSG Dear last changer of the RIPE database entry
SPLITMSG $BEGINADDRESS - $ENDADDRESS,
SPLITMSG 
SPLITMSG This is to notify that network block $BEGINADDRESS - $ENDADDRESS
SPLITMSG has been split due to the addition of guarded attributes. It has
SPLITMSG been split into the objects displayed below in the RIPE database.
SPLITMSG 
SPLITMSG Please update your local information accordingly,
SPLITMSG 
SPLITMSG RIPE Database Maintenance Department

# COPYRIGHT message that goes on top of every newly generated, or cleaned
# database, will be output with "#" before each line.

RIGHTS Copyright (c)1992/1993 by Daniel Karrenberg and the RARE Association
RIGHTS
RIGHTS Restricted rights.
RIGHTS
RIGHTS Except for agreed Internet operational purposes, no part of this
RIGHTS publication may be reproduced, stored in a retrieval system, or
RIGHTS transmitted, in any form or by any means, electronic, mechanical,
RIGHTS recording, or otherwise, without prior permission of the RIPE NCC
RIGHTS on behalf of the copyright holders. Any use of this material to
RIGHTS target advertising or similar activities are explicitly forbidden
RIGHTS and will be prosecuted.  The RIPE NCC requests to be notified of
RIGHTS any such activities or suspicions thereof.

# the list of valid country names RIPE database specific, used
# for syntax checking. May move into different config at later stage.

COUNTRY AE ae
COUNTRY AL al
COUNTRY AT at
COUNTRY AZ az
COUNTRY BE be
COUNTRY BG bg
COUNTRY BY by
COUNTRY CH ch
COUNTRY CM cm
COUNTRY CS cs
COUNTRY CZ cz
COUNTRY CY cy
COUNTRY DE de
COUNTRY DK dk
COUNTRY DZ dz
COUNTRY EE ee
COUNTRY EG eg
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 IR ir
COUNTRY IS is
COUNTRY IT it
COUNTRY KE ke
COUNTRY KW kw
COUNTRY LA la
COUNTRY LB lb
COUNTRY LI li
COUNTRY LU lu
COUNTRY LV lv
COUNTRY LT lt
COUNTRY MA ma
COUNTRY MC mc
COUNTRY MT mt
COUNTRY NL nl
COUNTRY NO no
COUNTRY OM om
COUNTRY PL pl
COUNTRY PT pt
COUNTRY RO ro
COUNTRY RU ru
COUNTRY SA sa
COUNTRY SE se
COUNTRY SG sg
COUNTRY SI si
COUNTRY SK sk
COUNTRY SU su
COUNTRY TN tn
COUNTRY TR tr
COUNTRY UA ua
COUNTRY YU yu
COUNTRY ZA za

# And some funny translations for the yobbos

COUNTRY GB UK
COUNTRY GB uk

# legal connect attribute values in alphabetic order
# also RIPE database specific used for syntax checking, may move to
# different config file later ....
#
CONNECT ACONET
CONNECT ALT
CONNECT CIX
CONNECT CNR
CONNECT	DATANET
CONNECT EASI
CONNECT	EBONE
CONNECT	EMPB
CONNECT EU
CONNECT EU-FI
CONNECT FICIX
CONNECT FUNET
CONNECT GARR
CONNECT HEPNET
CONNECT ICS
CONNECT INFN
CONNECT IRIS
CONNECT IUNET
CONNECT JANET
CONNECT LANLINK
CONNECT LOCAL
CONNECT NIKHEF
CONNECT NLNET
CONNECT NORDU
CONNECT NSF
CONNECT PIPEX
CONNECT POWERWAN
CONNECT RCCN
CONNECT REDIRIS
CONNECT RENATER
CONNECT RIPE
CONNECT SARA
CONNECT SURF
CONNECT SWIP
CONNECT SWITCH
CONNECT TIP
CONNECT WCW
CONNECT WIN
CONNECT XLINK

ENDCONF		# do not remove!



-------- Logged at  Wed Feb 23 10:20:20 MET 1994  ---------