<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] Proposal To Sign the Root Zone Made Public
- To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
- Subject: [council] Proposal To Sign the Root Zone Made Public
- From: Glen de Saint Géry <Glen@xxxxxxxxx>
- Date: Fri, 10 Oct 2008 00:50:33 -0700
- Accept-language: fr-FR, en-US
- Acceptlanguage: fr-FR, en-US
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AckqrN+vRQfMSyMASdemg1I3KRaZsA==
- Thread-topic: Proposal To Sign the Root Zone Made Public
[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org]
[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org]
[To: regional-liaisons[at]icann.org]
Proposal To Sign the Root Zone Made Public
http://www.icann.org/en/announcements/announcement-2-09oct08-en.htm
9 October 2008
A proposal [PDF, 276K]
http://www.icann.org/en/announcements/dnssec-proposal-09oct08-en.pdf
to sign the root zone file with Domain Name System Security Extensions, or
DNSSEC, technology was released by ICANN today.
DNSSEC provides a way for software to validate that Domain Name System (DNS)
data have not been modified during Internet transit. This is done by
incorporating public-private signature key pairs into the DNS hierarchy to form
a chain of trust originating at the root zone. Importantly, DNSSEC is not a
form of encryption. It is backward compatible with existing DNS, leaving
records as they are - unencrypted. DNSSEC ensures record integrity through the
use of digital signatures that attest to their authenticity.
This proposal has been written by ICANN staff, as authorized by ICANN's Board,
with the goal to proceed with appropriate speed and deploy DNSSEC at the root
level as a step towards improving the overall security of the DNS.
"The proposal has already been reviewed by a group of global DNSSEC experts.
The feedback ICANN received from this group indicates that the proposal is
technically sound, and appropriate" ICANN's President and CEO Paul Twomey said.
At the core of DNSSEC is the concept of a 'chain of trust'. ICANN's proposal
builds on that notion and, based on security advice, recommends that the entity
responsible for making changes, additions and deletions to the root zone file
and confirming those changes are valid (ICANN presently performs this function
- called the IANA function - under contract from the United States Department
of Commerce), should generate and digitally sign the resulting root zone file
update. This signed file should then be passed to another organization
(presently VeriSign Corporation) for distribution. In other words, the
organization responsible for the initial basis of trust - validating root zone
changes with top level domain operators - should also authenticate the validity
of the final product before it is distributed.
The release occurs as the United States Department of Commerce also announced a
Notice of Inquiry on the concept of signing the Root Zone. Details can be found
here: http://edocket.access.gpo.gov/2008/pdf/E8-23974.pdf [PDF, 72K].
"ICANN has more than a year of experience in producing a signed root zone that
has already been widely tested by DNS software vendors and the interested
DNSSEC community. ICANN also has "built-in" the participation of a group of
world-class DNS experts" Dr Twomey said.
"This is a moment of challenge and opportunity in addressing the overall
stability and security of the DNS system - the mission around which ICANN was
formed" he added.
A set of questions and answers
http://www.icann.org/en/announcements/dnssec-qaa-09oct08-en.htm
on what DNSSEC is and why it is important is also published to assist with the
reading of the proposal.
Glen de Saint Géry
GNSO Secretariat
gnso.secretariat@xxxxxxxxxxxxxx
http://gnso.icann.org
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|