- ipv6-wg - mailman.ripe.net

Re: [ipv6-wg@ripe.net] DNS Weather Report 2004-09-07
by Daniel Karrenberg 13 Sep '04

13 Sep '04

Since a storm seems to be rising about this and it threatens to leave the tea cup here is some perspective. Daniel ----- Forwarded message from Daniel Karrenberg <daniel.karrenberg(a)ripe.net> ----- Date: Wed, 8 Sep 2004 08:21:23 +0200 From: Daniel Karrenberg <daniel.karrenberg(a)ripe.net> To: Daniel Roesen <dr(a)cluenet.de> Subject: Re: [ipv6-wg(a)ripe.net] DNS Weather Report 2004-09-07 On 08.09 00:00, Daniel Roesen wrote: > On Tue, Sep 07, 2004 at 11:49:48AM +0200, Daniel Karrenberg wrote: > > On 07.09 01:08, Daniel Roesen wrote: > > > DNS WEATHER REPORT for selected infrastructure zones > > > ==================================================== > > > > Please stop spamming mailing lists. > > OK, you made me curious. Why do you (you are the first, all the other > feedback was overly positive) consider this "spamming"? Sending *unsolicited* automatic reports to *multiple* mailing lists is considered bad netiquette. In your case even more so since similar and better defined reports are available on demand from more than one source. It would have been more acceptable to say something like: "Hey, I have made this useful report. What do you think about it? If you are interested you can subscribe to regular reports here." These days netiquette is violated so frequently that most people do not even care to point things out to violators; they just ignore messages from people who do not behave socially. Procmail is an easy tool. [I spent 6 minutes composing this message. Multiply by n>20 / day] > And: was your request as a representant of the RIPE NCC, or as a > private person? Take it as advice from me as a person. The RIPE NCC does not police RIPE mailing lists. Daniel ----- End forwarded message -----

4 7

[ipv6-wg@ripe.net] Draft agenda (v2) for ipv6 wg RIPE49
by David Kessens 11 Sep '04

11 Sep '04

Hi, Please see below for the second version of our proposed agenda. We still have some time left, so proposals for additional agenda items that are useful for ipv6 Internet service providers are still welcome. You might have noticed that the minutes for RIPE 48 are still missing. I am working with the RIPE NCC to get them posted as soon as possible. I hope this helps, David Kessens --- Updated agenda for the IPv6 Working Group Meeting RIPE49 When: 14:00 - 18:00, Wednesday September 22, 2004 Where: Medici Room, Renaissance Hotel, Manchester, UK A. Administrative stuff - appointment of scribe - agenda bashing - approval of the minutes (David Kessens) B. Global IPv6 routing table status (Gert Doering) C. Report(s) about *actual* v6 traffic volume as compared to v4? *what's real* out there, not what's on powerpoint? (input from the audience) D. What are the deployment plans behind the larger ipv6 allocations ? o TeliaSonera (Mikael Lind) o Others ? E. Guidelines for ISPs on IPv6 assignments (Jordi Palet Martinez) http://www.europe.ipv6tf.org/PublicDocuments/guidelines_for_isp_on_ipv6_ass… F. moonv6 (Jim Bound) -- break --- G. Update on multihoming solutions from IETF (Geoff Huston) H. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) I. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0

[ipv6-wg@ripe.net] Draft (v1) IPv6 wg minutes at RIPE 47
by David Kessens 11 Sep '04

11 Sep '04

Please see below for the draft minutes of RIPE 47. My apologies for the late publication. The minutes will be approved if no significant comments will be received before the next working roup session in Manchester. David Kessens --- ________________________________________________ Draft (v1) minutes for the IPv6 Working Group Meeting RIPE 47 When: 14:00 - 15:30, Tuesday January 27, 2004 Where: St Johns II, Hotel Krasnapolsky, Amsterdam A. Administrative stuff Scribe: Timothy Lowe (RIPE NCC) Attendees: 132 B. Ranges of ipv6 addresses and their use (Jeroen Massar) http://www.ripe.net/ripe/meetings/ripe-47/presentations/ripe47-ipv6-ghost-r… C. Global IPv6 routing table status (Gert Doering) http://www.ripe.net/ripe/meetings/ripe-47/presentations/ripe47-ipv6-global-… D. Report(s) about *actual* v6 traffic volume as compared to v4 - Tunnel Detection Tool (Lorenzo Colitti, RIPE NCC, TTM project) http://www.ripe.net/ripe/meetings/ripe-47/presentations/ripe47-ipv6-tunnel-… - IPv6 Network Management (Bernard Tuy) E. Operational issues with IPv6: RPSLng testing, policy issues, filtering practices, peering (Simon Leinen, Swiss IPv6 task force & ops group) http://www.ripe.net/ripe/meetings/ripe-47/presentations/ripe47-ipv6-swiss-p… F. Developments/initiatives regarding IPv6 in the RIPE region and beyond - latest IPv6 Land Speed Record (Edoardo Martelli (CERN)) ---

