1. A request template for a delegation is to be sent to the RIPE NCC
2. The RIPE NCC will then acknowledge the request to the sender.
3. The RIPE NCC will then announce the existence of the application.
4. The RIPE NCC will then track any comments about the request during a waiting period. This waiting period is sixty (60) days.
5. If ITU-T TSB explicitly requests a delegation during the waiting period, the domain is delegated even though the 60 day period has not ended.
6. If ITU-T TSB does not object, and inform the RIPE NCC of the objection during the waiting period, the domain is delegated according to the request.
7. Anyone who has concerns about the delegation should contact the RIPE NCC or ITU-T TSB. 8) All communication regarding the application for a specific delegation is to be publicly archived.

Basically, this means that if you want to run the 1.e164.arpa registry for North America, just follow the instructions and if no one objects during the 60 day waiting period, then per # 6 above it's yours. An example template of what needs to be completed and submitted to RIPE can be found here.

It should be pointed out that "The RIPE NCC is not performing any evaluation of requests for delegation of domains under e164.arpa. This is the responsibility of ITU-T TSB." In other words, RIPE is just accepting the requests, making them public, and accepting feedback. (Seems like a straightforward approach - maybe someone should send the NTEPPTF this idea.) It is not clear as yet what the ITU-T TSB will be basing its decisions of delegation upon but according to the RIPE site the ITU-T SG2 is working on just such a document called A.ENUM.

A quick look at the RIPE archive shows a single entity that has thus far requested delegation: DENIC.de a member of the Internet Council of Registrars (CORE) presumably for the 49.e164.arpa representing the country of Germany.

enum.info