- ipv6-wg - mailman.ripe.net

[ipv6-wg@ripe.net] (no subject)
by Ilias Markantonis 16 Dec '03

16 Dec '03

hi!I am working in a mobile ip6 testbed and i hope you can tell me of a software better than ethereal which can print the binding updates and caches.also if this software has a plotting tool for the desired outputs,it would be perfect.

1 0

[ipv6-wg@ripe.net] "...convene a public meeting to gather information about IPv6."
by Jim Fleming 12 Dec '03

12 Dec '03

December 12, 2003 http://www.ntia.doc.gov/ntiahome/press/2003/IPv6_10142003.html October 14, 2003 "Specifically, the task force will issue a request for public comments in the next 45 days and will subsequently convene a public meeting to gather information about IPv6." ====

1 0

RE: [ipv6-wg@ripe.net] 2001:1700::/27 / CH-SUNRISE-20031124, check your prefix filters
by matthew.ford＠bt.com 12 Dec '03

12 Dec '03

Gert, You should probably change 2001:500::/32 to 2001:500::/30. This is now documented at http://www.arin.net/registration/ipv6/micro_alloc.html. Regards, Mat > -----Original Message----- > From: ipv6-wg-admin(a)ripe.net [mailto:ipv6-wg-admin@ripe.net] > On Behalf Of Gert Doering > Sent: 12 December 2003 13:11 > To: Jeroen Massar > Cc: nanog(a)nanog.edu; ipv6-wg(a)ripe.net > Subject: Re: [ipv6-wg(a)ripe.net] 2001:1700::/27 / > CH-SUNRISE-20031124, check your prefix filters > > Hi, > > On Wed, Dec 10, 2003 at 10:42:22PM +0100, Jeroen Massar wrote: > > At 2003-11-24 RIPE allocated 2001:1700::/27. > > ISP's doing IPv6 prefixlenght filtering should watch out > that they are > > not filtering out the above prefix > [..] > > Easiest way to avoid problems is to regulary check: > > http://www.space.net/~gert/RIPE/ipv6-filters.html > > Thanks for pointing that out to me :-) - I have made the > accompanying text more explicit regarding the > already-allocated /31 and /27. > > Gert Doering > -- NetMaster > -- > Total number of prefixes smaller than registry allocations: > 57386 (57785) > > SpaceNet AG Mail: netmaster(a)Space.Net > Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 > 80807 Muenchen Fax : +49-89-32356-299 > >

2 1

[ipv6-wg@ripe.net] 2001:1700::/27 / CH-SUNRISE-20031124, check your prefix filters
by Jeroen Massar 12 Dec '03

12 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Hi, At 2003-11-24 RIPE allocated 2001:1700::/27. ISP's doing IPv6 prefixlenght filtering should watch out that they are not filtering out the above prefix It is visible in most parts of the world, check: http://www.sixxs.net/tools/grh/lg/?find=2001:1700::/27 But it is also quite easy to see from that list that many ISP's do filter, somewhat fortunatly, but they do have to update their prefix filters ;) Easiest way to avoid problems is to regulary check: http://www.space.net/~gert/RIPE/ipv6-filters.html Even Gert's 'strict' filters allows the above prefix as it is based on the RIR's policies. A 'golden IPv6 network' page will be created to be able to lookup these prefixes without much problems Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / jeroen(a)unfix.org / http://unfix.org/~jeroen/ iQA/AwUBP9eTOimqKFIzPnwjEQKz4wCgn7m7+puSY3uXxoQP+wZ6jPilfpwAn2ru wmQh1E574sqE/iqy6xtK+QS/ =97kN -----END PGP SIGNATURE-----

2 1

[ipv6-wg@ripe.net] IPv6 connectivity in Iran
by Henk Uijterwaal (RIPE-NCC) 11 Dec '03

11 Dec '03

Dear All, At the RIPE NCC regional meeting earlier this week, one of the participants asked me about IPv6 connectivity between a local network there and the rest of the world. I had no idea, but promised to post the question here. So: Is there anybody on this list who offers IPv6 connectivity in Iran _today_? Please reply privately, I'll forward the responses and summarize if there is interest. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(a)ripe.net RIPE Network Coordination Centre WWW: http://www.ripe.net/home/henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ That problem that we weren't having yesterday, is it better? (Big ISP NOC)

2 1

[ipv6-wg@ripe.net] ip6.arpa broken because of arrowroot.arin.net + buchu.arin.net wrongly in .net gtld servers
by Jeroen Massar 28 Nov '03

28 Nov '03

