IAB Instructions for operation of the domain e164.arpa
August 2004
| 1.1 | A request for a delegation is to be sent to the RIPE NCC, to an email address that the RIPE NCC will define [3.1]. The request is to follow a template that the RIPE NCC will create. [3.2]. | |
| 1.2 | The RIPE NCC will then acknowledge the request to the sender. | |
| 1.3 | The RIPE NCC will then announce the existence of the application in all of the following three ways: | |
| 1.3.1 | On a public Mailing List [3.3] that the RIPE NCC will define. | |
| 1.3.2 | On a Webpage [3.4] that the RIPE NCC will define. | |
| 1.3.3 | Via electronic mail to ITU-T TSB [3.5]. | |
| 1.4 | The RIPE NCC will then track any comments about the request during a waiting period. This waiting period is sixty (60) days. | |
| 1.4.1 | If ITU-T TSB explicitly authenticates a request during the waiting period, the domain is delegated even though the 60 day period has not ended. | |
| 1.4.2 | If ITU-T TSB does not object, and does not inform the RIPE NCC of the objection during the waiting period, the domain is delegated according to the request. | |
| 1.4.3 | No delegation will be performed if ITU-T TSB objects within the sixty (60) day waiting period. | |
| 1.5 | Anyone who has concerns about the delegation should contact the RIPE NCC [3.1] or ITU-T TSB. If comments come to the RIPE NCC on the proposed delegation, the RIPE NCC will forward the comments to ITU-T TSB [3.5]. The comments, the dates they are received by the RIPE NCC, as well as the forwarding of the comments by the RIPE NCC to ITU-T TSB are all made public. | |
| 1.6 | All communication regarding the application for a specific delegation is to be publicly archived. | |