From jim at rfc1035.com Fri Apr 8 13:53:46 2005 From: jim at rfc1035.com (Jim Reid) Date: Fri, 08 Apr 2005 12:53:46 +0100 Subject: [dns-wg] ETSI ENUM Plugtest Announcement Message-ID: <20565.1112961226@gromit.rfc1035.com> I'm forwarding the announcement below on behalf of the ETSI Plugtest Secretariat. Any questions about the event should be sent to the address below. Apologies to those of you who've already seen this in the ENUM WG or IETF mailing lists. Dear All, We are pleased to invite you to the ENUM interoperability event, 30th May to 3rd June 2005 at ETSI Headquarters, Sophia Antipolis, France. The emerging technology of ENUM is attracting a lot of interest. By mapping telephone numbers to domain names, and from those to URLs, ENUM will be a key driver for the increasing convergence between the internet and telephony worlds. The ETSI ENUM Plugtests event will provide a vendor-neutral setting for equipment manufacturers, operators, ISPs, registries, software companies and system integrators to carry out controlled interoperability and conformance testing. It is a chance to discover ENUM system behaviour with misconfigured clients, servers, and intermediaries, so that they can explore the symptoms of such problems before their customers. For further details and to register, please visit our web site at the following URL: http://www.etsi.org/plugtests/ENUM.htm, the registration deadline is 16th May 2005. Please, show your interest by registering as soon as possible, but payment is not due before 23rd May 2005. Upon registration, you will be provided with ETSI's preferential rates for hotels and car rental. This invitation is open to anyone who may be interested so please feel free to forward it. To promote, boost or expand your image and products a wide range of sponsorship opportunities are available at: http://www.etsi.org/plugtests/sponsorus.htm We are looking forward to welcoming you in the South of France. Best regards, ETSI Plugtests TM Service Email: plugtests at etsi.org From pk at DENIC.DE Wed Apr 13 09:47:45 2005 From: pk at DENIC.DE (Peter Koch) Date: Wed, 13 Apr 2005 09:47:45 +0200 Subject: [dns-wg] (Open) DNS WG Action Items Message-ID: <20050413074745.GA7956@denics7.denic.de> Dear All, the list of action items at has been updated. As agreed upon at RIPE 49, item 48.3 (pointer to the list of reverse delegation checks) is marked "done", since there was no discussion after Olaf had sent the information. As always, the topic may be subject to discussion again in the future should anyone feel the need and propose changes. During the WG meeting in Stockholm there will be presentations and/or progress reports on the remaining items. Please review the list and send questions and contributions to the identified action item owner or to this list. -Peter From ncc at ripe.net Fri Apr 15 11:58:38 2005 From: ncc at ripe.net (RIPE NCC Operations) Date: Fri, 15 Apr 2005 11:58:38 +0200 Subject: [dns-wg] Changes to RIPE DNS Infrastructure Message-ID: <5.2.1.1.2.20050415115656.01aa4310@mailhost.ripe.net> Apologies for duplicate messages Dear Colleagues As part of our ongoing preparations for DNSSEC deployment., we have recently made some changes to the RIPE NCC DNS Server infrastructure. Our main DNS server (ns.ripe.net) held a significant amount of primary in-addr.arpa zones and secondary copies of many zones on behalf of other parties. We have split this into several servers as follows. ? ns.ripe.net ? This contains no primary, but many secondary zones. ? ns-pri.ripe.net ? This contains all zones for which RIPE is primary. ? ns-[CountryCode].ripe.net ? This contains all Country Code Top level Domain (CCTLD) zones for which RIPE is secondary. ? ns-sec.ripe.net ? We will deploy this server soon, it currently contains no zones. We are working towards the following: ? ns.ripe.net - This will contain /16 IPv4 reverse and /32 IPv6 secondary reverse zones. ? ns-pri.ripe.net - This will contain all zones for which RIPE is primary. ? ns-[CountryCode].ripe.net - This will contain ccTLD zones for which RIPE is secondary. ? ns-sec.ripe.net - This will contain all zones for which RIPE is secondary (excluding those on ns andns-tld). We will soon contact users to arrange moving zones from ns to ns-sec. This information was correct on 12 April 2005. Regards Brett Carr System Engineer RIPE NCC From jim at rfc1035.com Fri Apr 15 12:10:51 2005 From: jim at rfc1035.com (Jim Reid) Date: Fri, 15 Apr 2005 11:10:51 +0100 Subject: [dns-wg] Changes to RIPE DNS Infrastructure In-Reply-To: Message from RIPE NCC Operations of "Fri, 15 Apr 2005 11:58:38 +0200." <5.2.1.1.2.20050415115656.01aa4310@mailhost.ripe.net> Message-ID: <7224.1113559851@shaun.rfc1035.com> Thanks for this announcement. However I'm surprised and disappointed that the NCC didn't discuss the reorganisation with the DNS WG. Where will the ENUM zones that are/were on ns.ripe.net live once these changes have been done? From ripe-wgs.cs at schiefner.de Fri Apr 15 12:28:02 2005 From: ripe-wgs.cs at schiefner.de (Carsten Schiefner) Date: Fri, 15 Apr 2005 12:28:02 +0200 Subject: [dns-wg] Changes to RIPE DNS Infrastructure In-Reply-To: <7224.1113559851@shaun.rfc1035.com> References: <7224.1113559851@shaun.rfc1035.com> Message-ID: <425F9732.5000804@schiefner.de> Hi Jim, all - Jim Reid wrote: > Thanks for this announcement. However I'm surprised and disappointed > that the NCC didn't discuss the reorganisation with the DNS WG. > > Where will the ENUM zones that are/were on ns.ripe.net live once these > changes have been done? e164.arpa sits on ns-pri.ripe.net for quite a while already and is consistently delegated from arpa. According to the announcement I expect those E.164 CCs having ns.ripe.net as a secondary be moved to ns-sec.ripe.net. This, I believe, would require bilateral cooperation with the respective Tier 1 registry as the latter would have to update the zone on the primary to reflect the change from ns.ripe.net to ns-sec.ripe.net. Best, Carsten Schiefner From andrei at ripe.net Mon Apr 18 13:42:53 2005 From: andrei at ripe.net (Andrei Robachevsky) Date: Mon, 18 Apr 2005 13:42:53 +0200 Subject: [dns-wg] Changes to RIPE DNS Infrastructure In-Reply-To: <7224.1113559851@shaun.rfc1035.com> References: <7224.1113559851@shaun.rfc1035.com> Message-ID: <42639D3D.7060703@ripe.net> Jim, Jim Reid wrote: > Thanks for this announcement. However I'm surprised and disappointed > that the NCC didn't discuss the reorganisation with the DNS WG. > We considered this more a back-end side of the Reverse DNS project. But if people are interested we may present specific goals and the rationale of this part. A 15 min slot in the DNS-WG agenda should probably be enough. > Where will the ENUM zones that are/were on ns.ripe.net live once these > changes have been done? Regards, Andrei Robachevsky RIPE NCC From olaf at ripe.net Wed Apr 20 12:01:37 2005 From: olaf at ripe.net (Olaf M. Kolkman) Date: Wed, 20 Apr 2005 12:01:37 +0200 Subject: [dns-wg] Comparison of Delegation Checker (v 2.0 and v 2.1) Message-ID: <20050420120137.0a682ba9.olaf@ripe.net> Dear Colleagues, This message is about the DNS delegation checks performed when you update DOMAIN objects by requesting the updating of a delegation in the reverse address trees. We have recently updated the web interface to use version 2.1 of the back-end library (Net::DelCheck) while the whois database still uses version 2.0. We would like to ask the DNS Working Group to provide feedback on the version that is now available through the web interface. After considering the feedback, we plan to install the module for use with the whois database. We plan to do this after RIPE 50 (May 2 - 6) as part of a regular whois database upgrade. You can find the delegation checker web interface at: http://www.ripe.net/cgi-bin/delcheck/delcheck2.cgi You can find a list of the error codes returned by version 2.1 of the delegation checker at: http://www.ripe.net/rs/reverse/delcheck/delchecker_descr.html Detailed explanations of the most important differences between the tests that are currently running on the whois database (v 2.0) and those available through the web interface (v 2.1) can be found at: http://www.ripe.net/rs/reverse/changes.html This message relates to an earlier message to this list [1] and action item 48.2 [2]. Regards, Olaf M. Kolkman RIPE NCC [1] http://www.ripe.net/ripe/maillists/archives/dns-wg/2004/msg00172.html [2] http://www.ripe.net/ripe/wg/dns/dns-actions.html