🚀 go-pugleaf

 In your previous mail you wrote:


   	There is something that has been rankling me a while now,
   and shows no sign of changing... that is the registration of
   in-addr.arpa records for "non-connected" sites. Now the status
   "non-connected" is a relative, or more correctly relativistic, term.
   It depends on the perspective of the observer.

--> Philippe,
This problem has been identified for some time already inside RIPE (I'd
around January 90). There has been intense discussion between RIPEmen
(Rob, Matts Brunnel, Bernhard Stockman, ...) and our US collegues (including
Merrit and NIC). This led to the understanding that being in the 
naming-tree (direct or inverse) is totally decoupled with adminsitrative
authorisation to use any part of the Internet (once called "connected
status").
This understanding has been reflected both in an RFC and in actual practice
from the NIC (then at SRI).

It is a fact that (seldom) some problem of "in-addr+connected-status" arise
but we (inside RIPE) really consider this as an accident. No such problem
has stayed long after we told relevant people at NIC.

Thus I don't see a problem here. 

Should you experience such problem please feel free to contact 
fr-technical-contact@inria.fr for assistance, or Francis.Dupont@inria.fr
(chairman of RIPE TF3, related to DNS issues) or Rob Blokzijl (k13@nikhef.nl)
in case escalation is needed.

Enjoy a nice new year,
Yves.

 ----------------------------------------------------------------
 Yves Devillers
 Internet:    Yves.Devillers@inria.fr  Institut National de Recherche
 Goodie-Oldie: ...!uunet!inria!devill  en Informatique et Automatique
 Phone: +33 1 39 63 55 96              INRIA, Centre de Rocquencourt
 Fax:   +33 1 39 63 53 30              BP 105, 78153 Le Chesnay CEDEX
 Twx:   633 097 F                      France.