<html><body> <ul> We agree with the RIPE letter and proposals on designing of signing the DNS root zone. We wait with impatience testing activities for DNSSEC</ul> Best regards, Head of Operators' VAS department OAO "VimpelCom" Nataliya V. Romashova loc. 09 53395 tel. +7 495-961-31-86 #53395 tel. +7(495)743-01-70 fax. +7(495)985-95-55 e-mail: rom@beeline.ru <img width="16" height="16" src="cid:1__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt="Inactive hide details for Dmitry Burkov <dburk@burkov.aha.ru>">Dmitry Burkov <dburk@burkov.aha.ru> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr valign="top"><td style="background-image:url(cid:2__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru); background-repeat: no-repeat; " width="40%"> <ul> <ul> <ul> <ul>Dmitry Burkov <dburk@burkov.aha.ru> 19.11.2008 17:56</ul> </ul> </ul> </ul> </td><td width="60%"> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr valign="top"><td width="1%"><img width="73" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""> <div align="right">��</div></td><td width="100%"><img width="1" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""> rom@beeline.ru</td></tr> <tr valign="top"><td width="1%"><img width="73" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""> <div align="right">��</div></td><td width="100%"><img width="1" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""> </td></tr> <tr valign="top"><td width="1%"><img width="73" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""> <div align="right">��</div></td><td width="100%"><img width="1" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""> [Fwd: [regional-russia] RIPE statement to NTIA - need your action - corrected]</td></tr> </table> <table border="0" cellspacing="0" cellpadding="0"> <tr valign="top"><td width="58"><img width="1" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""></td><td width="336"><img width="1" height="1" src="cid:3__=4CBBFF94DFDD8CD08f9e8a93d@abn.beeline.ru" border="0" alt=""></td></tr> </table> </td></tr> </table> <tt> </tt> ----- �� 'Dmitry Burkov <dburk@burkov.aha.ru>' �� 'Wed, 19 Nov 2008 13:18:37 +0300' ----- <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr valign="top"><td width="10%" valign="middle"><div align="right">��:</div></td><td width="90%" valign="middle">regional-russia@ripe.net</td></tr> <tr valign="top"><td width="10%" valign="middle"><div align="right">��:</div></td><td width="90%" valign="middle">[regional-russia] RIPE statement to NTIA - need your action - corrected</td></tr> </table> <tt>�� , �� - � �� - �� �� 9 �� USG DoC NTIA �� DNSSEC. </tt><tt><a href="http://www.ntia.doc.gov/DNS/DNSSEC.html">http://www.ntia.doc.gov/DNS/DNSSEC.html</a></tt><tt> (�� ) �� . �� RIPE �� - �� DNS WG, �� RIPE ��. � �� -�� NTIA. �� �� . �� -�� � ripe-list@ripe.net �� - �� �� . �� �� - � �� : The RIPE community thanks the NTIA for its consultation on proposals to sign the root and is pleased to offer the following response to that consultation. We urge the adoption of a solution that leads to the prompt introduction of a signed root zone. Our community considers the introduction of a signed root zone to be an essential enabling step towards widespread deployment of Secure DNS, DNSSEC. This view is supported by the letter from the RIPE community to ICANN as an outcome of discussions at the May 2007 RIPE meeting in Tallinn: </tt><tt><a href="http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf">http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf</a></tt><tt>. It is to be expected that a community as diverse as RIPE cannot have a unified set of detailed answers to the NTIA questionnaire. However several members of the RIPE community will be individually responding to that questionnaire. We present the following statement as the consensus view of our community about the principles that should form the basis of the introduction of a signed DNS root. �� RIPE �� NTIA �� �� . �� �� . �� �� , �� – �� �� DNSSEC �� DNS. �� RIPE � �� ICANN �� RIPE � ��, �� 2007: </tt><tt><a href="http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf">http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf</a></tt><tt>. ��, �� , �� RIPE, �� �� , �� �� NTIA. �� RIPE �� ��. �� , �� �� (�� DNS) �� , �� �� . 1. Secure DNS, DNSSEC, is about data authenticity and integrity and not about control. 1. DNSSEC �� �� DNS, � �� . 2. The introduction of DNSSEC to the root zone must be made in such a way that it is accepted as a global initiative. 2. �� DNSSEC � �� , �� �� . 3. Addition of DNSSEC to the root zone must be done in a way that does not compromise the security and stability of the Domain Name System. 3. �� DNSSEC � �� ��, �� �� (DNS). 4. When balancing the various concerns about signing the root zone, the approach must provide an appropriate level of trust and confidence by offering an optimally secure solution. 4. �� ��, �� �� . 5. Deployment of a signed root should be done in a timely but not hasty manner. 5. �� ��. 6. Updates from TLD operators relating to DNSSEC should be aligned with the operational mechanisms for co-ordinating changes to the root zone. 6. �� , �� DNSSEC, �� ��, �� . �� �� �� . 7. If any procedural changes are introduced by the deployment of DNSSEC they should provide sufficient flexibility to allow for the roles and processes as well as the entities holding those roles to be changed after suitable consultations have taken place. 7. �� DNSSEC �� , �� �� , �� �� ��, �� , �� . 8. Policies and processes for signing the root zone must be transparent and trustworthy, making it straightforward for TLDs to supply keys and credentials so the delegations for those TLDs can benefit from a common DNSSEC trust anchor, the signed root. 8. �� �� , �� �� , �� �� �� DNSSEC , �� . 9. There is no technical justification to create a new organisation to oversee the process of signing of the root. 9. �� �� . 10. No data should be moved between organisations without appropriate authenticity and integrity checking, particularly the flow of keying material between a TLD operator and the entity that signs the root. 10. �� �� . 11. The public part of the key signing key must be distributed as widely as possible. 11. �� ��, �� . 12. The organisation that generates the root zone file must sign the file and therefore hold the private part of the zone signing key. 12. ��, �� , �� �� (�� ) �� ��. 13. Changes to the entities and roles in the signing process must not necessarily require a change of keys. 13. �� �� . �� Subject: Call for Support: RIPE response to the US NTIA's NoI From: Peter Koch <pk@DENIC.DE> Date: Fri, 14 Nov 2008 23:59:09 +0100 To: ripe-list@ripe.net Dear RIPE Community, as mentioned in my email sent on Monday, the DNS working group has come up with a response to the US NTIA's Notice of Inquiry (NoI) regarding the introduction of DNSSEC for the DNS root zone (for details see <</tt><tt><a href="http://www.ntia.doc.gov/DNS/DNSSEC.html">http://www.ntia.doc.gov/DNS/DNSSEC.html</a></tt><tt>>). The text below reflects the consensus of the DNS working group. As a follow up to our earlier efforts (see below), the DNS WG suggests that the response to the NTIA come from the broader RIPE community. So, this is the DNS WG's request for your support and endorsement of the proposal. Please read the text and voice your support or opposition. As mentioned earlier, we will have to meet an external deadline. Therefore, we are not looking for editorial suggestions. Regrettably, it is impractical to further refine or reword the text, since that would require more editing cycles and new consensus calls, which time won't permit. The WG chairs' collective and the RIPE Chair have agreed that it needs a binary decision on the proposal as presented here. It is possible that the text doesn't represent the optimum for everyone. Still, please consider whether you can support it as a community statement. In any case, the NoI is open for anybody, so you might want to send your individual response and/or contribute to other group efforts, as well. Clarifying questions are welcome, probably best asked on the DNS WG mailing list or to the DNS WG co-chairs <</tt><tt><a href="http://www.ripe.net/ripe/wg/dns/index.html">http://www.ripe.net/ripe/wg/dns/index.html</a></tt><tt>>. Given the 24 Nov deadline and to allow some time for the evalutaion of the list traffic, you are kindly asked to send your explicit statements to this list no later than Friday, 21 Nov 2008 12:00 UTC. Thanks in advance for your consideration! -Peter Koch [DNS WG co-chair] ----------------------------------------------------------------------------- # # $Id: ntia-draft,v 1.9 2008/11/13 20:20:41 jim Exp $ # The RIPE community thanks the NTIA for its consultation on proposals to sign the root and is pleased to offer the following response to that consultation. We urge the adoption of a solution that leads to the prompt introduction of a signed root zone. Our community considers the introduction of a signed root zone to be an essential enabling step towards widespread deployment of Secure DNS, DNSSEC. This view is supported by the letter from the RIPE community to ICANN as an outcome of discussions at the May 2007 RIPE meeting in Tallinn: </tt><tt><a href="http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf">http://www.ripe.net/ripe/wg/dns/icann-root-signing.pdf</a></tt><tt>. It is to be expected that a community as diverse as RIPE cannot have a unified set of detailed answers to the NTIA questionnaire. However several members of the RIPE community will be individually responding to that questionnaire. We present the following statement as the consensus view of our community about the principles that should form the basis of the introduction of a signed DNS root. 1. Secure DNS, DNSSEC, is about data authenticity and integrity and not about control. 2. The introduction of DNSSEC to the root zone must be made in such a way that it is accepted as a global initiative. 3. Addition of DNSSEC to the root zone must be done in a way that does not compromise the security and stability of the Domain Name System. 4. When balancing the various concerns about signing the root zone, the approach must provide an appropriate level of trust and confidence by offering an optimally secure solution. 5. Deployment of a signed root should be done in a timely but not hasty manner. 6. Updates from TLD operators relating to DNSSEC should be aligned with the operational mechanisms for co-ordinating changes to the root zone. 7. If any procedural changes are introduced by the deployment of DNSSEC they should provide sufficient flexibility to allow for the roles and processes as well as the entities holding those roles to be changed after suitable consultations have taken place. 8. Policies and processes for signing the root zone must be transparent and trustworthy, making it straightforward for TLDs to supply keys and credentials so the delegations for those TLDs can benefit from a common DNSSEC trust anchor, the signed root. 9. There is no technical justification to create a new organisation to oversee the process of signing of the root. 10. No data should be moved between organisations without appropriate authenticity and integrity checking, particularly the flow of keying material between a TLD operator and the entity that signs the root. 11. The public part of the key signing key must be distributed as widely as possible. 12. The organisation that generates the root zone file must sign the file and therefore hold the private part of the zone signing key. 13. Changes to the entities and roles in the signing process must not necessarily require a change of keys. ----------------------------------------- </tt> </body></html>