On Jan 4, 10:08, RIPE NCC Hostmaster wrote:

Subject: New Status of Last Resort Registries

Dear hostmaster, I don't see any reference in the letter to in-addr.arpa delegation being passed from Last Resort Registries to RIPE NCC. It should be included and also the procedure for this transfer (for instance, copy of the primary servers files). Regards, Miguel A. Sanz +---------------------------------------------------------------+ | ES-NIC (Delegated Internet Registry for Spain) | | Centro de Comunicaciones CSIC RedIRIS | | Serrano 142 Tel: + 34 1 5855150 | | 28006 Madrid Fax: + 34 1 5855146 | | SPAIN Email: nic@rediris.es | +---------------------------------------------------------------+

Dear Colleagues,

Seasons Greeting and the best wishes for the New Year from all of the RIPE NCC.

As announced earlier the status of the Last Resort Registries will change from 1996 on.

We appologise for not sending this message earlier. We kindly ask you to respond as soon as possible. Our target to have these matter resolved is the beginning of February, right after the next RIPE Meeting.

The NCC Contributors Comittee decided during the last meeting in September that all Local IRs need to contribute to the RIPE NCC to receive registration service.

This has implications for the Local IRs that currently run a Registry of Last Resort. There are two possiblities for these LIR's:

1. Contribution to the RIPE NCC 2. Closure of the Last Resort Registry

In order to facilitate aggregation of routing information and therefor a stable Internet routing the closure of the Last Resort Registries is the preferred solution.

If the first possibility is chosen, the size of the registry needs to be determined and an "Agreement on the provision and use of the RIPE NCC services" needs to be signed and send to the RIPE NCC. For more details please refer to

ftp://ftp.ripe.net/ripe/new-registry

or contact <billing@ripe.net>.

If the Last Resort Registry will be closed, please read and edit the following form letter and send it back to <hostmaster@ripe.net>

The closure of a LIR can only be effective after the issues below are resolved.

If you plan to continue the Last Resort Registration Service, please notify us before January 15th. Otherwise your registry will receive no service.

In case you run two registries a Last Resort Registry and a Provider Registry, please note, that the operation of the Provider Registry is not effected by this matter.

Kind regards,

Mirjam Kuehne RIPE NCC

----------------------------------------------------------------------

Dear colleagues,

We formally request to close the local Internet Registry operated by XXXXX-Organisation under registry ID xxx.zz effective at <date>.

We enclose a final summary of all address space assigned by and through our registry as enclosure A.

We also enclose a list of all address space allocated (delegated) to our registry but not yet assigned as enclosure B. We understand that we are not allowed to make any further assignments from this address space after the closure and that this address space can be re-allocated and re-assigned by the RIPE NCC as necessary.

We will guarantee that the RIPE NCC can at any time access all records concerning customers's requests for address space as per the "IP Address Space Assignment Procedures" (ripe-104): "IRs will keep records of correspondence and information exchanges in conjunction with the registry function for later review and the resolution of disputes. IRs will hold this information in strict confidence and use it only to review requests and in audit procedures or to resolve disputes."

If access can not or will no longer be guaranteed, we will transfer the records to the RIPE NCC after prior agreement on the procedure.

The RIPE NCC will hold this information in strict confidence and use it only to review requests, audit procedures or to resolve disputes.

Currently ongoing requests for IP address space will either be finished before closing the registry or the requester will be referred to the list of local Internet registries that can be found at

ftp://ftp.ripe.net/ripe/registries/

after he/she has been informed about the issues related with PA/PI address space outlined in ripe-127.

We understand that the closure of our registry has the following consequences:

- The registy entry xxx.zz will be removed from the directory of Local Internet Registries (ftp://ftp.ripe.net/ripe/registries/).

- The e-mail addresses registered for registry xxx.zz will be removed from the mailing lists ip-provs@ripe.net, ncc-co@ripe.net and local-ir@ripe.net automatically. Note that it is possible to re-subscribe to local-ir@ripe.net on an individual basis.

- All registry requests from XXX-Organisation directly to the RIPE NCC will henceforth be treated as requests from an individual and will not receive registration service unless they are channeled through another local IR.

We understand and agree to the above.

For the xxx.zz registry operated by XXX-Organisation

<signature of xxx.zz administrative contact(s)>

Enclosure A:

EXAMPLE EXAMPLE EXAMPLE

------- Allocation record -----------

193.0.0.0 - 193.0.255.255 -----------------------------------------------------------------

193.0.0.0 - 193.0.1.255 1-Dec-94 Internal Infrastructure 193.0.2.0 - 193.0.2.127 1-Dec-94 ABC Organisation 193.0.2.128 - 193.0.2.255 1-Dec-94 ABC Organisation Int. 193.0.3.0 - 193.0.3.255 2-Dec-94 XYC-Organisation 193.0.4.0 - 193.0.7.255 11-Dec-94 AB Network Inc. 193.0.8.0 - 193.0.15.255 11-Dec-94 XY Net-Institute ...

Enclosure B:

EXAMPLE EXAMPLE EXAMPLE

Non-assigned IP addresses: -----------------------------------------------------------------

193.0.104.0 - 193.0.127.255 193.0.160.0 - 193.0.168.255

193.0.213.0 - 193.0.213.255 193.0.216.0 - 193.0.216.255 193.0.221.0 - 193.0.221.255 193.0.244.0 - 193.0.244.255 193.0.245.0 - 193.0.245.255

-- End of excerpt from RIPE NCC Hostmaster