1 0

[ipv6-wg@ripe.net] Re: [dns-wg] IPv6 in .ie
by Jim Reid 09 Sep '04

09 Sep '04

>>>>> "Daniel" == Daniel Karrenberg <daniel.karrenberg(a)ripe.net> writes: Daniel> If I was IANA I would advise .ie strongly to rationalise Daniel> the names in their glue to save space. Yeah. Somebody needs to write up a draft on this as a BCP: using efficient label compression to avoid truncated responses.

5 5

[ipv6-wg@ripe.net] IPv6 in .ie (fwd)
by Carlos Friacas 08 Sep '04

08 Sep '04

One more today... Belgium (.BE), supported by BRUSSELS.NS.DNS.BE. (2001:6a8:3c60::be) ./Carlos -------------- http://www.ip6.fccn.pt/nativeRCTS2.html Wide Area Network (WAN) Workgroup, CMF8-RIPE, CF596-ARIN FCCN - Fundacao para a Computacao Cientifica Nacional http://www.fccn.pt "Internet is just routes (140068/465), naming (millions) and... people!" ---------- Forwarded message ---------- Date: Tue, 7 Sep 2004 08:54:30 +0100 (WEST) From: Carlos Friacas <cfriacas(a)fccn.pt> To: ipv6-wg(a)ripe.net Subject: [ipv6-wg(a)ripe.net] IPv6 in .ie (fwd) FYI, 19 TLDs already served by IPv6 nameservers w/glue-record on ".". Tue Sep 7 08:50:45 WEST 2004 ----------------------------- CH. DOMREG.NIC.CH. LI. DOMREG.NIC.CH. DE. A.NIC.DE. FR. C.NIC.FR. IE. NS6.IEDR.IE. JP. A.DNS.JP. JP. D.DNS.JP. JP. E.DNS.JP. JP. F.DNS.JP. KR. G.DNS.KR. IE. NS3.NS.ESAT.NET. TP. NS3.NS.ESAT.NET. AN. NS0.JA.NET. GB. NS0.JA.NET. GG. NS0.JA.NET. INT. NS0.JA.NET. JE. NS0.JA.NET. AN. NS0.JA.NET. GB. NS0.JA.NET. GG. NS0.JA.NET. INT. NS0.JA.NET. JE. NS0.JA.NET. INT. NS-SEC.RIPE.NET. AQ. NS-EXT.ISC.ORG. IL. NS-EXT.ISC.ORG. NL. NS-EXT.ISC.ORG. PH. NS-EXT.ISC.ORG. TN. NS.ATI.TN. TW. A.DNS.TW. TW. C.DNS.TW. TW. D.DNS.TW. ./Carlos -------------- http://www.ip6.fccn.pt/nativeRCTS2.html Wide Area Network (WAN) Workgroup, CMF8-RIPE, CF596-ARIN FCCN - Fundacao para a Computacao Cientifica Nacional http://www.fccn.pt "Internet is just routes (140068/465), naming (millions) and... people!" ---------- Forwarded message ---------- Date: Mon, 06 Sep 2004 18:05:11 +0100 From: Billy Glynn <billy.glynn(a)domainregistry.ie> To: ipv6-wg(a)ripe.net Cc: dns-wg(a)ripe.net, tech(a)lists.centr.org, ga(a)centr.org Subject: [ipv6-wg(a)ripe.net] IPv6 in .ie Hi, FYI, the IEDR in it's capacity as ccTLD manager of .ie have added a new IPv6 compatible name server ns6.iedr.ie. Additionally, we have added AAAA glue for one of our slaves ns3.ns.esat.net. ns3.ns.esat.net also slaves for the folks at .tp Kind regards -- ________________________________ Billy Glynn Network Operations Centre IE Domain Registry Ltd Tel: +353 (0)1 2365404 Mobile: +353 (0)87 9188317 billy.glynn(a)domainregistry.ie ________________________________

