9,082
edits
Changes
→Root Zone Operational Changes
==Root Zone Operational Changes==
==Root Zone Operational Changes==
On February 3, 2009, the [[ICANN Board]] enumerated the upcoming operational changes that will be implemented in the [[DNS]] root zone such as the addition of [[IPv6]] records to the root, new generic top level domains ([[gTLD]]s), new country code Internationalized Domain Names ([[cc IDN]]s), [[IDN]]s, and the implementation of [[DNSSEC]]. In connection to the anticipated root zone operational changes, the Board requested Security and Stability Advisory Committee ([[SSAC]]) and Root Server System Advisory Committee ([[RSSAC]]) to hold a joint study to analyze its impact to the stability and security to the DNS root server system. Furthermore, the Board reques ed 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 will also 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 that will be implemented in the [[DNS]] root zone such as the addition of [[IPv6]] records to the root, new generic top level domains ([[gTLD]]s), new country code Internationalized Domain Names ([[cc IDN]]s), [[IDN]]s, and the implementation of [[DNSSEC]]. In connection to the anticipated root zone operational changes, the Board requested Security and Stability Advisory Committee ([[SSAC]]) and Root Server System Advisory Committee ([[RSSAC]]) to hold a joint study to analyze its impact to the stability and security to the DNS root server system. Furthermore, the Board reques ed 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 will also take part in the study.<ref>[http://www.icann.org/en/minutes/prelim-report-03feb09.htm ICANN Special Board Meeting]</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.
* 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 a group of resource record.Implementation of the DNSSEC will result to 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 inquiries to the DNS will needs more bandwidth network resources and the signature data's 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.
* 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.
==References==
==References==