|
For a full overview of all RIPE NCC e-mail contacts, please refer
to: http://www.ripe.net/info/ncc/email-contact.html
Registry Identifier
The Registry Identifier must be included in every message sent
to <hostmaster@ripe.net> and <lir-help@ripe.net>.
It is used to identify the registry. Each request containing a valid
identifier will receive an acknowledgement indicating whether they
receive service or not and a ticket number (see below).
In accordance with the policies established by the contributors' committee
(see ripe-132
for details), the RIPE NCC provides service only to its contributors.
Requests received from contributing LIRs will be handled in the order
in which they are received. Requests from LIRs that are behind on
their payments will not be serviced until the financial situation
has been rectified. Requests not accompanied by a valid Registry Identifier
will not be processed.
Where possible we suggest the inclusion of the identifier in an RFC822
header line of the messages concerned. The suggested format is: X-NCC-RegID:
nn.example Where it is impossible to modify the RFC822
header, this line can also be included in the body of the message.
Please note that the registry identifier needs to be lower case (it
is case sensitive).
Ticketing System
The RIPE NCC uses a ticketing system to track the history of every request
sent to the above mailboxes. Requests submitted to these role accounts
will be notified of the ticket number that has been assigned to the
request. The number must be referenced in all subsequent messages
related to this request. The ticket number remains valid until the
request has been handled. Every new request gets a new ticket number.
This means that a LIR should never send two requests in the same message.
Moreover, because a ticket number is associated with a specific request,
it should never be re-used.
Distribution Robot
The RIPE NCC uses an automatic robot to distribute all messages sent
to these role accounts.
PGP Authentication
At the RIPE 40 meeting, a decision was made that all outgoing e-mails from
the RIPE-NCC to the Local Internet Registries should be authenticated.
The e-mail that you received from these accounts (mentioned above)
have been signed by the RIPE-NCC PGP master key.
|
you are here: home -> Internet Resources