1 0

[ipv6-wg@ripe.net] Re: [dns-wg] IPv6 in .ie
by Andrei Robachevsky 08 Sep '04

08 Sep '04

Andreas S. Kerber wrote: > On Tue, Sep 07, 2004 at 08:39:08AM +0200, Jeroen Massar wrote: > >>I also see that you have ns2.nic.fr listed in there, ns3.nic.fr has IPv6 >>for sure. >>You should maybe ask RIPE NCC if they can stick glue for ns.ripe.net >>into the . also with an IPv6 address, which would also give quite a >>number of other TLD's etc an IPv6 capable nameserver all of a sudden. > > > uuh, I guess that would get pretty close to 512 bytes when querying ie. > > # dig -t NS ie. @a.root-servers.net | grep MSG > ;; MSG SIZE rcvd: 493 I think adding another AAAA record will actually exceed this limit. Daniel wrote: > So what? See below for examples of what could happen: > soem glue is omitted. > But also the IANA procedure will not permit it: "5. If the number of name servers or IP addresses in the delegation exceeds eight (8), the size of responses to reasonable queries with the intended delegation will be checked to ensure that such responses fit into a 512 byte UDP packet. This is the standard size limitation for UDP response packets for most resolving name server software on the Internet today." Coming back to the issue with ns.ripe.net. The fact that it is a secondary for about 90 ccTLDs makes it impossible to insert AAAA record in the root for any of the zone, because that will affect others. Currently, we are planning to introduce a scheme whereby each ccTLD has its own name in the ripe.net domain, eg: ns-ie.ripe.net A 193.0.12.107 AAAA 2001:610:240:0:53:cc:12:107 All of the addresses for ccTLDs (ns-XX.ripe.net) are simply IP aliases on a shared machine. Regards, Andrei Robachevsky RIPE NCC

2 1

[ipv6-wg@ripe.net] IPv6 Deployment Conference at RIPE 49
by Tim Chown 07 Sep '04

07 Sep '04

Hi, The UK IPv6 Task Force, in conjunction with RIPE and the European IST IPv6 Cluster, is presenting a programme of IPv6 events from 23rd-24th September 2004. The UK IPv6 Deployment Conference, sponsored by BT and Cisco, is targeted at those interested in the current state of play in IPv6 deployment. It aims to present an overview of state-of-the-art in the latest IPv6 deployment technology, including: * Advanced testbeds, including the US Moonv6 project * Early IPv6 production deployments, in backbones and enterprises * IPv4-IPv6 transition and integration technologies * IPv6 opportunities: new technologies, delivery media and applications The Conference is co-located with the 49th RIPE Meeting of 20th-24th September, at which Europe's ISPs will gather to discuss technology and policy. We have scheduled a free European IST IPv6 Cluster meeting on the afternoon before the UK IPv6 Deployment Conference to allow our delegates the opportunity of attending an attractive, fuller one-and-a-half day programme of leading edge IPv6 talks and discussion should they wish to do so. For full details and registration information, please see: http://www.uk.ipv6tf.org/events/manchester.html Hope to see you in Manchester! Regards, Tim Chown UK IPv6 Task Force Steering Committee

1 0

[ipv6-wg@ripe.net] IEEE SAINT2005 workshop CPF: IPv6 Deployment Status and Challenges
by JORDI PALET MARTINEZ 07 Sep '04

07 Sep '04

Hi all, The call for papers for this international workshop is now open until October 7. Authors are kindly requested to submit papers as early as possible to facilitate a review process. IEEE SAINT2005 workshop CPF: IPv6 Deployment Status and Challenges http://www.ist-ipv6.org/modules.php?op=modload&name=News&file=article&sid=6… Please forward this email to all your contacts. Regards, Jordi ********************************** Madrid 2003 Global IPv6 Summit Presentations and videos on line at: http://www.ipv6-es.com This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