-----BEGIN PGP SIGNED MESSAGE----- ip6.arpa is, according to the root-servers.net boxes hosted on: ip6.arpa. 172800 IN NS ARROWROOT.ARIN.NET. ip6.arpa. 172800 IN NS BUCHU.ARIN.NET. ip6.arpa. 172800 IN NS NS.APNIC.NET. ip6.arpa. 172800 IN NS NS.ICANN.ORG. ip6.arpa. 172800 IN NS NS.RIPE.NET. ip6.arpa. 172800 IN NS SVC00.APNIC.NET. ;; Received 241 bytes from 198.41.0.4#53(A.ROOT-SERVERS.NET) in 97 ms But: $ dig @ARROWROOT.ARIN.NET ip6.arpa ns ; <<>> DiG 9.2.3 <<>> @ARROWROOT.ARIN.NET ip6.arpa ns ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22022 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13 ;; QUESTION SECTION: ;ip6.arpa. IN NS ;; AUTHORITY SECTION: . 86400 IN NS A.ROOT-SERVERS.NET. . 86400 IN NS B.ROOT-SERVERS.NET. . 86400 IN NS C.ROOT-SERVERS.NET. . 86400 IN NS D.ROOT-SERVERS.NET. . 86400 IN NS E.ROOT-SERVERS.NET. . 86400 IN NS F.ROOT-SERVERS.NET. . 86400 IN NS G.ROOT-SERVERS.NET. . 86400 IN NS H.ROOT-SERVERS.NET. . 86400 IN NS I.ROOT-SERVERS.NET. . 86400 IN NS J.ROOT-SERVERS.NET. . 86400 IN NS K.ROOT-SERVERS.NET. . 86400 IN NS L.ROOT-SERVERS.NET. . 86400 IN NS M.ROOT-SERVERS.NET. ;; Query time: 28 msec ;; SERVER: 198.133.199.110#53(ARROWROOT.ARIN.NET) ;; WHEN: Thu Nov 27 22:16:01 2003 ;; MSG SIZE rcvd: 445 There is a oddness here btw: $ dig @aloe.arin.net arrowroot.arin.net ;; ANSWER SECTION: arrowroot.arin.net. 10800 IN A 63.146.182.189 BUT according to the .net servers: $ dig @A.GTLD-SERVERS.net. arrowroot.arin.net ; <<>> DiG 9.2.3 <<>> @A.GTLD-SERVERS.net. arrowroot.arin.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16818 ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 8, ADDITIONAL: 8 ;; QUESTION SECTION: ;arrowroot.arin.net. IN A ;; ANSWER SECTION: arrowroot.arin.net. 172800 IN A 198.133.199.110 Which is the address that is used above and in queries, the arin.net version does work btw. But this does break many queries. Btw ns.ripe.net reports: ip6.arpa. 172800 IN NS ns.ripe.net. ip6.arpa. 172800 IN NS ns.apnic.net. ip6.arpa. 172800 IN NS ns.icann.org. ip6.arpa. 172800 IN NS tinnie.arin.net. So please get these in sync as it is breaking stuff miracously. Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / jeroen(a)unfix.org / http://unfix.org/~jeroen/ iQA/AwUBP8ZsNymqKFIzPnwjEQJbCwCgg/1Fbu/XOhFCY3iM6chmjDc51VEAoLjI jyFWB1H+/c/xJSu/B65Av7LU =oRLs -----END PGP SIGNATURE-----

2 1

[ipv6-wg@ripe.net] First dual-stack IPv4/IPv6 handsets
by David Kessens 05 Nov '03

05 Nov '03

Hi, I think that you might like this news: Last week, Nokia announced the Nokia 7700, the first dual stack GSM/GPRS/EDGE phone: http://www.nokia.com/nokia/0,6771,47550,00.html And this week, the first dual stack CDMA phone was demonstrated: http://press.nokia.com/PR/200311/923589_5.html & http://biz.yahoo.com/prnews/031105/daw010_1.html David K. ---

1 0

[ipv6-wg@ripe.net] Ipv6 addressing plan tool
by susana.caudelitome＠telefonica-data.com 24 Sep '03

24 Sep '03

Hi all. I'm looking for a tool to manage the IPv6 address allocation. Could anyone help me?. Thanks in advance. Regards. Susana. Conozca mejor eBA e-Soluciones de Banda Ancha en http://www.telefonica.es/eba Esperamos su visita en http://www.telefonica-data.es Este mensaje se dirige exclusivamente a su destinatario y puede contener informacion privilegiada o confidencial cuya divulgacion esta prohibida en virtud de la legislacion vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma via y proceda a su destruccion.

2 1

[ipv6-wg@ripe.net] [iesg-secretary@ietf.org: Last Call: 'Delegation of 2.0.0.2.ip6.arpa' to BCP]
by David Kessens 15 Sep '03

15 Sep '03

----- Forwarded message from The IESG <iesg-secretary(a)ietf.org> ----- To: IETF-Announce :; Cc: From: The IESG <iesg-secretary(a)ietf.org> Subject: Last Call: 'Delegation of 2.0.0.2.ip6.arpa' to BCP Date: Sun, 14 Sep 2003 22:04:24 -0400 The IESG has received a request from an individual submitter to consider the following document: - 'Delegation of 2.0.0.2.ip6.arpa ' <draft-ymbk-6to4-arpa-delegation-00.txt> as a BCP The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg(a)ietf.org or ietf(a)ietf.org mailing lists by 2003-10-12. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ymbk-6to4-arpa-delegation-00.txt ----- End forwarded message ----- David K. ---

1 0

[ipv6-wg@ripe.net] Draft minutes for ipv6 wg session RIPE45
by David Kessens 11 Sep '03

