Changes

== Deployment of DNSSEC ==

== Deployment of DNSSEC ==

In April 2008, PIR submitted a request to ICANN to amend the .org registry, specifically the function of the registry and the corresponding [[Whois]] and [[DNS]] systems for the .org gTLD, in order to facilitate the use of "Domain Name System Security Extensions" ([[DNSSEC]]) as specified in RFCs 4033, 4034, 4035 and 5155 (NSEC3).<ref>http://www.icann.org/en/registries/rsep/pir-request-03apr08.pdf</ref> The ICANN board approved this proposal in June 2008.<ref>http://www.icann.org/en/minutes/resolutions-26jun08.htm#_Toc76113176</ref>

In April, 2008, PIR submitted a request to ICANN to amend the .org registry, specifically the function of the registry and the corresponding [[Whois]] and [[DNS]] systems for the .org gTLD, in order to facilitate the use of "Domain Name System Security Extensions" ([[DNSSEC]]) as specified in RFCs 4033, 4034, 4035 and 5155.<ref>[http://www.icann.org/en/registries/rsep/pir-request-03apr08.pdf ICANN.org]</ref> The ICANN board approved this proposal in June, 2008.<ref>http://www.icann.org/en/minutes/resolutions-26jun08.htm#_Toc76113176</ref>

On June 23, 2010, Ms. Alexa Raad, PIR CEO, announced at an ICANN 38 Brussels press conference that .org has become the first generic top-level domain to offer full deployment of [[DNSSEC]]. The DNSSEC has become the most robust security protocol on the internet as of 2010, and registrars who have implemented DNSSEC in their system can "offer added security protection to their customers by enabling .org website owners to sign their respective domain name with validation keys."<ref>http://www.pir.org/pdf/dashboard_1H_2010.pdf</ref>

On June 23, 2010, Ms. [[Alexa Raad]], PIR's CEO at that time, announced at an ICANN 38 Brussels press conference that .org has become the first generic top-level domain to offer full deployment of [[DNSSEC]]. DNSSEC had become the most robust security protocol on the internet as of 2010, and registrars who have implemented DNSSEC in their system can "offer added security protection to their customers by enabling .org website owners to sign their respective domain name with validation keys".<ref>http://www.pir.org/pdf/dashboard_1H_2010.pdf</ref>

The benefit of DNSSEC to a .org registrant is the "added ability to thwart the increased predominance of attacks like pharming, cache poisoning, [[DNS]] redirection and domain hijacking - all of which have been used to commit fraud, distribute malware and identity theft."<ref>http://www.pir.org/pdf/dashboard_1H_2010.pdf</ref>

The benefit of DNSSEC to a .org registrant is the "added ability to thwart the increased predominance of attacks like pharming, cache poisoning, [[DNS]] redirection and domain hijacking - all of which have been used to commit fraud, distribute malware and identity theft."<ref>http://www.pir.org/pdf/dashboard_1H_2010.pdf</ref>