This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

in-addr.arpa zone data in RIPE database

• Previous message (by thread): in-addr.arpa zone data in RIPE database
• Next message (by thread): in-addr.arpa zone data in RIPE database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Piet Beertema Piet.Beertema at cwi.nl
Wed Mar 3 15:55:29 CET 1993

		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

• Previous message (by thread): in-addr.arpa zone data in RIPE database
• Next message (by thread): in-addr.arpa zone data in RIPE database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]