[ipv6-wg@ripe.net] DNS Weather Report 2004-09-07
by Daniel Roesen 07 Sep '04

07 Sep '04

DNS WEATHER REPORT for selected infrastructure zones ==================================================== Issue 2004-09-07 Zones analyzed and their SOA contacts: - . - arpa. nstld(a)verisign-grs.com - int. noc(a)icann.org - in-addr.arpa bind(a)arin.net - ip6.arpa. hostmaster(a)icann.org - ip6.int. hostmaster(a)ep.net Operators: please let me know wether you do want a copy when there's no problem with your zone(s) or not. Don't want to annoy anyone unnecessarily! Some people have approached me wether it would be possible to receive personal copies of the report. Please let me know wether you are interested in such a service yourself. If there is enough interest, I will set up a distro list for that. Executive summary: * the IP6.ARPA problems regarding delegation NS RRset got fixed! * ns.isi.edu is _still_ out of sync for the INT zone. * ns.isi.edu is _still_ auth for IP6.INT where it shouldn't be. The state of the root zone =========================== fine! The state of the ARPA zone ========================== fine! The state of the INT zone ========================= - ns.isi.edu is not in sync with the other nameservers Current SOA serial of the INT TLD: 2004090400, ns.isi.edu has still 2002080104 and is publishing stale data (e.g. an old NS RRset for the zone). Problem exists since at least 2004-08-24 The state of the IN-ADDR.ARPA zone ================================== fine! The state of the IP6.ARPA zone ============================== fine! The state of the IP6.INT zone ============================= - ns.isi.edu (one of the INT TLD servers) feels authoritative for the IP6.INT zone, but is neither listed in the delegation NS RRset, nor in the in-zone NS RRset of IP6.INT. Luckily, ns.isi.edu carries ip6.int with the same SOA serial as the official servers, so induces no operational problems so far. Problem exists since at least 2004-08-24 Regards, Daniel

1 1

[ipv6-wg@ripe.net] Re: [dns-wg] IPv6 in .ie
by Daniel Karrenberg 07 Sep '04

07 Sep '04

