Support and Transparent Process for ENUM Designated Zone implementations for the USA

1. Before theDept of State ITAC-T Advisory Committee SG-A AdHoc Meeting on ENUM Washington DC 28 Mar 2001 Support and Transparent Process for ENUM Designated Zone implementations for the USA Tony RutkowskiVeriSign, Incmailto:trutkowski@netsol.comtel:+1.703.742.4905

2. Basis for this contribution • Provide for an open, transparent process and development of agreements for the instantiation and management of Country Code 1 in the DNS zone e164.foo* • Provide for stable, robust arrangements for the top level designated DNS zone e164.foo nameservers that point to the Country Code 1 nameservers • These arrangements are critical to the creation and continued stable provisioning of Country Code 1 ENUM services on an operational basis • The arrangements are also necessary for the establishment of any testbeds for the ENUM protocol in e164.foo • Identify the parties associated with the process of establishing and evolving these arrangements * “foo” to be replaced with the designated ENUM Top Level Domain denominated by the USGOV, if any

3. Parties Associated with Creating E164.foo Designated ENUM Zone Arrangements • U.S. Dept. of State. The Office of Communications and Information Policy (CIP) has explicit Constitutional authority over foreign affairs generally; and under Executive Order 12046, authority over matters involving the International Telecommunication Union (ITU) for the U.S., and coordination among NTIA and the Federal Communications Commission (FCC) on ITU related matters, including as necessary other relevant government agencies. • The Federal Communications Commission (FCC). The FCC has statutory authority for numbering in the U.S. and hosts the North American Numbering Council. For ITU purposes, the FCC is the Administration Regulator. • U.S. Dept. of Commerce. The National Telecommunication and Information Administration (NTIA) presently controls the DNS root servers through contractual agreements with both the Internet Corporation for Names and Numbers (ICANN) for the performance of the IANA Function, and with VeriSign Global Registry Services for operation of the A and J rootservers and associated databases. The Contract Technical Representative is the point of contact. • E164.foo Administrator. The RIPE Network Coordination Center (NCC) was initially designated by the IANA Function as the responsible administrator of the E164.ARPA domain. The point of contact is Mirjam Kuhne, head of RIPE External Relations. Whoever the administrator is, the same parties are involved and the same procedures would apply. • Internet Architecture Board (IAB). The IAB as an Internet Society advisory committee has both an advisory function with respect to Internet Engineering Task Force (IETF) standards and with respect to the Society's participation as an International Organization participant in the International Telecommunication Union Telecommunication Standardization Sector (ITU-T). • ITU-T Study Group 2. ITU-T SG2 has historically been the primary collaborative standards activity through which ITU Member States have coordinated the interworking of their national public telephone networks and the associated numbering plans. This includes agreements among Member States as to the geographical and Country Codes for International Public Telephone Service. The current specification of the format of these codes is specified in ITU-T Recommendation E.164 (05/97), The International Public Telecommunication Numbering Plan. The codes are specified in the List of ITU-T Recommendation E.164 (05/97) Assigned Country Codes, published as a Complement to ITU-T Recommendation E.164 (05/97). The point of contact for this activity is the Chair of Working Party 1/2. • ITU Telecommunication Standardization Bureau (TSB). The ITU-T TSB, among other things, is responsible under the ITU Convention for support of ITU-T Study Groups. The point of contact of this activity is the TSB Director. • ITU Member States. The ITU exists as an intergovernmental organization among sovereign States who are signatories to the ITU Constitution and Convention. (Minneapolis, 1998). The point of contact for ITU Member States is specified in the ITU Global Directory as the Administration. It is the Member States Administration that agrees to the use of specific Assigned Country Codes for International Public Telecommunication Networks pursuant to Rec. E.164. • ENUM Service Providers, Users, and Subscribers. In the USA, these are private-sector parties who are providing and using unregulated enhanced services in the marketplace using the ENUM protocol. This also includes includes special E.164 codes. The provisioning arrangements for these services in designated zone E164.foo for the USA have not been determined by the FCC.

4. Creating and Supporting Entries* in the E164.foo designated ENUM Zone • The E164.foo zone administrator will provide for the creation, operation, and maintenance of primary and secondary Internet DNS nameservers with a satisfactory level of performance capable of resolving ITU-T Rec. E.164 Country Codes for Networks registered with the E164.foo administrator in accordance with the procedures described below. • Any party seeking to create a Country Code subdomain in the E164.foo DNS domain should submit a request to the E164.foo administrator contact in accordance with procedures established by the E164.foo administrator , describing the national authorization and implementation details for instantiating the ITU-T Rec. E.164 Assigned Country Code in the E164.foo domain • The E164.foo administrator will • Notify the IANA • Verify - using ITU TSB information compiled in collaboration with WP2/1 - notification of expressed intent by the relevant country administration to participate in ENUM E164.foo designated zone service, or • Contact the designated administration contact in the ITU Global Directory for further advice • Within one week, the IANA contact will review the request and submit its advice concerning the request to the E164.foo administrator contact. • If the E164.foo administrator proceeds with the request, it shall obtain additional necessary relevant information from the requesting party, as well as effect a contractual agreement with the party specifying terms and conditions of the instantiation • The agreement should provide for necessary levels of service and specify the administrator’s liabilities • All administrative procedures for creating and supporting entities in the e164.foo zone shall be established through a fully open and transparent process among the parties * That is, the zone file records that point to the proper nameservers for the presumably multiple Tier1 zones supporting country code 1