in-addr.arpa zone data in RIPE database

		An indirect way of correcting things via submissions to
		the RIPE DB in my view is far from ideal, as it may well
		introduce unnecessary delays.
	Soon this argument will be moot for at least 193.in-addr.arpa...
True. Now if only the world consisted solely of 193.in-addr.arpa...

		....then how can e.g. a top level domain registrar
		determine whether a given change is valid, e.g. comes
		from an authoritative person?
	How do you ensure authority today?
By checking against my TLD admin files.


	Piet