Changes

'''Root Zone''' refers to the highest level of the [[DNS|Domain Name System]] (DNS) structure. It contains the names and the numeric IP addresses for all the top level domain names such as the [[gTLD]]s ([[.com]], [[.net]], [[.org]]), including [[new gTLD]]s ([[.xyz]], [[.club]], [[.google]]), as well [[CcTLD|ccTLD]]s ([[.us]], [[.uk]], [[.ar]]) and [[IDN]]s ([[.在线]], [[.عرب]], [[.संगठन]]) in the root zone file.<ref>[http://www.isoc.org/briefings/019/ www.isoc.org]</ref>

'''Root Zone''' refers to the highest level of the [[DNS|Domain Name System]] (DNS) structure. It contains the names and the numeric IP addresses for all the top level domain names such as the [[gTLD]]s ([[.com]], [[.net]], [[.org]], [[.jobs]]), and all the country code top level domains ([[ccTLD]]s), for example ([[.us]], [[.uk]] [[.ph]]), including the entire list of all the root servers.<ref>[http://www.isoc.org/briefings/019/ www.isoc.org]</ref>

The DNS root zone contains only 280 delegations of generic, country code and internationalized [[TLD|top level domain names]] (TLD)s and its size is more or less 80,000 bytes. It also changes slowly and absorbs only one minor change per TLD every year.<ref>

The DNS root zone contains over 1,500 gTLDs, ccTLDs and IDNs that are delegated to the Root Zone Database.<ref>

[http://www.icann.org/en/committees/dns-root/root-scaling-study-report-31aug09-en.pdf Scaling the Root]</ref>

[http://www.iana.org/domains/root/db IANA Root Zone Database]</ref>

==Root Zone Management Process==

==Root Zone Management Process==  

The [[NTIA|National Telecommunications Information Administration]] (NTIA), [[ICANN]], [[Verisign]] and the [[Root Server Operators]] play significant roles in the management and process of the root zone.  

The [[NTIA|National Telecommunications Information Administration]] (NTIA), [[ICANN]], [[Verisign]] and the [[Root Server Operators]] play significant roles in the management and process of the root zone.  

Verisign, and formerly [[Network Solutions]], serves as the root zone administrator under a cooperative agreement entered with the United States government; this has been in effect since 1998.

Verisign, and formerly [[Network Solutions]], serves as the root zone administrator under a cooperative agreement entered with the United States government; this has been in effect since 1998.

The [[Root Server Operators]]' primary role is to make sure that the operations of the root zone is always accurate, available, reliable and secure. There are thirteen 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 is 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>

* A - [[Verisign]] Global Registry Services

* A/J - [[Verisign]] Global Registry Services

* B - [[Information Sciences Institute]]

* B - [[Information Sciences Institute]]

* C - [[Cogent Communications]]

* C - [[Cogent Communications]]

* M - [[WIDE Project]]

* M - [[WIDE Project]]

==Root Zone Operational Changes==

==Root Zone Operational Changes==  

On February 3, 2009, the [[ICANN Board]] enumerated the upcoming operational changes to be implemented in the [[DNS]] root zone, such as the addition of [[IPv6]] records to the root, new [[generic top level domains]] (gTLDs), new [[IDN|Internationalized Domain Names]], and the implementation of [[DNSSEC]]. In connection to the anticipated root zone operational changes, the Board requested  the [[SSAC|Security and Stability Advisory Committee]] (SSAC) and [[RSSAC|Root Server System Advisory Committee]] (RSSAC) to conduct a joint study to analyze its impact to the stability and security to the DNS root server system. Furthermore, the Board requested both the committees to identify the capacity and scaling of the root server system to be able to solve any  technical and operational challenges that might take place when the proposed changes are implemented. Some [[ICANN]] senior technical staff were also to take part in the study.<ref>[http://www.icann.org/en/minutes/prelim-report-03feb09.htm ICANN Special Board Meeting]</ref>

On February 3, 2009, the [[ICANN Board]] enumerated the upcoming operational changes to be implemented in the [[DNS]] root zone, such as the addition of [[IPv6]] records to the root, new [[gTLD|generic top level domains]] (gTLDs), new [[IDN|Internationalized Domain Names]], and the implementation of [[DNSSEC]]. In connection to the anticipated root zone operational changes, the Board requested  the [[SSAC|Security and Stability Advisory Committee]] (SSAC) and [[RSSAC|Root Server System Advisory Committee]] (RSSAC) to conduct a joint study to analyze its impact to the stability and security to the DNS root server system. Furthermore, the Board requested both the committees to identify the capacity and scaling of the root server system to be able to solve any  technical and operational challenges that might take place when the proposed changes are implemented. Some [[ICANN]] senior technical staff were also to take part in the study.<ref>[http://www.icann.org/en/minutes/prelim-report-03feb09.htm ICANN Special Board Meeting]</ref>

==Root Scaling Study Report==

==Root Scaling Study Report==  

The SSAC, RSSAC and ICANN Staff responded to the request of the ICANN Board by creating a Scaling Steering Group to conduct the study. On September 7, 2009, a report entitled: Report on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone was submitted by the Root Scaling Study Team for the Scaling Steering Group with the following findings and recommendations:<ref>[http://www.icann.org/en/committees/dns-root/root-scaling-study-report-31aug09-en.pdf Root Scaling Study Report]</ref>

The SSAC, RSSAC and ICANN Staff responded to the request of the ICANN Board by creating a Scaling Steering Group to conduct the study. On September 7, 2009, a report entitled: Report on the Impact on the DNS Root System of Increasing the Size and Volatility of the Root Zone was submitted by the Root Scaling Study Team for the Scaling Steering Group with the following findings and recommendations:<ref>[http://www.icann.org/en/committees/dns-root/root-scaling-study-report-31aug09-en.pdf Root Scaling Study Report]</ref>

* Any of the proposed changes has an effect to the growth of the root zone. The study team suggested that it is best to add or make changes to the root zone with a large or sudden impact. Gradual changes can be added at later stages.

* Any of the proposed changes has an effect to the growth of the root zone. The study team suggested that it is best to add or make changes to the root zone with a large or sudden impact. Gradual changes can be added at later stages.

* Additional new TLDs will increase both the number of entries and the size of the root zone, however an increase in the number of TLDs will not increase the number of request per year per TLD.

* Additional new TLDs will increase both the number of entries and the size of the root zone, however an increase in the number of TLDs will not increase the number of request per year per TLD.

* Adding DNSSEC changes the nature of the root zone wherein it will no longer be an atomic unit or an individual resource record, instead it will be a group resource record. Implementation of DNSSEC will result in a much bigger amount of data carried in the zone as well as larger zone transfers. Signature and other security related data will will added to queries to the DNS, and thus it needs more bandwidth network resources and the signature data needs to be regularly updated because they have expiration dates to avoid serving bad data and to avoid replay attacks.

* Adding DNSSEC changes the nature of the root zone wherein it will no longer be an atomic unit or an individual resource record, instead it will be a group resource record. Implementation of DNSSEC will result in a much bigger amount of data carried in the zone as well as larger zone transfers. Signature and other security related data will be added to queries to the DNS, and thus it needs more bandwidth network resources and the signature data needs to be regularly updated because they have expiration dates to avoid serving bad data and to avoid replay attacks.

* Additional IDN results to changes in the root zone similar to adding a TLD.

* Additional IDN results to changes in the root zone similar to adding a TLD.

* 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.

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}}

[[Category:Glossary]]

[[Category:Glossary]]