ITU

Committed to connecting the world

Interim Procedures for Shared Country Codes

Interim Procedures for the delegation of E.164

Shared Country Codes for Networks and Groups of Countries

These procedures have been approved on 15 May 2008 by ITU-T Study Group 2

1 Scope

The purpose of this document is to set out the interim procedures that will be used by the TSB, should the TSB receive a request from RIPE-NCC or an assignee of a Identification Code (IC) from a shared E.164 Country Code for Networks or Group Identification Code (GIC) from a shared E.16​4 Country Code for Group of Countries before final approval of the future Recommendation.  The procedures to be described in the finally approved version of the future Recommendation will supersede these interim procedures. These procedures shall not prejudice the future Recommendation.

The following agreements will apply to the interim procedures:
These interim procedures cover only assigned CC + ICs and CC + GICs within the respective shared E.164 country codes.  Unless further guidance is received to the contrary from Study Group 2, the TSB will send an objection to RIPE NCC with respect to any requests for delegations of any other types of country codes not covered in this or any other interim procedure.

2 Interim Procedures

These interim procedures are consistent with the agreed SG2 statement that the CC + IC assignee or CC + GIC administrator will have the right to choose whether to participate in the common designated ENUM domain, or not to participate in it, at their discretion, and with the procedures currently under development as specified in the future Recommendation(s). In the case of CC + ICs, it is a national matter whether requests for codes require national Administration review or approval.

2.1 Formal Validity of CC

When the TSB receives a request from RIPE NCC, it will first verify that the country code (CC) mentioned in the request meets the formal conditions for delegation for ENUM, namely:
    1. That the country code is a currently-assigned resource

    2. All number assignees (IC or GIC code holders) within the requested CC must endorse the request.

    3. In the alternative, when a request representing the entire code is received and endorsed by two or more code holders, but not all of the code holders, within the shared country code, this request shall also be accepted provided that no code holder within the shared country code objects within 60 days and that there is a formal agreement between the TSB and the Tier 1 Registry that only those portions (i.e., ICs or GICs) of the code for which the requesting code holders are responsible will be delegated.

    4. Furthermore, when only a single code holder within a shared country code requests that its IC or GIC be delegated, this request may also be accepted if the request corresponds to that IC or GIC for which the code holder has administrative responsibilities and the country code is delegated to the Tier 0 Registry and there is a formal agreement between the Tier 0 Registry and the TSB to the effect that only the IC of GIC for that specific code holder will be delegated under a separate arrangement between the code holder and the Tier 0 Registry.
If these conditions are not met, the TSB will notify RIPE NCC that it objects to the delegation.  As a consequence, the delegation will not take place.

2.2 Assignee Position Known

If the conditions of 2.1 are met, and if the concerned assignee has notified the TSB of its position regarding delegation for ENUM of its CC + IC or GIC, then the TSB will immediately make that position known to RIPE NCC.
That is, TSB will inform RIPE NCC that the concerned assignee either approves or objects to the delegation.  If the assignee objects, the delegation will not take place.
Since the request from RIPE NCC will designate a specific ENUM Tier 1 Registry, the TSB will only be able to approve the request if the assignee has notified the TSB that it approves that particular Tier 1 entity.

2.3 Assignee Position Not Known

If the conditions of 2.1 are met, but the concerned assignee has not previously notified the TSB of its position regarding delegation for ENUM of its CC + IC or GIC, then the TSB will proceed as follows:
    1. Within 60 days, notify RIPE NCC that it objects to the delegation, because it has not received approval from the concerned assignee.

    2. Within 60 days, notify the concerned assignee of the request and of the TSB objection sent to RIPE NCC, and request the assignee to advise the TSB if the objection should be rescinded and an approval sent to RIPE NCC.

    3. If an approval is received from the assignee, notify RIPE NCC of that approval.
That is, the delegation will not take place until the concerned assignee has notified the TSB that it approves the delegation.

2.4 Change in Position

If an assignee notifies the TSB of a change in its position, the TSB will communicate that change to RIPE NCC, who will implement the change.  The changes can be:
    1. A previously granted approval becomes an objection.  In this case, the delegation will be removed and ENUM will no longer be available for the concerned CC + IC or GIC.

    2. A previously stated opposition, or lack of approval, becomes an approval.  In this case, the delegation will be granted and ENUM will be available for the concerned CC + IC or GIC.

    3. There is a change in the party to which the CC+ IC or CC + GIC is delegated, that is, a change in the ENUM Tier 1 Registry.  In this case, the TSB will notify RIPE NCC of that change and the change will be implemented.  In the case of Groups of Countries, any change would need to be certified by the administrator of the CC + GIC.
That is, an assignee may at any time stop, enable, or change ENUM delegations.

2.5 Communication Methods

    1. Communications between the TSB and assignee will be between the Director of the TSB and the official contact nominated by the assignee and on file with the ITU.  Assignees are encouraged to notify the TSB regarding who should be the official contact for ENUM matters.  Such notification shall be provided by the official contact described below.

    2. Communications will take place by physical letter or facsimile, although E-Mail may be used in addition for clarification (but not for formal decisions).

    3. To expedite the process, initial requests should be sent first to the TSB.  After approval is received, the requests can be sent to RIPE NCC in conformance with the RIPE NCC Instructions.

    4. All approvals will be posted on the TSB Web site at http://www.itu.int/ITU-T/inr/enum/.

    5. Communications between the TSB and RIPE NCC will take place by E-Mail. The TSB will designate a mail address for this purpose. The TSB will keep an archive of all E-Mails sent and received.

    6. Any approvals sent to RIPE NCC will be confirmed in writing by the Director of the TSB.

    7. When notifying an approval to RIPE NCC, the formal approval letter by the Director of the TSB will contain appropriate language with respect to the Member State’s authority to revoke its approval and transform it into an objection.