IAB Instructions for operation of the domain e164.arpa

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 ITU-T TSB will acknowledge the receipt of the request and take appropriate action to verify the delegation request within a sixty-day period.

1.4.1 The RIPE NCC will wait for the ITU-T TSB to confirm the delegation. A delegation will only be made upon receipt of confirmation from the ITU-TSB.

1.4.2 If no confirmation is received or the ITU-T TSB explicitly objects, the requester will be informed that a delegation cannot be made and the request is denied.

1.5 Anyone who has concerns about the delegation should contact the ITU-T TSB.

1.6 All communication regarding the application for a specific delegation is to be publicly archived.  

2. Notes

2.1 In its capacity as the IESG-designated expert for ENUM as specified in RFC 2916, the RIPE NCC will review the submission for completeness according to the template. If it is not complete, the RIPE NCC will notify the sender of that fact and request that it be completed. An incomplete application will not be taken into consideration for delegation or re-delegation.

2.2 Given that the RIPE NCC and the ITU-T TSB will request different information (technical and administrative information, respectively), it is recommended that the applicant send the request both to the RIPE NCC and the ITU-T TSB.

2.3 The ITU-T TSB acts on requests according to methods of its choosing. The ITU-T TSB must inform the RIPE NCC of a decision within a sixty-day period.

2.4 The ITU-T TSB can, at any time, directly instruct the RIPE NCC to delegate any E.164 country code (CC). This instruction from the ITU-T TSB must include a completed delegation request form.

2.5 If more than one request is received for the same E.164 CC before the delegation is made, the RIPE NCC will forward that information to the ITU-T TSB as a comment on the initial delegation request.

2.6 If a request is received for a CC that is already delegated, the RIPE NCC will forward the second request to the ITU-T TSB. The ITU-T TSB should authenticate the request with the original E.164 resource assignee and inform the RIPE NCC of what action to take. Such action can either be to fulfil the request and re-delegate the resource to the new requester, or to deny the request. The RIPE NCC will take no action (other than forwarding the request to the ITU-T TSB) until and unless instruction is received from the ITU-T TSB.

2.7 Any actions referred to in [2.6] requested by the ITU-T TSB will be implemented by the RIPE NCC within 60 days of the RIPE NCC’s reception of the request.

2.8 This document instructs the RIPE NCC in the handling of E.164 CC delegations.

2.9 In the case that a request is made for a domain that is not a valid CC, the ITU-T TSB will inform the RIPE NCC and the applicant that it will not proceed with the requested delegation.

2.10 A request to revoke an existing delegation of an E.164 resource can be sent to the RIPE NCC by the original resource assignee. The RIPE NCC will exercise appropriate due diligence to authenticate this request and, upon successful authentication, will forward the revocation request to the ITU-T TSB for consultation and publish it in accordance with [1.3]. It will then enter a sixty-day waiting period.

2.10.1 Within the sixty-day period, a request for re-delegation can be made by filing a new delegation request. Such a request will be processed as per [2.6], restarting the associated sixty-day waiting period for the ITU-T TSB to approve the re-delegation.

2.10.2 If a revocation request is not approved within the sixty day period and no request for a new delegation is received, the RIPE NCC will send a reminder to the ITU-T TSB regarding the outstanding request. If a subsequent reminder of a revocation is not responded to, the matter will be brought to the attention of ITU Study Group 2 by means of a Liaison Statement.

2.10.3 If the new delegation request is not approved or no response is received within the sixty-day period, the RIPE NCC will send a reminder to the ITU-T TSB regarding the outstanding requests. If a subsequent reminder of a request is not responded to, the matter will be brought to the attention of ITU Study Group 2 by means of a Liaison Statement.

2.10.4 Upon revocation, the RIPE NCC will inform the ITU-T TSB and request it to remove any reference to the delegation from ITU-T webpages or other publications that may contain an overview of E.164 resources.

2.10.5 When the RIPE NCC is requested to restore a previously revoked delegation, the RIPE NCC will consider this to be a new request and process it accordingly.

2.10.6 When RIPE NCC receives notification via the TSB that a Member State has changed a previously granted approval, RIPE NCC will work with those to whom the delegation was made and the Member State to develop a plan for the existing ENUM delegations.

2.11 In case the technical set-up of an existing delegation becomes fully non-functional, and the assignee has no intentions to restore it (or is unreachable), the RIPE NCC will consider this to be a revocation request, which it will forward to the ITU-T TSB and will announce in accordance with [1.3].

2.11.1 After the ITU-T TSB has instructed the RIPE NCC to delegate a domain, the assignee must complete the necessary technical set-up in order for the delegation to be registered. In case the technical set-up is not completed after 180 days, and the assignee has no intentions to complete it (or is unreachable), the RIPE NCC will consider this to be a revocation request, which it will forward to the ITU-T TSB and will announce in accordance with [1.3].

2.12 The RIPE NCC will conduct periodical checks (at time intervals that the RIPE NCC will define) of approved delegations and will contact assignees to ensure the correctness of their DNS set-up, registration data and contact information.

2.12.1 In case the technical set-up of an existing delegation becomes non-functional, and the assignee has no intentions to restore it (or is unreachable), the RIPE NCC will consider this to be a revocation request, which it will forward to the ITU-T TSB and will announce in accordance with [1.3].

3. Summary List of Actions required by the RIPE NCC before delegations can be made

3.1 Set up an email address to which delegation applications and comments are to be sent.

3.2 Define the template that is to be filled out by the applicant.

3.3 Set up a mailing list with archiving and automatic subscription capabilities to which the RIPE NCC is to send announcements. Anyone is to be able to subscribe to this mailing list, but posting is to be restricted.

3.4 Set up a webpage with a URI that will be as long lived as possible so direct references can be made to the URI of the page itself.

3.5 In communication with the ITU-T TSB director, agree on the email address to which notifications will be sent to the ITU-T TSB.