Dear All,
First off, my apologies to all who get more than one copy of this
message. I'm hoping not to miss anyone who may be effected.
As many of you may know, we have long been planning to more fully
automate our inaddr robot <auto-inaddr(a)ripe.net>. Well, we've gotten
around to it and are happy to announce we will soon be doing almost
all processing automatically, with just a touch of human intervention
at the end to make certain our robot behaves as expected.
The result will be a substantial reduction in rather tedius work for
the NCC staff, and consistent short response times (one working day)
for inaddr requests.
The new robot, programmed by Mal Morris, will be installed on
*** Tuesday, May 6, 1997 ***
It is essential that users take the following changes into account:
1. The domain or inetnum database object must be in the RIPE database
before the request is submitted to <auto-inaddr(a)ripe.net>.
2. As is required in ripe-140 (Section 3.4.2), the "status" field must
be filled in properly for any inetnum associated with the request.
The robot will complain and fail if either of these does not hold.
We hope the new robot serves you well,
Carol
