the difference between assign@localhost and ripe-dbm@localhost
- Date: Mon, 21 Jun 1993 12:19:39 +0200
Dear people,
There seems to be some misunderstanding between the usage of assign@localhost
and ripe-dbm@localhost. Please use these two addresses as follows:
assign@localhost
- only for NEW assignments made out of your 193.x block (so, they
should not be in the RIPE or NIC database yet)
ripe-dbm@localhost
- all other nets new to the database, and all updates.
x.193.in-addr.arpa requests should be send to hostmaster@localhost, because
there is some additional action on behalf of the NCC needed. We will then
forward the objects to ripe-dbm, when all set up.
The reason we have a difference between the two is that assign@localhost has
some additional consistency checking before it will forward to the database,
since we found that many people made 192/193 typos, and also we are planning
with InterNIC to automatically forward NEW 193 assignments directly to them
in exchange format in the future.
If a network send in to assign@localhost is already present in the NIC or RIPE
database, the update is bounced back to the NCC for manual review. In most
cases it will be forwarded to ripe-dbm after, but it would be nice if we
could keep these kinds of "assignment errors" as we call them, to a minimum.
PS contact people send in to either address are not checked, so you can
simply include them in assign or ripe-dbm together with the network numbers
they belong to.
Cheers,
-Marten
