In reference to the query raised by SG2 [1] regarding the administrative arrangements relating to the management of the e164.arpa domain, and the .arpa domain as it relates to ENUM.

As stated in Annex A of RFC 3172 [2] , the IAB believes that the contract between the US Department of Commerce and ICANN concerning the IANA function indicates that ICANN’s administration of the ‘arpa’ domain takes place under the guidance of the IAB. That is, the IAB believes that no changes can be made to the ‘arpa’ domain without the explicit authorization of the IAB. This includes of course the administrative contacts for ‘.arpa’ and for ‘e164.arpa’.

For the same reasons noted in the IAB’s liaison statement to SG2 of 12 September 2002 [3], the IAB is able to offer the view that any changes in the administrative contact for the domain e164.arpa would require equivalent operational working relationships to be established with any successor or alternative administrative contact. Accordingly, the IAB provides an undertaking to consult with ITU-T TSB and relevant ITU study groups in advance of making any changes in the administrative contact for the domain e164.arpa.

In respect to any contemplated changes in the .arpa domain, the IAB is mindful of the commitments made in this and the previous liaison statement on this topic, and provides an undertaking that, to the best of its abilities, the IAB would not make changes to the .arpa domain arrangements that would materially alter the nature of these existing commitments relating to e164.arpa.

We hope this will address your concerns, and look forward to continued constructive collaboration in making the ENUM standard a success.

Leslie Daigle.
Chair, Internet Architecture Board
iab-chair@ietf.org

28 February 2003

References

[1] ITU-T SG2 LIAISON STATEMENT, e164.arpa domain management
http://www.ietf.org/IESG/LIAISON/COM2-056.htm.

[2] Internet Architecture Board, Huston, G., ed., “Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain (“arpa”) “, BCP 52, RFC 3172, September 2001.

[3] Internet Architecture Board Liaison Statement to ITU-T SG2, “Re. APPROVAL OF INTERIM PROCEDURES AND ASSURANCES OF STABILITY”,
sg2-liaison-sep-02.html.