On 07.09 08:49, Andreas S. Kerber wrote: > > uuh, I guess that would get pretty close to 512 bytes when querying ie. So what? See below for examples of what could happen: soem glue is omitted. If the client supports IPv6 it almost certainly supports EDNS(0), so the 512 byte limit is no issue. If the lient does not support EDNS some glue may be dropped for very long names without problems. See http://www.nlnetlabs.nl/ipv6/publications/v6rootglue.pdf for a little more detail. (It can be argued that dropping AAAA glue first is a good tactic here because "see above". This will be implemented on all root name servers in the near future.) Daniel ----- ; <<>> DiG 8.2 <<>> @k.root-servers.net. short.ie. ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 12 ;; QUERY SECTION: ;; short.ie, type = A, class = IN ;; AUTHORITY SECTION: ie. 2D IN NS ns2.nic.fr. ie. 2D IN NS ns.ripe.net. ie. 2D IN NS banba.domainregistry.ie. ie. 2D IN NS uucp-gw-1.pa.dec.com. ie. 2D IN NS uucp-gw-2.pa.dec.com. ie. 2D IN NS ns3.ns.esat.net. ie. 2D IN NS gns1.domainregistry.ie. ie. 2D IN NS gns2.domainregistry.ie. ie. 2D IN NS ice.netsource.ie. ie. 2D IN NS ns6.iedr.ie. ;; ADDITIONAL SECTION: ns2.nic.fr. 2D IN A 192.93.0.4 ns.ripe.net. 2D IN A 193.0.0.193 banba.domainregistry.ie. 2D IN A 193.1.142.2 uucp-gw-1.pa.dec.com. 2D IN A 204.123.2.18 uucp-gw-2.pa.dec.com. 2D IN A 204.123.2.19 ns3.ns.esat.net. 2D IN A 192.111.39.100 ns3.ns.esat.net. 2D IN AAAA 2001:7c8:2:a::64 gns1.domainregistry.ie. 2D IN A 198.133.199.102 gns2.domainregistry.ie. 2D IN A 198.133.199.103 ice.netsource.ie. 2D IN A 212.17.32.2 ns6.iedr.ie. 2D IN A 213.190.149.221 ns6.iedr.ie. 2D IN AAAA 2001:bb0:ccc3::2 ;; Total query time: 71 msec ;; FROM: dienst.karrenberg.net to SERVER: k.root-servers.net. 193.0.14.129 ;; WHEN: Tue Sep 7 11:29:37 2004 ;; MSG SIZE sent: 26 rcvd: 499 ; <<>> DiG 8.2 <<>> @k.root-servers.net. something.verylogindeed.fordemopurposes.ie ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 11 ;; QUERY SECTION: ;; something.verylogindeed.fordemopurposes.ie, type = A, class = IN ;; AUTHORITY SECTION: ie. 2D IN NS ns2.nic.fr. ie. 2D IN NS ns.ripe.net. ie. 2D IN NS banba.domainregistry.ie. ie. 2D IN NS uucp-gw-1.pa.dec.com. ie. 2D IN NS uucp-gw-2.pa.dec.com. ie. 2D IN NS ns3.ns.esat.net. ie. 2D IN NS gns1.domainregistry.ie. ie. 2D IN NS gns2.domainregistry.ie. ie. 2D IN NS ice.netsource.ie. ie. 2D IN NS ns6.iedr.ie. ;; ADDITIONAL SECTION: ns2.nic.fr. 2D IN A 192.93.0.4 ns.ripe.net. 2D IN A 193.0.0.193 banba.domainregistry.ie. 2D IN A 193.1.142.2 uucp-gw-1.pa.dec.com. 2D IN A 204.123.2.18 uucp-gw-2.pa.dec.com. 2D IN A 204.123.2.19 ns3.ns.esat.net. 2D IN A 192.111.39.100 ns3.ns.esat.net. 2D IN AAAA 2001:7c8:2:a::64 gns1.domainregistry.ie. 2D IN A 198.133.199.102 gns2.domainregistry.ie. 2D IN A 198.133.199.103 ice.netsource.ie. 2D IN A 212.17.32.2 ns6.iedr.ie. 2D IN A 213.190.149.221 ;; Total query time: 69 msec ;; FROM: dienst.karrenberg.net to SERVER: k.root-servers.net. 193.0.14.129 ;; WHEN: Tue Sep 7 11:29:43 2004 ;; MSG SIZE sent: 60 rcvd: 505 ; <<>> DiG 8.2 <<>> @k.root-servers.net. something.verylogindeed.fordemopurposes.evenlonger.toforceommittingmoreglue.ie ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 9 ;; QUERY SECTION: ;; something.verylogindeed.fordemopurposes.evenlonger.toforceommittingmoreglue.ie, type = A, class = IN ;; AUTHORITY SECTION: ie. 2D IN NS ns2.nic.fr. ie. 2D IN NS ns.ripe.net. ie. 2D IN NS banba.domainregistry.ie. ie. 2D IN NS uucp-gw-1.pa.dec.com. ie. 2D IN NS uucp-gw-2.pa.dec.com. ie. 2D IN NS ns3.ns.esat.net. ie. 2D IN NS gns1.domainregistry.ie. ie. 2D IN NS gns2.domainregistry.ie. ie. 2D IN NS ice.netsource.ie. ie. 2D IN NS ns6.iedr.ie. ;; ADDITIONAL SECTION: ns2.nic.fr. 2D IN A 192.93.0.4 ns.ripe.net. 2D IN A 193.0.0.193 banba.domainregistry.ie. 2D IN A 193.1.142.2 uucp-gw-1.pa.dec.com. 2D IN A 204.123.2.18 uucp-gw-2.pa.dec.com. 2D IN A 204.123.2.19 ns3.ns.esat.net. 2D IN A 192.111.39.100 ns3.ns.esat.net. 2D IN AAAA 2001:7c8:2:a::64 gns1.domainregistry.ie. 2D IN A 198.133.199.102 gns2.domainregistry.ie. 2D IN A 198.133.199.103 ;; Total query time: 67 msec ;; FROM: dienst.karrenberg.net to SERVER: k.root-servers.net. 193.0.14.129 ;; WHEN: Tue Sep 7 11:33:53 2004 ;; MSG SIZE sent: 96 rcvd: 509

2 2