From randy at psg.com Tue Dec 1 00:15:37 2009 From: randy at psg.com (Randy Bush) Date: Tue, 01 Dec 2009 08:15:37 +0900 Subject: [dns-wg] Re: [db-wg] DOMAIN object proposals In-Reply-To: <4B13B6F6.1030300@ripe.net> References: <4B13B6F6.1030300@ripe.net> Message-ID: > Removal of Forward DOMAIN data from the RIPE Database From pk at DENIC.DE Mon Dec 14 14:54:05 2009 From: pk at DENIC.DE (Peter Koch) Date: Mon, 14 Dec 2009 14:54:05 +0100 Subject: [dns-wg] DOMAIN object proposals In-Reply-To: <4B13B6F6.1030300@ripe.net> References: <4B13B6F6.1030300@ripe.net> Message-ID: <20091214135405.GB5987@x27.adm.denic.de> Dear WG, On Mon, Nov 30, 2009 at 01:13:42PM +0100, Denis Walker wrote: > The RIPE NCC made two proposals recently concerning DOMAIN objects: > > 22 October > New rules for reverse domain object creation in the RIPE Database > http://www.ripe.net/ripe/maillists/archives/dns-wg/2009/msg00104.html > > 23 November > Removal of Forward DOMAIN data from the RIPE Database > http://www.ripe.net/ripe/maillists/archives/dns-wg/2009/msg00119.html > > There have been no comments for or against either of these proposals on > the mailing lists. They were both discussed at RIPE Meetings, without > any negative comments. We would like to ask for any final comments by > this Friday, 4 December 2009, so the working group chairs can then draw > a consensus. both proposals have been presented at the latest and previous RIPE meetings. The topic of removal of forward domain objects was also coordinated with the CENTR technical working group due to the TLDs affected. Support was broad with no objections raised. Feedback regarding notifications has been incorporated and the NCC has published a preliminary implementation schedule: >From the perspective of the DNS WG, both proposals have found strong consensus and can move forward. -Peter (for the DNS WG co-chairs) From noreply at ripe.net Wed Dec 16 16:49:20 2009 From: noreply at ripe.net (Andrei Robachevsky) Date: Wed, 16 Dec 2009 16:49:20 +0100 Subject: [dns-wg] RIPE NCC Confirms Commitment to DNSSEC Deployment in the Root Zone Message-ID: <4B290180.1080402@ripe.net> [Apologies for duplicate emails] Dear Colleagues, On 1 December 2009, ICANN and VeriSign began to deploy DNSSEC across the root server system when they signed the root zone using DNSSEC. They noted that the signing would become public from January 2010, when the process of signing each of the 13 root servers in turn would begin. This process will continue until July 2010, when ICANN publishes the root zone trust anchor and root operators begin to serve the signed root zone with actual keys. On 15 December 2009, the root zone DNSSEC deployment team launched a website that provides information about DNSSEC for the root zone: http://www.root-dnssec.org/ The website is a repository for the documentation relating to the deployment of DNSSEC in the root zone, and it includes information such as technical status updates and the full timetable for the deployment of DNSSEC. The RIPE NCC, operator of K-root, confirms its commitment to support the ICANN/VeriSign initiative and coordinate with the other root zone server operators in the deployment of DNSSEC in the root zone. The RIPE NCC also provides data collection and measurements that allows monitoring of the effects the transition has on the overall performance of the root server system. This information is available on RIPE Labs at: http://labs.ripe.net/content/preparing-k-root-signed-root-zone Further details on the RIPE NCC's operation of K-root are available at: http://k.root-servers.org Best regards, Andrei Robachevsky Chief Technical Officer RIPE NCC From anandb at ripe.net Tue Dec 22 11:23:31 2009 From: anandb at ripe.net (Anand Buddhdev) Date: Tue, 22 Dec 2009 11:23:31 +0100 Subject: [dns-wg] RIPE NCC Reply-size Test Application Message-ID: <4B309E23.6030106@ripe.net> Dear Colleagues, The RIPE NCC is pleased to release an application for the purpose of determining the maximum size of DNS responses that a resolver can receive. This application is meant to assist users and network administrators to prepare their networks and resolvers for a signed root zone. To download this application, and learn how to use it, please see the RIPE Labs website: http://labs.ripe.net/content/testing-your-resolver-dns-reply-size-issues If you have any questions or comments, please feel free to post them on the RIPE Labs website. Regards, Anand Buddhdev, DNS Services Manager, RIPE NCC From rickard.bellgrim at iis.se Tue Dec 22 13:30:23 2009 From: rickard.bellgrim at iis.se (Rickard Bellgrim) Date: Tue, 22 Dec 2009 13:30:23 +0100 Subject: [dns-wg] A Review of Administrative Tools for DNSSEC Message-ID: <983F17705339E24699AA251B458249B51F197DE9A0@EXCHANGE2K7.office.nic.se> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi .SE (The Internet Infrastructure Foundation) has together with Certezza produced a report that show the current state of administrative tools for DNSSEC. The report is a summary of the functionality of some leading DNSSEC management tools. The focus of the examination has been on DNSSEC signing and key management functionality. An important part of the work has been to specify a set of user review points. It is our belief that the review points are fairly general and as such can be used in similar reviews in the future. The key finding in the study is that there has been a substantial development of DNSSEC tools during the last year, but in a few areas some improvement work still remains. In general the product standard is good and the tested products work as expected. We hope that this product review facilitates the deployment of DNSSEC and would also encourage others to follow up on this work. Please, read the review here: http://www.iis.se/docs/DNSSEC-Admin-tools-review-1.01.pdf // Rickard Bellgrim -----BEGIN PGP SIGNATURE----- Version: 9.8.3 (Build 4028) Charset: utf-8 wsBVAwUBSzC73+CjgaNTdVjaAQg0oAf+JuByCwfqLWCqje4DV/lg1ih9+9+MAeFe kS2HEEVd2rX0x7z+IjRyYz06U39lQsfeOURl2Eby/nOHc54Anw7TLR8u2zTmDZ68 UFCND/8DY7be6AY6uuvPRLx8L0RUpjRMLZSEjbkECXydmNslejuxZkm5nVVl+EKQ 2oc0BioEZ1uyQuvfT+BBD3g4D/gdZihlpF4pg2ey+nGC5bhO2PaTMjBYq+Y//M7L 2JvT/sesT+5KJDkwnBY1aVeplqWS823fIcbdK89bP36GZTjt9gV61OoYuY+PK4h3 47z3MIFyVpDA447i/YH4yxKd5qNpHfEOOwgCRR6nlOHfmMOMXhEkkg== =S0WO -----END PGP SIGNATURE----- -------------- next part -------------- An HTML attachment was scrubbed... URL: