<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

database config change


Folks,

Due to the introduction of or routes and other changes that are a
result of the second and final database transition today towards
ripe-181, please find below the object definitions as currently used
at the NCC. Secondaries should update their config. For others, FYI.
Also there are some other variables which will no longer be used:
CONNECT, SPLITMSG, GRDCONFLICT.

If you have questions, please let me know.

-Marten


# The list of valid attribute names themselves in short and long version
#
ATTR	ac	admin-c
ATTR    aa      as-name
ATTR	ad	address
ATTR    ae      as-exclude
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    at      auth
ATTR	au	authority
ATTR	av	advisory
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    dt      upd-to
ATTR	em	e-mail
ATTR	fx	fax-no
ATTR	gd	guardian
ATTR	gw	gateway
ATTR    ho      hole
ATTR    if      ifaddr
ATTR	ii	ias-int
ATTR	in	inetnum
ATTR    ir      inet-rtr
ATTR    it      interas-in
ATTR    io      interas-out
ATTR    la      localas
ATTR	lo	location
ATTR	ma	maintainer
ATTR    mb      mnt-by
ATTR    mt      mntner
ATTR    mn      mnt-nfy
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    or      origin
ATTR    pe      peer
ATTR	ph	phone
ATTR	pn	person
ATTR	rl	routpr-l
ATTR	rm	remarks
ATTR	rp	rout-pr
ATTR    rt      route
ATTR	rz	rev-srv
ATTR	sd	sub-dom
ATTR	so	source
ATTR	tc	tech-c
ATTR	tr	as-transit
ATTR    wd      withdrawn
ATTR	zc	zone-c

# TEMPORARY FOR MERIT, WILL DISSAPEAR IN APRIL 1995
# Has been renamed to "av" or "advisory" and that one will stay
# Keep here for just a little while longer...

ATTR	lr	local-route

# Attributes with u* short names are special!
# They all have hardcoded side effects, so do NOT change them
# unless you know what you are doing

ATTR	ua	authorise	# very special
ATTR	ud	delete		# delete operation
ATTR	ue	*ERROR*		# error attribute
ATTR	uo	override	# very special as well
ATTR	uw	WARNING		# warning attribute
#

# attribute aliases (because they appear so often!)
#
ATTA	ch	change
ATTA	em	email
ATTA	fx	fax
ATTA	rm	remark
ATTA	ua	authorised
ATTA	ud	deleted
ATTA    aa      asname

# 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, a number, 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
# OBS	- these attributes are obsoleted and will be removed from objects
#		The NEED to be in ATSQ though to be recognized
#

# First, let's determine what objects are guarded, these can not be
# updated automatically, and will generate an error message.
# These objects need a "mnt-by" attribute or some other magic ....

GRDOBJ	am an cm rt ir mt

#	autonomous systems
#
OBJ     an      ATSQ    an aa de ai ao it io ae df gd ac tc
OBJ     an      ATSQ    rm ny mb ch so
OBJ     an      MAND    an de ac tc ch so
OBJ     an      OPT     aa ai ao it io ae df gd rm ny ma mb
OBJ     an      MULT    de ai ao it io ae df ac tc rm ch ny mb
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 mb ch so
OBJ     am      MAND    am de al gd tc ac ch so
OBJ     am      OPT     rm ny
OBJ     am      MULT    de al tc ac rm ch ny mb
OBJ     am      SORT    8
OBJ     am      UNIQ    am
OBJ     am      KEYS    am
OBJ     am      REC     tc ac

#	boundary gateways - obsoleted 940906
#
# 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 mb 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 mb
OBJ	cm	SORT	6
OBJ	cm	UNIQ	cm
OBJ	cm	KEYS	cm
OBJ	cm	REC	ac tc
OBJ	cm	OBS	ma

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

#	networks
#
# Switch above line to below line after a reasonable time after T2
# OBJ	in	ATSQ	in na de cy ac tc rz rm ny ma mb ch so
#
OBJ	in	ATSQ	in na de cy ac tc co as cl ii ni no gw rz
OBJ	in	ATSQ	rm ny ma mb 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 mb
OBJ	in	MULT	ac ch de ii rm rz tc ny mb
OBJ	in	SORT	5
OBJ	in	UNIQ	in
OBJ	in	KEYS	in na
OBJ	in	REC	ac tc
OBJ	in	OBS	co as cl ii ni no gw bl rl ma

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

#	routing privileges - obsoleted 940906 mt
#
# 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 rm ny ma mb ch so
OBJ	dp	MAND	dp da ac tc ch so
OBJ	dp	OPT	bi de dm do df gd ny ma rm mb
OBJ	dp	MULT	de bi dm do df ac tc ch ny rm mb
OBJ	dp	SORT	7
OBJ	dp	UNIQ	dp
OBJ	dp	KEYS	dp da
OBJ	dp	REC	ac tc
OBJ	dp	OBS	ma

#       inet-rtr
#
OBJ     ir      ATSQ    ir la if pe ac tc rm ny mb ch so
OBJ     ir      MAND    ir la if tc ac ch so
OBJ     ir      OPT     pe ny mb rm
OBJ     ir      MULT    if pe tc ac rm ny ch mb
OBJ     ir      SORT    9
OBJ     ir      UNIQ    ir
OBJ     ir      KEYS    ir if
OBJ     ir      REC     tc ac

#       maintainer
#
OBJ     mt      ATSQ    mt de ac tc dt mn at rm ny mb ch so
OBJ     mt      MAND    mt de ac dt at ch so
OBJ     mt      OPT     tc mn rm ny mb
OBJ     mt      MULT    de ac tc dt mn at rm ny mb ch
OBJ     mt      SORT    10
OBJ     mt      UNIQ    mt
OBJ     mt      KEYS    mt
OBJ     mt      REC     ac tc

#       route
#
#	lr or local-route should go soon ....
#
OBJ     rt      ATSQ    rt de or ho wd cl lr av rm ny mb ch so
OBJ     rt      MAND    rt de or ch so
OBJ     rt      OPT     ho wd cl rm ny mb la av
OBJ     rt      MULT    de ho cl rm ny ch mb av
OBJ     rt      SORT    11
OBJ     rt      UNIQ    rt or
OBJ     rt      KEYS    rt

# NO LONGER USED
#
# 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@localhost
# GRDCONFLICT Subject: Guarded attributes conflicts found
# GRDCONFLICT Cc: marten@localhost
# GRDCONFLICT 
# GRDCONFLICT REMEMBER: AS OF OCT 13, ENTRIES IN GUARDIAN FILES MUST
# GRDCONFLICT *EXACTLY* MATCH OBJECTS IN THE DATABASE !!!!!!!!!!!!!!
# 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 ------

#
# NO LONGER USED
#
# 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@localhost
# SPLITMSG Subject: $BEGINADDRESS - $ENDADDRESS has been split
# SPLITMSG Cc: marten@localhost, tony@localhost
# 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

# NO LONGER USED
#
# 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 NETTUNO
# 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!



<<< Chronological >>> Author    Subject <<< Threads >>>