<font size="4">Gentle reminder for all and especially Governments. </font><font size="4"><span style="background-color: rgb(255, 255, 0);">DATES: Comments are due on or before March 31, 2011.</span></font>
<font size="4"><br><br>Questions are welcome and I am available via the above email.<br>best<br>AR<br></font><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Anne-Rachel Inné</b> <span dir="ltr"><<a href="mailto:annerachel@gmail.com">annerachel@gmail.com</a>></span><br>
Date: 2011/3/2<br>Subject: Request for Comments on the Internet Assigned Numbers Authority (IANA) Functions<br>To: <a href="mailto:africann@afrinic.net">africann@afrinic.net</a><br><br><font size="4"><br><a href="http://edocket.access.gpo.gov/2011/2011-4240.htm" target="_blank">http://edocket.access.gpo.gov/2011/2011-4240.htm</a><br>
<br>
[Federal Register: February 25, 2011 (Volume 76, Number 38)]</font>
<font size="4"><br>
[Notices]<br>
[Page 10569-10571]<br>
>From the Federal Register Online via GPO Access [<a href="http://wais.access.gpo.gov" target="_blank">wais.access.gpo.gov</a>]<br>
[DOCID:fr25fe11-35]<br><br>
------------------------------</font>
<font size="4">------------------------------</font><font size="4">-----------<br><br>
DEPARTMENT OF COMMERCE</font>
<font size="4"><br><br>
National Telecommunications and Information Administration</font>
<font size="4"><br><br>
[Docket No. 110207099-1099-01]</font>
<font size="4"><br>
RIN 0660-XA23<br><br><br>
Request for Comments on the Internet Assigned Numbers Authority</font>
<font size="4"><br>
(IANA) Functions<br><br>
AGENCY: National Telecommunications and Information Administration,</font>
<font size="4"><br>
U.S. Department of Commerce.<br><br>
ACTION: Notice of Inquiry.</font>
<font size="4"><br><br>
------------------------------</font>
<font size="4">------------------------------</font><font size="4">-----------<br><br>
SUMMARY: The United States Department of Commerce's National</font>
<font size="4"><br>
Telecommunications and Information Administration (NTIA) remains<br>
committed to preserving a stable and secure Internet Domain Name System<br>
(DNS). Critical to the DNS is the continued performance of the Internet<br>
Assigned Numbers Authority (IANA) functions. The IANA functions have<br>
historically included: (1) The coordination of the assignment of<br>
technical Internet protocol parameters; (2) the administration of<br>
certain responsibilities associated with Internet DNS root zone<br>
management; (3) the allocation of Internet numbering resources; and (4)<br>
other services related to the management of the .ARPA and .INT top-<br>
level domains. The Internet Corporation for Assigned Names and Numbers<br>
(ICANN) currently performs the IANA functions, on behalf of the United<br>
States Government, through a contract with NTIA. Given the September<br>
30, 2011 expiration of this contract, NTIA is seeking public comment to<br>
enhance the performance of the IANA functions in the development and<br>
award of a new IANA functions contract.<br><br>
<span style="background-color: rgb(255, 255, 0);">DATES: Comments are due on or before March 31, 2011.</span></font>
<font size="4"><br><br>
ADDRESSES: Written comments may be submitted by mail to Fiona M.</font>
<font size="4"><br>
Alexander, Associate Administrator, Office of International Affairs,<br>
National Telecommunications and Information Administration, 1401<br>
Constitution Avenue, NW., Room 4701, Washington, DC 20230. Paper<br>
submissions should include a three and one-half inch computer diskette<br>
in HTML, ASCII, Word or WordPerfect format (please specify version).<br>
Diskettes should be labeled with the name and organizational<br>
affiliation of the filer, and the name of the word processing program<br>
used to create the document. Alternatively, comments may be submitted<br>
electronically to <a href="mailto:IANAFunctions@ntia.doc.gov">IANAFunctions@ntia.doc.gov</a>. Comments provided via<br>
electronic mail should also be submitted in one or more of the formats<br>
specified above. Comments will be posted to NTIA's Web site at http://<br><a href="http://www.ntia.doc.gov/ntiahome/domainname/IANAFunctions.html" target="_blank">www.ntia.doc.gov/ntiahome/domainname/IANAFunctions.html</a></font>
<font size="4">.<br><br>
FOR FURTHER INFORMATION CONTACT: For questions about this Notice</font>
<font size="4"><br>
contact: Vernita D. Harris, National Telecommunications and Information<br>
Administration, U.S. Department of Commerce, 1401 Constitution Avenue,<br>
NW., Room 4701, Washington, DC 20230; telephone: (202) 482-4686; e-<br>
mail: <a href="mailto:vharris@ntia.doc.gov">vharris@ntia.doc.gov</a>. Please direct media inquiries to the Office<br>
of Public Affairs, NTIA, at (202) 482-7002.<br><br>
SUPPLEMENTARY INFORMATION: The Internet Assigned Numbers Authority</font>
<font size="4"><br>
(IANA) functions were initially performed under a series of contracts<br>
between the Department of Defense's Advanced Research Projects Agency<br>
(DARPA) and the University of Southern California (USC), as part of a<br>
research project known as the Terranode Network Technology (TNT). As<br>
the TNT project and the DARPA/USC contract neared completion, the<br>
United States Government recognized the need for the continued<br>
performance of the IANA functions as vital to the stability and correct<br>
functioning of the Internet. In January 1999, NTIA initiated a<br>
procurement process to fulfill this need.\1\ NTIA awarded the IANA<br>
functions contract to ICANN in February 2000, and subsequently in March<br>
2001, March 2004, and August 2005.\2\ The current contract expires<br>
September 30, 2011.\3\ Given this impending expiration, NTIA is issuing<br>
this Notice of Inquiry (NOI) to seek public comment to inform the<br>
procurement process, leading to the award of a new IANA functions<br>
contract. We take this opportunity to ask a detailed set of questions<br>
on this topic as this is the first time NTIA has undertaken a<br>
comprehensive review of the IANA functions contract since the award of<br>
the first contract in 2000.<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
\1\ To assist in this transition from the DARPA contract with<br>
USC to ICANN, in 1998, ICANN entered into an agreement with the<br>
University of Southern California Information Sciences Institute<br>
(USC/ISI) to transition certain functions, responsibilities, assets,<br>
and personnel to ICANN.<br>
\2\ Each contract and modifications are available at http://<br><a href="http://www.ntia.doc.gov/ntiahome/domainname/iana.htm" target="_blank">www.ntia.doc.gov/ntiahome/domainname/iana.htm</a></font>
<font size="4">.<br>
\3\ The current contract has an option to extend the performance<br>
period for an additional six months. If necessary, NTIA will<br>
exercise this option in order to complete the contract procurement<br>
process. See Contract Clause 1.5 of the current contract, which can<br>
be viewed at <a href="http://www.ntia.doc.gov/ntiahome/domainname/iana/" target="_blank">http://www.ntia.doc.gov/ntiahome/domainname/iana/</a><br>
ianacontract_081406.pdf.<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
The domain name system (DNS) is a critical component of the<br>
Internet that works like an address book, allowing users to reach<br>
websites using easy-to-understand domain names (e.g., http://<br><a href="http://commerce.gov" target="_blank">commerce.gov</a></font>
<font size="4">) rather than the numeric network server addresses (e.g.,<br><a href="http://170.110.225.168" target="_blank">http://170.110.225.168</a></font>
<font size="4">) necessary to retrieve information on the<br>
Internet. It is a hierarchical and globally distributed system in which<br>
distinct servers maintain the detailed information for their local<br>
domains and pointers for how to navigate the hierarchy to retrieve<br>
information from other domains. The accuracy, integrity, and<br>
availability of the information supplied by the DNS are essential to<br>
the operation of most systems, services, or applications that use the<br>
Internet.<br>
Essential to the DNS is the performance of the IANA functions. At a<br>
summary level, the IANA functions include: (1) The coordination of the<br>
assignment of technical Internet protocol parameters; (2) the<br>
administration of certain responsibilities associated with Internet DNS<br>
root zone management; (3) the allocation of Internet numbering<br>
resources; and (4) other services related to the management of the<br>
.ARPA and .INT top-level domains. A more detailed description of each<br>
of the IANA functions follows.<br>
The first of the IANA functions is the coordination of the<br>
assignment of technical protocol parameters. This function includes the<br>
review and assignment of unique values to numerous parameters (e.g.,<br>
operation codes, port numbers, object identifiers, protocol numbers)<br>
used in various Internet protocols. This function also includes<br>
dissemination of listings of assigned parameters through various means<br>
(including on-line publication) and the review of technical documents<br>
for consistency with assigned values.<br><br>
[[Page 10570]]</font>
<font size="4"><br><br></font>
<font size="4">
The second function is the administration of certain<br>
responsibilities associated with Internet DNS root zone management. It<br>
includes receiving requests for and making routine updates of the top-<br>
level domain contact, nameserver and DS record information. This<br>
function also includes receiving delegation and redelegation requests,<br>
investigating the circumstances pertinent to those requests, and making<br>
recommendations and reporting actions undertaken in connection with<br>
processing requests.\4\ Additionally, this function involves certain<br>
responsibilities related to DNSSEC operation at the root, including<br>
management of the root zone Key Signing Key (KSK).\5\<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
\4\ Performance of this function in relation to country code top<br>
level domains (ccTLDs) has evolved over time to address specific<br>
issues, one of which has been how best to respect the legitimate<br>
interests of governments in the management of their respective ccTLD<br>
within the current model.<br>
\5\ At present, the process flow for root zone management (see<br>
diagram at <a href="http://www.ntia.doc.gov/DNS/CurrentProcessFlow.pdf" target="_blank">http://www.ntia.doc.gov/DNS/CurrentProcessFlow.pdf</a>)<br>
involves three roles that are performed by different entities<br>
through two separate legal agreements with NTIA. The process itself<br>
includes the following steps: (1) TLD operators submit change<br>
requests to the IANA Functions Operator; (2) the IANA Functions<br>
Operator processes the request and conducts due diligence in<br>
verifying the request; (3) the IANA Functions Operator sends a<br>
recommendation regarding the request to the Administrator for<br>
verification/authorization; (4) the Administrator verifies that the<br>
IANA Functions Operator has followed its agreed upon verification/<br>
processing policies and procedures; (5) the Administrator authorizes<br>
the Root Zone Maintainer to make the change; (6) the Root Zone<br>
Maintainer edits and generates the updated root zone file; and (7)<br>
the Root Zone Maintainer distributes the updated root zone file to<br>
the thirteen (13) root server operators. Currently, ICANN performs<br>
the role of the IANA Functions Operator, NTIA performs the role of<br>
Administrator, and VeriSign performs the role of Root Zone<br>
Maintainer. NTIA's agreements with ICANN (IANA functions contract)<br>
and VeriSign, Inc. (Cooperative Agreement) provide the process<br>
through which changes are currently made to the authoritative root<br>
zone file.<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
The third function involves responsibilities for allocated and<br>
unallocated IPv4 and IPv6 address space and Autonomous System Number<br>
(ASN) space, including the delegation of IP address blocks to Regional<br>
Internet Registries (RIRs) for routine allocation. This function also<br>
includes reservation and direct allocation of space for special<br>
purposes, such as multicast addressing, addresses for private networks<br>
and globally specified applications.<br>
Other services related to the performance of the IANA functions<br>
include the management of .ARPA and .INT top-level domains.<br>
The responsibilities encompassed within the IANA functions require<br>
cooperation and coordination with a variety of technical groups and<br>
stakeholder communities. For example, protocol parameters are developed<br>
through and overseen by groups such as the Internet Engineering Task<br>
Force (IETF) and the Internet Architecture Board (IAB), policies and<br>
procedures associated with Internet DNS root zone management are<br>
developed by a variety of actors (e.g., the Internet technical<br>
community, ccTLD operators, and governments) and continue to evolve,<br>
and policies and procedures related to Internet numbering resources are<br>
developed within the RIRs. NTIA is cognizant and respectful of the<br>
policy and technical standards development roles these organizations,<br>
their constituencies, and other relevant Internet community<br>
stakeholders play.<br>
NTIA recognizes that the IANA Functions Operator, in the<br>
performance of its duties, requires close constructive working<br>
relationships with interested and affected parties if it is to ensure<br>
quality performance of the IANA functions. Applicable to each of these<br>
functions and their performance are relevant policies, technical<br>
standards, and procedures developed and administered outside the<br>
purview of the IANA functions contract.<br>
Given the importance of the Internet as a global medium supporting<br>
economic growth and innovation, continuing to preserve the security and<br>
stability of the Internet DNS remains a top priority for NTIA. This is<br>
a shared responsibility among all stakeholders in the Internet<br>
community. Currently, the IANA Functions Operator is required to<br>
operate computing and communications systems in accordance with best<br>
business and security practices. This includes utilizing authenticated<br>
communications between it and its customers. The IANA Functions<br>
Operator is also required to submit annually an IANA functions<br>
information security plan. The annual plan addresses controls that the<br>
IANA Functions Operator has employed to ensure the confidentiality,<br>
integrity and availability of the IANA functions processes and<br>
information assets. Additionally, the IANA Functions Operator is<br>
required to submit monthly performance reports. The monthly reports<br>
contain statistical and narrative information on the performance of the<br>
IANA functions (i.e., assignment of technical protocol parameters;<br>
administrative functions associated with root zone management; and<br>
allocation of internet numbering resources) for the previous 30<br>
days.\6\<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
\6\ For reports on IANA functions activities see: http://<br><a href="http://www.iana.org/reports" target="_blank">www.iana.org/reports</a></font>
<font size="4"> and <a href="https://charts.icann.org/public/index-iana-%0Amain.html" target="_blank">https://charts.icann.org/public/index-iana-<br>
main.html</a>.<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
Request for Comment: The current IANA functions contract will<br>
expire on September 30, 2011. Given the impending expiration of this<br>
contract, NTIA is seeking public comment to enhance the performance of<br>
the IANA functions. These comments will be considered in the<br>
procurement process to award a new IANA functions contract.<br>
Comments that contain references, studies, research, and other<br>
empirical data that are not widely published should include copies of<br>
the referenced materials with the submitted comments.<br>
1. The IANA functions have been viewed historically as a set of<br>
interdependent technical functions and accordingly performed together<br>
by a single entity. In light of technology changes and market<br>
developments, should the IANA functions continue to be treated as<br>
interdependent? For example, does the coordination of the assignment of<br>
technical protocol parameters need to be done by the same entity that<br>
administers certain responsibilities associated with root zone<br>
management? Please provide specific information to support why or why<br>
not, taking into account security and stability issues.<br>
2. The performance of the IANA functions often relies upon the<br>
policies and procedures developed by a variety of entities within the<br>
Internet technical community such as the IETF, the RIRs and ccTLD<br>
operators. Should the IANA functions contract include references to<br>
these entities, the policies they develop and instructions that the<br>
contractor follow the policies? Please provide specific information as<br>
to why or why not. If yes, please provide language you believe<br>
accurately captures these relationships.<br>
3. Cognizant of concerns previously raised by some governments and<br>
ccTLD operators and the need to ensure the stability of and security of<br>
the DNS, are there changes that could be made to how root zone<br>
management requests for ccTLDs are processed? Please provide specific<br>
information as to why or why not. If yes, please provide specific<br>
suggestions.<br>
4. Broad performance metrics and reporting are currently required<br>
under the contract.\7\ Are the current metrics and reporting<br>
requirements sufficient? Please provide specific information as to why<br>
or why not. If not, what specific changes should be made?<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
\7\ See Appendix A and Appendix B of the current contract, which<br>
can be viewed at <a href="http://www.ntia.doc.gov/ntiahome/domainname/iana/%0Aianacontract_081406.pdf" target="_blank">http://www.ntia.doc.gov/ntiahome/domainname/iana/<br>
ianacontract_081406.pdf</a>.<br>
------------------------------</font><font size="4">------------------------------</font><font size="4">---------------<br><br></font>
<font size="4">
5. Can process improvements or performance enhancements be made to<br><br>
[[Page 10571]]</font>
<font size="4"><br><br>
the IANA functions contract to better reflect the needs of users of the</font>
<font size="4"><br>
IANA functions to improve the overall customer experience? Should<br>
mechanisms be employed to provide formalized user input and/or<br>
feedback, outreach and coordination with the users of the IANA<br>
functions? Is additional information related to the performance and<br>
administration of the IANA functions needed in the interest of more<br>
transparency? Please provide specific information as to why or why not.<br>
If yes, please provide specific suggestions.<br>
6. Should additional security considerations and/or enhancements be<br>
factored into requirements for the performance of the IANA functions?<br>
Please provide specific information as to why or why not. If additional<br>
security considerations should be included, please provide specific<br>
suggestions.<br><br></font>
<font size="4">
Dated: February 22, 2011.<br>
Lawrence E. Strickling,<br>
Assistant Secretary for Communications and Information.<br>
[FR Doc. 2011-4240 Filed 2-24-11; 8:45 am]<br>
BILLING CODE 3510-60-P<br></font>
</div><font size="4"><br></font><br clear="all">