11 Sep '03

Hi, Please see below for a draft version of the working group minutes for the ipv6 session at RIPE45. I am sorry for the late posting, I only received the minutes right before the last meeting. The minutes will be declared final by Friday September 26, 2003 if I don't receive any comments other than small typos/corrections. Thanks, David K. --- Draft Minutes IPv6 Working Group RIPE 45 The IPv6 Working Group session Wednesday 14 May, 16.30 - 18.30 A. Administrative Stuff: Chair (David Kessens, Nokia) Scribe (Timothy Lowe, RIPE NCC) Actions: 44.1 RIPE NCC Enable reverse delegation for the 6bone Andrei: after much discussion, 6bone will do it for themselves. #Action point closed# 44.2 Bernard Tuy To co-ordinate an IPv6 routing guideline document Discussion ongoing with Marc Blanchet (Hexago) for more comprehensive document. David: this point is being passed to the routing working group. #Action point closed# 44.3 RIPE NCC To investigate with IANA increasing the size of RIR allocations to rationalize routing David: discussion has begun between the parties so we can close this one. Gert Doering (Spacenet): I see at least 3 /23s being delegated in the interim and this is a shame. David: it is a bit tech and a bit policy so I this might need to go to the LIR working group. John Crain: ICANN There are discussions concerning this with the RIRs about a temporary solution. #action point closed#, discussion moved to policy working group 44.4 RIPE NCC Report back to the working group what the status is and what the issues are regarding: - enabling AAAA glue records in the . zone - AAAA glue records for delegations to TLDs - AAAA glue records for the root servers themselves, enabling ipv6 transport to the . zone John: AAAA in the root there are possible issues with too many AAAA records into the root zone. In the lab we are building a root zone with lots of AAAA queries to prove it is safe. We don't believe there will be any issues but we have some requests for this so we have to come back with proof that it is stable before going ahead. The Root server advisory committee will be asked to approve this before the summer. Mohsen Souissi (AFNIC): The request for comments document from IANA was run by myself and I sent IANA my comments. We have no issues for .fr with AAAA glue records under the root zone. Mr Vixie was asked to comment and had no technical issues. We have been waiting for a long time. John: yes I saw that and according to his draft not RFC but draft it has no issues but we have to ensure that it doesn't just work for .fr but for everyone. Also we have had little comment on his draft and no other tech tests of this. However we see that it is a good idea and we want to have this implemented as soon as possible. David: Who needs to sign off on this? John: inet clue elite David: good, it's not lost in the department of commerce. John: No we just have to present solid evidence to the Department of Commerce so they can approve Andrei:we tried to research this by asking Verisign what registrars support AAAA records. They said they don't know. Fortunately our registrar did it and we found that it was only blocked at the root zone. We wanted to change our registrar but the new one had no interest in doing AAAA dns. David: I think others have the same problem can you make public who is willing to do it? Lars-Johan Liman: can we see a way of changing the name on the right hand side of the ns delegation so that it doesn't conflict with the ns.ripe.net. Like ns6.ripe.net (we already have this see www.ripe.net/reverse) Andrei:I agree we should look into this but it was just to clarify that it should be looked into. David: this a DNS issue so we should pass it to them. Ok we should keep action open so we can hear about progress in this area? Good we keep it. B. Status of the 6bone http://www.kessens.com/~david/presentations/ (David Kessens) 6bone registry is now reachable over v6 in all aspects. Draft phase out plan of the addresses has been proposed. The cut off date for allocating ptlas is 20040101 and the date of phase out is 20060606. Some stats are 60 countries with ptlas in the 6bone C. University of Tennessee IPv6 network storage stack http://www.ripe.net/ripe/meetings/ripe-45/presentations/ ripe45-ipv6-logistic.pdf (Alessandro Bassi - LoCI - Univ of Tennessee) Logistical networking, which is based on distributed network storage, is a project of the UTK Logistical Computing and Internetworking Lab. The LoCI Lab website: http://loci.cs.utk.edu/ D. Global IPv6 routing table status http://www.ripe.net/ripe/meetings/ripe-45/presentations/ ripe45-ipv6-table/ (Gert Doering) Slide 12: Kurtis Lindqvist, Netnod: Can you track which blocks are allocated and which are routed? Also the delay between when the allocation was made and when it was first routed? Gert: My scripts don't do it but I can do that. I will look into it but no promises. Mohsen: Tunis isn't in Europe (refers to slide 15) Gert: sure but its around the mediteranian so around the corner sort of Europe. E. Report(s) about actual v6 traffic volume as compared to v4? http://www.ripe.net/ripe/meetings/ripe-45/presentations/ ripe45-tt-ipv6/page1.htm (Henk Uijterwaal, RIPE NCC) The test traffic project is now also able to measure the ipv6 Internet. F. Developments/initiatives in the RIPE region and beyond -Presentation (Bernard Tuy, RENATER) Geant IPv6 service M6bone worldwide deployment and multicast protocols for IPv6 6Net and on going IPv6 experiments G. Input for the RIPE NCC Activity Plan (No input from the audience) Z. AOB -----

1 0