|
INTERNATIONAL
TELECOMMUNICATION UNION |
|
|
TELECOMMUNICATION STUDY
PERIOD 2001 - 2004 |
COM 2-LS 42/2-E |
||
|
|
||
itu-t
sg2, 7-16 may 2002 |
|||
TITLE: |
APPROVAL
OF INTERIM PROCEDURES AND ASSURANCES OF STABILITY |
||
Question(s): |
Q1/2 |
||
LIAISON STATEMENT |
|||
TO: |
ISOC
FOR IAB |
||
APPROVAL: |
agreed
sg2 16 may 2002 |
||
FOR: |
Information
|
||
DEADLINE: |
|
||
CONTACT: |
Philippe
Distler Chairman, WP
1/2 |
Tel: +33 1 40
47 71 20 Fax: +33 1 40
47 71 90 E-mail: distler@art-telecom.fr
|
The ITU-T Study Group 2 plenary has approved interim procedures for delegation of E.164 geographic country codes into the e164.arpa domain in accordance with RFC 2916. These procedures provide instructions to the ITU-T Telecommunications Standardization Bureau (TSB) with respect to its interactions with the technical manager of e164.arpa (currently the RIPE-NCC), in order to specify what TSB should do whenever it receives a request for the delegation of an E.164 country code. The interim procedures are attached.
The e164.arpa domain name is the root under which the whole ENUM system will be implemented for the period of validity of the interim procedures (i.e. until definitive procedures set out in an ITU-T Recommendation supersede the interim procedures).
The ITU-TSB has a major role to play for the sound implementation of these interim procedures and to ensure that the data entered into the domain e.164.arpa and its sub-domains are consistent with the E.164 numbering plan.
In that context, Study Group 2 seek assurances that the Director of ITU-T TSB and the appropriate Study Group would be consulted before significant changes that would affect the interim procedures take place.
For example:
ú references to TSB's role in the IAB Instructions to RIPE NCC and,
ú the choice of the Tier 0 Registry, at present RIPE NCC.
There might be several ways to address these assurances with a view to formalizing the understandings reached and associated relationships. As an example, one way could be a Memorandum of Understanding or similar document between ISOC and ITU-T covering the issues.
We would welcome suggestions from IAB concerning the best ways to address these issues.
ANNEX
ENUM administration ad interim
(Revised 14 May 2002 - clean version of the text)
1 Background
It appears that
there is considerable interest in starting ENUM trials in some Member States so
that it would be appropriate to provide interim procedures to enable such
trials to take place.
In response to this
interest, the Internet Architecture Board (IAB) issued instructions to RIPE-NCC
regarding how to proceed with any requests received by RIPE-NCC. The instructions are reproduced for
information in the Appendix of this contribution. It should be noted that the instructions are fully
consistent with the statement:
Member States
will have the right to choose whether to participate in the common designated
ENUM domain, or not to participate in it, at their discretion.
Consistency with
the above statement is achieved by RIPE-NCC’s referring any requests for
delegations[1] of domain names
corresponding to E.164 country codes[2] to the
Telecommunications Standardization Bureau (TSB) for approval.
It is important
that the TSB process any such requests in a transparent and consistent way, and
therefore these procedures have been created. In the long-term, it is envisaged that the TSB processes and
procedures will be specified in a future Recommendation(s).
2 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 before final approval of
the future Recommendation(s). The
procedures to be described in the finally approved version of the future
Recommendation(s) will supersede these interim procedures. These procedures shall not prejudice
the future Recommendation(s).
The following agreements were made relative to the interim procedures:
ú The interim procedures will remain in effect until the approval of a future Draft Recommendation(s), currently Draft Recommendation E.A-ENUM, which will then supersede these interim procedures.
ú The interim procedures can be modified at any time and will be reviewed no later than the scheduled May meeting of SG2 in 2003.
These interim
procedures cover only assigned geographic 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.
3 Interim
Procedures
These interim
procedures are consistent with the agreed SG2 statement that Member States 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).
3.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 code is a currently-assigned country code, and
2.
For country codes within an integrated numbering plan, the request
corresponds to that portion of the code for which the requesting Member State
has administrative responsibilities.
When a request representing the entire integrated country code area is
received, all Member States within the integrated numbering plan must endorse
the request.
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.
3.2 National
Position Known
If the conditions
of 3.1 are met, and if the concerned Member State has notified the TSB of its
position regarding delegation for ENUM of its CC, then the TSB will immediately
make that position known to RIPE NCC.
That is, TSB will
inform RIPE NCC that the concerned Member State either approves or objects to
the delegation. If the
Administration 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 Member State has notified the TSB that it
approves that particular Tier 1 entity.
3.3 National
Position Not Known
If the conditions
of 3.1 are met, but the concerned Member State has not previously notified the
TSB of its position regarding delegation for ENUM of its CC, 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 Member State.
2.
Within 60 days, notify the concerned Member State of the request and of
the TSB objection sent to RIPE NCC, and request the Member State 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 Member State, notify RIPE NCC of
that approval.
That is, the
delegation will not take place until the concerned Member State has notified
the TSB that it approves the delegation.
3.4 Change
in National Position
If a Member State
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.
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.
3.
There is a change in the party to which the CC 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.
That is, a Member
State may at any time stop, enable, or change ENUM delegations.
3.5 Communication Methods
1.
Communications between the TSB and Member States will be between the
Director of the TSB and the official contact nominated by the Administration of
the concerned Member State and on file with the ITU. Administrations of Member States 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.
In the absence of
a specific notification for ENUM matters, the official Administration point of
contact listed in the ITU Directory will be used.[3] Communications
will take place by physical letter or facsimile, although E-Mail may be used in
addition for clarification (but not for formal decisions).
2.
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.
3.
All approvals will be posted on the TSB Web site at http://www.itu.int/ITU-T/inr/index.html.
4.
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.
Any approvals
sent to RIPE NCC will be confirmed in writing by the Director of the TSB.
5.
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.
________________
[1] The term “delegation” as it applies to the Domain Name System (DNS)
is described in RFC 1591.
[2] See RFC 2916.
[3] For information, these official contacts can be found at http://www.itu.int/cgi-bin/htsh/mm/scripts/mm.list?_search=ITUstates&_languageid=1
by clicking on the Member State entry and then, within the Member State entry,
on the entry listed as “ADMIN”.