What remains open is the question on whether in-addr.arpa zone registrations should be effected automatically by registering the 'rev-srv' field in the RIPE database. I have had quite a few comments from people who want this and I personally agree it would be a nice feature. I do not see Piet's argument that this would mean a loss of authority of the network contacts. This form of "indirect registration" would indeed not mean loss of authority. The problem remains though that separate functions - DB and DNS - become intermixed here. And then whom do you contact/tell/flame if the root servers contain wrong information? 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. And once you start doing such things for the reverse servers, the next step may well be doing the same for "forward servers"; then how can e.g. a top level domain registrar determine whether a given change is valid, e.g. comes from an authoritative person?
There no need to do that for forward servers because they are structured as a distributed three and the authority is delegated at each level. In practice today the US NIC does not check at all if a rev-srv change comes from an "authoritative person" because they do not check where the mail request comes from and it is practically impossible for them to pick a phone an call someone in Europe. So this is not the point. ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito@nis.garr.it GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito c/o CNUCE - Istituto del CNR Tel: +39 (50) 593246 Via S. Maria, 36 Telex: 500371 CNUCE I 56126 PISA Italy Fax: +39 (50) 904052 ---------- ----------