From ddiaz at ripe.net Mon Dec 2 12:08:19 2002 From: ddiaz at ripe.net (Daniel Diaz) Date: Mon, 02 Dec 2002 12:08:19 +0100 Subject: RIPE NCC's DNS server available in IPv6 Message-ID: <200212021108.gB2B8JpG025509@birch.ripe.net> Dear all, We are glad to announce that since November 29, RIPE NCC's DNS service (ns.ripe.net) is also available in IPv6. This was an action on RIPE NCC for RIPE 43 and it is now accomplished. ns.ripe.net internet address = 193.0.0.193 ns.ripe.net IPv6 address = 2001:610:240:0:193::193 Best regards. -- Daniel.Diaz Operations Manager RIPE NCC From ddiaz at ripe.net Tue Dec 3 14:58:06 2002 From: ddiaz at ripe.net (Daniel.Diaz) Date: Tue, 03 Dec 2002 14:58:06 +0100 Subject: RIPE NCC's DNS server available in IPv6 In-Reply-To: Message from Carlos Friacas of "Tue, 03 Dec 2002 11:44:55 GMT." Message-ID: <200212031358.gB3Dw68V022038@birch.ripe.net> Dear Carlos, et al, (Apologies for duplicates). Carlos Friacas writes: * Hello, * * I have a question about this, as pointed out by one of my colleagues here: * * As the SOA record for ripe.net., the glue record for ns.ripe.net. on * .gtld-servers.net is 193.0.0.193, right? * Shouldnt they have also an AAAA record for ns.ripe.net on the net. zone? * Is this scheduled/possible/requestable/desirable??? * Indeed having this IN AAAA record included in the parent zone for ripe.net. would be the most desirable. So far I ignore though if .net nameservers are V6 ready or not. We definitively will look forward getting this record included in our parent zone etc... still the root-zone is not V6 ready yet, so the tree can not be completed anyway. With best regards. -- Daniel.Diaz Operations Manager RIPE NCC From ddiaz at ripe.net Tue Dec 3 15:08:41 2002 From: ddiaz at ripe.net (Daniel.Diaz) Date: Tue, 03 Dec 2002 15:08:41 +0100 Subject: RIPE NCC's DNS server available in IPv6 In-Reply-To: Message from "Daniel.Diaz" of "Tue, 03 Dec 2002 14:58:06 +0100." <200212031358.gB3Dw68V022038@birch.ripe.net> Message-ID: <200212031408.gB3E8f8V026792@birch.ripe.net> apologies for duplicates. "Daniel.Diaz" writes: * Indeed having this IN AAAA record included in the parent zone for ripe.net ^^^^^^^^^^ |||||||||| Sorry... this was meant to be 'ns.ripe.net' * would be the most desirable. So far I ignore though if .net nameservers are V6 * ready or not. * We definitively will look forward getting this record included in our * parent zone etc... still the root-zone is not V6 ready yet, so the tree can not * be completed anyway. -- Daniel.Diaz From bmanning at ISI.EDU Tue Dec 3 15:23:36 2002 From: bmanning at ISI.EDU (Bill Manning) Date: Tue, 3 Dec 2002 06:23:36 -0800 (PST) Subject: RIPE NCC's DNS server available in IPv6 In-Reply-To: <200212031358.gB3Dw68V022038@birch.ripe.net> from "Daniel.Diaz" at "Dec 3, 2 02:58:06 pm" Message-ID: <200212031423.gB3ENb229388@boreas.isi.edu> we will be adding the AAAA glue record in the v6 testbed root zone for those sites that use ns.ripe.net as a server. for those who wish, this system does have v6 aware .NET and . zones as well as select, other TLDs that are v6 aware. % % Dear Carlos, et al, % % (Apologies for duplicates). % % % Carlos Friacas writes: % * Hello, % * % * I have a question about this, as pointed out by one of my colleagues here: % * % * As the SOA record for ripe.net., the glue record for ns.ripe.net. on % * .gtld-servers.net is 193.0.0.193, right? % * Shouldnt they have also an AAAA record for ns.ripe.net on the net. zone? % * Is this scheduled/possible/requestable/desirable??? % * % % Indeed having this IN AAAA record included in the parent zone for ripe.net. % would be the most desirable. So far I ignore though if .net nameservers are V6 % ready % or not. We definitively will look forward getting this record included in our % parent zone etc... still the root-zone is not V6 ready yet, so the tree can % not % be completed anyway. % % With best regards. % % -- Daniel.Diaz % Operations Manager % RIPE NCC % % -- --bill Opinions expressed may not even be mine by the time you read them, and certainly don't reflect those of any other entity (legal or otherwise). From Francis.Dupont at enst-bretagne.fr Tue Dec 3 15:27:39 2002 From: Francis.Dupont at enst-bretagne.fr (Francis Dupont) Date: Tue, 03 Dec 2002 15:27:39 +0100 Subject: [ipv6-wg@ripe.net] Re: RIPE NCC's DNS server available in IPv6 In-Reply-To: Your message of Tue, 03 Dec 2002 14:58:06 +0100. <200212031358.gB3Dw68V022038@birch.ripe.net> Message-ID: <200212031427.gB3ERdPC094185@givry.rennes.enst-bretagne.fr> In your previous mail you wrote: Indeed having this IN AAAA record included in the parent zone for ripe.net. would be the most desirable. So far I ignore though if .net nameservers are V6 ready or not. We definitively will look forward getting this record included in our parent zone etc... still the root-zone is not V6 ready yet, so the tree can not be completed anyway. => to support AAAA RRs in the glue and to support IPv6 transport are two different things. And what it is asked for is the first/easiest one. Regards Francis.Dupont at enst-bretagne.fr From ddiaz at ripe.net Tue Dec 3 15:30:30 2002 From: ddiaz at ripe.net (Daniel Diaz) Date: Tue, 03 Dec 2002 15:30:30 +0100 Subject: [ipv6-wg@ripe.net] Re: RIPE NCC's DNS server available in IPv6 In-Reply-To: Your message of Tue, 03 Dec 2002 15:27:39 +0100. <200212031427.gB3ERdPC094185@givry.rennes.enst-bretagne.fr> References: <200212031427.gB3ERdPC094185@givry.rennes.enst-bretagne.fr> Message-ID: <200212031431.gB3EVC8V004027@birch.ripe.net> Francis Dupont writes: * In your previous mail you wrote: * * Indeed having this IN AAAA record included in the parent zone for * ripe.net. would be the most desirable. So far I ignore though if .net * nameservers are V6 ready or not. We definitively will look forward * getting this record included in our parent zone etc... still the * root-zone is not V6 ready yet, so the tree can not be completed * anyway. * * => to support AAAA RRs in the glue and to support IPv6 transport are * two different things. And what it is asked for is the first/easiest one. I know and that was what I was replying to Francis. Not all DNS SW is V6 ready.... ;) Regards -- Daniel.Diaz RIPE NCC From cfriacas at fccn.pt Tue Dec 3 12:44:55 2002 From: cfriacas at fccn.pt (Carlos Friacas) Date: Tue, 3 Dec 2002 11:44:55 +0000 (WET) Subject: RIPE NCC's DNS server available in IPv6 In-Reply-To: <200212021108.gB2B8JpG025509@birch.ripe.net> Message-ID: On Mon, 2 Dec 2002, Daniel Diaz wrote: > Dear all, > > We are glad to announce that since November 29, RIPE NCC's DNS > service (ns.ripe.net) is also available in IPv6. > > This was an action on RIPE NCC for RIPE 43 and it is now accomplished. > > ns.ripe.net internet address = 193.0.0.193 > ns.ripe.net IPv6 address = 2001:610:240:0:193::193 > > Best regards. > > -- Daniel.Diaz > Operations Manager > RIPE NCC Hello, I have a question about this, as pointed out by one of my colleagues here: As the SOA record for ripe.net., the glue record for ns.ripe.net. on .gtld-servers.net is 193.0.0.193, right? Shouldnt they have also an AAAA record for ns.ripe.net on the net. zone? Is this scheduled/possible/requestable/desirable??? Thanks. Regards, ./Carlos "Networking is fun!" -------------- [http://www.ip6.fccn.pt] http://www.fccn.pt , CMF8-RIPE, CF596-ARIN, Wide Area Network Workgroup F.C.C.N. - Fundacao para a Computacao Cientifica Nacional fax: +351 218472167 From bmanning at ISI.EDU Mon Dec 9 19:32:21 2002 From: bmanning at ISI.EDU (Bill Manning) Date: Mon, 9 Dec 2002 10:32:21 -0800 (PST) Subject: RIPE NCC's DNS server available in IPv6 In-Reply-To: from Carlos Friacas at "Dec 3, 2 11:44:55 am" Message-ID: <200212091832.gB9IWM608231@boreas.isi.edu> ok, so the testbed has this server listed for slave service. I would ask the RIPE folks to do the following: add this aaaa record to the ripe.net zone that they manage. contact the administrators of the testbed .NET zone (if you need a pointer...) and have the testbed .NET zone include this glue as well ... for example: [root at 66 named]# dig uy. ns any @::1 ;; Warning, extra type option ; <<>> DiG 9.3.0s20021115 <<>> uy. ns any @::1 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33493 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 5, ADDITIONAL: 6 ;; QUESTION SECTION: ;uy. IN ANY ;; AUTHORITY SECTION: uy. 172800 IN NS SECIU.EDU.uy. uy. 172800 IN NS UUCP-GW-1.PA.DEC.COM. uy. 172800 IN NS UUCP-GW-2.PA.DEC.COM. uy. 172800 IN NS NS.UU.NET. uy. 172800 IN NS NS.RIPE.NET. ;; ADDITIONAL SECTION: NS.UU.NET. 172800 IN A 137.39.1.3 NS.RIPE.NET. 172800 IN AAAA 2001:610:240:0:193::193 SECIU.EDU.uy. 172800 IN A 164.73.128.5 UUCP-GW-1.PA.DEC.COM. 172800 IN A 204.123.2.18 UUCP-GW-1.PA.DEC.COM. 172800 IN A 16.1.0.18 UUCP-GW-2.PA.DEC.COM. 172800 IN A 16.1.0.19 .... while: [root at 66 named]# dig ns.ripe.net. aaaa @::1 ; <<>> DiG 9.3.0s20021115 <<>> ns.ripe.net. aaaa @::1 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21852 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;ns.ripe.net. IN AAAA ;; AUTHORITY SECTION: net. 172800 IN NS COM-A.ip4.int. ;; ADDITIONAL SECTION: COM-A.ip4.int. 172800 IN AAAA 3ffe:4::5 .... % On Mon, 2 Dec 2002, Daniel Diaz wrote: % % > Dear all, % > % > We are glad to announce that since November 29, RIPE NCC's DNS % > service (ns.ripe.net) is also available in IPv6. % > % > This was an action on RIPE NCC for RIPE 43 and it is now accomplished. % > % > ns.ripe.net internet address = 193.0.0.193 % > ns.ripe.net IPv6 address = 2001:610:240:0:193::193 % > % > Best regards. % > % > -- Daniel.Diaz % > Operations Manager % > RIPE NCC % % Hello, % % I have a question about this, as pointed out by one of my colleagues here: % % As the SOA record for ripe.net., the glue record for ns.ripe.net. on % .gtld-servers.net is 193.0.0.193, right? % Shouldnt they have also an AAAA record for ns.ripe.net on the net. zone? % Is this scheduled/possible/requestable/desirable??? % % Thanks. % % % Regards, % % ./Carlos % "Networking is fun!" % -------------- [http://www.ip6.fccn.pt] http://www.fccn.pt % , CMF8-RIPE, CF596-ARIN, Wide Area Network Workgroup % F.C.C.N. - Fundacao para a Computacao Cientifica Nacional fax: +351 218472167 % -- --bill Opinions expressed may not even be mine by the time you read them, and certainly don't reflect those of any other entity (legal or otherwise). From training at ripe.net Fri Dec 20 16:16:50 2002 From: training at ripe.net (RIPE NCC Training) Date: Fri, 20 Dec 2002 16:16:50 +0100 Subject: ANNOUNCEMENT: DNSSEC TRAINING COURSES Message-ID: <200212201516.gBKFGovP013961@birch.ripe.net> Dear colleagues, [apologies for duplicate postings] As a new service to its members the RIPE NCC offers the DNSSEC training courses. The main objective of the DNSSEC training course is to provide LIRs with sufficient background to be able to deploy DNSSEC in their own organisation as soon as the protocol is standardised. This course also explains the specific procedures set up by the RIPE NCC to to secure the in-addr.arpa zone. The Domain Name System (DNS) is one of the main parts of the Internet infrastructure. At the moment DNS lacks a mechanism to establish the authenticity and integrity of the data it provides. DNSSEC is a set of extensions to provide this end-to-end authenticity and integrity. It is currently being developed within the IETF dnsnext working group. The protocol is about to be finalised and the code implementing the protocol is available in alpha releases. The DNSSEC course consists of two parts: an "Introduction to DNSSEC" and a "real life demonstration" . The "Introduction to DNSSEC" will cover: - DNS security threats - DNSSEC security mechanisms - DNSSEC server protection - DNSSEC data protection - Delegation issues - Key management issues - Current developments Examples are based on the BIND name server. Please note that the DNSSEC is an advanced course, it will: - NOT teach the basics of DNS. - NOT describe how to receive Internet resources from the RIPE NCC nor how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network & system operators, engineers, etc. This course is not intended for administrative or management staff (e.g. hostmasters). It is assumed that all attendees are familiar with common DNS terminology, have a practical knowledge in operating DNS servers and are interested in learning the concepts and mechanisms that DNSSEC offers. The DNSSEC course is conducted in the English language and is free of charge, since it is covered by the membership contribution. More information about the DNSSEC training course can be found at: http://www.ripe.net/training/dnssec/ REGISTRATION: You can register for a course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this email and replying to In order to register for a DNSSEC course you must be an employee of an LIR and either : - be an LIR contact - be confirmed by an LIR contact. LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the "DNSSEC Training Course" will not be an authorative contact persons for their LIR, therefore will be refused by the course registration "robot". In order to be admited to the course, confirmation email need to be send to . Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, The RIPE NCC Training Team COURSE DATES AND VENUES ======================== Date: Saturday 1st February 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands AND: Date: Monday 24th February 2003 Time: 0900 - 1700 Location: Frankfurt, Germany AND: Date: Thursday 27th March 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The Course you plan to attend (date and location) # COURSE [ ] %END From training at ripe.net Fri Dec 20 16:16:50 2002 From: training at ripe.net (training at ripe.net) Date: Fri, 20 Dec 2002 16:16:50 +0100 Subject: [local-ir@ripe.net]ANNOUNCEMENT: DNSSEC TRAINING COURSES In-Reply-To: <200212201516.gBKFGovP013961@birch.ripe.net> References: <200212201516.gBKFGovP013961@birch.ripe.net> Message-ID: Dear colleagues, [apologies for duplicate postings] As a new service to its members the RIPE NCC offers the DNSSEC training courses. The main objective of the DNSSEC training course is to provide LIRs with sufficient background to be able to deploy DNSSEC in their own organisation as soon as the protocol is standardised. This course also explains the specific procedures set up by the RIPE NCC to to secure the in-addr.arpa zone. The Domain Name System (DNS) is one of the main parts of the Internet infrastructure. At the moment DNS lacks a mechanism to establish the authenticity and integrity of the data it provides. DNSSEC is a set of extensions to provide this end-to-end authenticity and integrity. It is currently being developed within the IETF dnsnext working group. The protocol is about to be finalised and the code implementing the protocol is available in alpha releases. The DNSSEC course consists of two parts: an "Introduction to DNSSEC" and a "real life demonstration" . The "Introduction to DNSSEC" will cover: - DNS security threats - DNSSEC security mechanisms - DNSSEC server protection - DNSSEC data protection - Delegation issues - Key management issues - Current developments Examples are based on the BIND name server. Please note that the DNSSEC is an advanced course, it will: - NOT teach the basics of DNS. - NOT describe how to receive Internet resources from the RIPE NCC nor how to operate a Local Internet Registry (LIR) The target audience of the course are technical staff of LIRs: e.g. network & system operators, engineers, etc. This course is not intended for administrative or management staff (e.g. hostmasters). It is assumed that all attendees are familiar with common DNS terminology, have a practical knowledge in operating DNS servers and are interested in learning the concepts and mechanisms that DNSSEC offers. The DNSSEC course is conducted in the English language and is free of charge, since it is covered by the membership contribution. More information about the DNSSEC training course can be found at: http://www.ripe.net/training/dnssec/ REGISTRATION: You can register for a course at the following URL: http://www.ripe.net/cgi-bin/trainingform.pl.cgi Or by completing the registration form at the end of this email and replying to In order to register for a DNSSEC course you must be an employee of an LIR and either : - be an LIR contact - be confirmed by an LIR contact. LIR contacts are those employees of an LIR who are registered with RIPE NCC as authoritative contact persons. It is expected that most of those interested in the "DNSSEC Training Course" will not be an authorative contact persons for their LIR, therefore will be refused by the course registration "robot". In order to be admited to the course, confirmation email need to be send to . Please approach the LIR contacts from your organisation personally, since the identity of LIR contacts is confidential, and the RIPE NCC is unable to divulge contact persons for any given LIR. Kind Regards, The RIPE NCC Training Team COURSE DATES AND VENUES ======================== Date: Saturday 1st February 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands AND: Date: Monday 24th February 2003 Time: 0900 - 1700 Location: Frankfurt, Germany AND: Date: Thursday 27th March 2003 Time: 0900 - 1700 Location: Amsterdam, Netherlands REGISTRATION FORM ================= %START PART 1 - Registration 1) Your name Enter First name, Last name in full e.g. John Doe Mary-Beth Walton # NAME [ ] 2) Your Registry ID (format: country-code.) # REG [ ] 3) Your e-mail address # EMAIL [ ] 4) Your NIC handle (optional) # NICHANDLE [ ] 5) The Course you plan to attend (date and location) # COURSE [ ] %END