Root Zone: Difference between revisions
Dustin Loup (talk | contribs) No edit summary |
Applied modification ruleset: Automated workflow |
||
| (12 intermediate revisions by 4 users not shown) | |||
| Line 5: | Line 5: | ||
==Root Zone Management Process== | ==Root Zone Management Process== | ||
[[ICANN]], [[Verisign]] and the [[Root Server Operators]] play significant roles in the management and process of the root zone. | |||
ICANN is the operator of the [[IANA|Internet Assigned Numbers Authority]] (IANA), which is responsible for the day-to-day management of the DNS root zone. IANA assigns the operators of the top level domain and ensures the maintenance and the administrative details of the TLDs.<ref>RFC 1591</ref><ref>[http://www.iana.org/domains/root/ Root Zone Management]</ref> It is also responsible for the coordination of the [[IP|Internet Protocol]] (IP) and [[ASN|Autonomous System Numbers]] (ASN) to the [[RIR|Regional Internet Registries]] (RIR). | |||
Verisign, and formerly [[Network Solutions]], serves as the root zone administrator. | |||
The [[Root Server Operators]]' primary role is to make sure that the operations of the root zone are always accurate, available, reliable, and secure. There are twelve Root Server Operators in the database of the root zone, which include:<ref>[http://www.isoc.org/briefings/019/ Root Server Operators]</ref> | |||
The [[Root Server Operators]]' primary role is to make sure that the operations of the root zone | |||
* A/J - [[Verisign]] Global Registry Services | * A/J - [[Verisign]] Global Registry Services | ||
* B - [[Information Sciences Institute]] | * B - [[University of Southern California – Information Sciences Institute|USC ISI]] | ||
* C - [[Cogent Communications]] | * C - [[Cogent Communications]] | ||
* D - [[University of Maryland]] | * D - [[University of Maryland – ACIGS]] | ||
* E - [[NASA Ames Research Center]] | * E - [[NASA Ames Research Center]] | ||
* F - [[ISC|Internet Systems Consortium, Inc.]] | * F - [[ISC|Internet Systems Consortium, Inc.]] | ||
* G - [[ | * G - [[Defense Information Systems Agency]] | ||
* H -[[ U.S. Army Research Lab]] | * H -[[ U.S. Army Research Lab]] | ||
* I - [[Autonomica | * I - [[Netnod | Autonomica/NORDUnet]] | ||
* K - [[RIPE NCC]] | * K - [[RIPE NCC]] | ||
* L - [[ICANN]] | * L - [[ICANN]] | ||
| Line 39: | Line 37: | ||
* Adding IPv6 records to the root zone will add glue records for the name server of every TLD. This means that the amount of data increases per TLD in the root zone and the number of changes per TLD will also increase each year. | * Adding IPv6 records to the root zone will add glue records for the name server of every TLD. This means that the amount of data increases per TLD in the root zone and the number of changes per TLD will also increase each year. | ||
The Root Scaling Study Team also found that the proposed changes to the root also affect the end-system applications of the Internet such as the web browsers, intermediary “middleboxes” that perform traffic shaping, firewall, and caching functions; and [[ISP]]s that manage the DNS services provided to | The Root Scaling Study Team also found that the proposed changes to the root also affect the end-system applications of the Internet such as the web browsers, intermediary “middleboxes” that perform traffic shaping, firewall, and caching functions; and [[ISP]]s that manage the DNS services provided to Internet users. | ||
In addition, the team also recommended further study of how to detect the important signs of stress or problems in root zone management, and how to arrange communication between the individuals primary involved in the root zone management system to ensure that timely intelligence support and effective cooperative action are available and resolve the effects of discontinuities before causing further problems. | In addition, the team also recommended further study of how to detect the important signs of stress or problems in root zone management, and how to arrange communication between the individuals primary involved in the root zone management system to ensure that timely intelligence support and effective cooperative action are available and resolve the effects of discontinuities before causing further problems. | ||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||