- 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

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

10 Sep '03

Hi, Please see below for the draft minutes of the ipv6 wg session at RIPE46. We are still missing a few URLs for presentations. The minutes will be declared final by Friday September 26, 2003 if I don't receive any comments other than small typos and provided that I receive the missing urls for the presentations by that date. I hope this helps, David K. --- Draft minutes for the IPv6 Working Group Meeting RIPE46 When: 16:00 - 17:30, Wednesday September 3, 2003 Where: Grand Ballroom, Hotel Krasnapolsky, Amsterdam Who: Chair: David Kessens Scribe: Pierre Baume A. Administrative stuff - appointment of scribe: Pierre Baume (RIPE NCC) - agenda bashing http://www.kessens.com/~david/presentations/ (David Kessens) Agenda point D below dropped. B. Status of the 6bone http://www.kessens.com/~david/presentations/ (David Kessens) - no new 6bone addresses will be allocated from 1/1/2004. - allocated 6bone addresses will not be valid anymore after 6/6/2006 C. Reports from the IETF - multi6 working group summary missing url (Kurt Erik Lindqvist) Illjitsch van Beijnum: Who else is on the design team(s)? David Kessens: I will send the names I have to the list. D. Update on ttm progress (Henk Uijterwaal) Dropped from agenda. E. Global IPv6 routing table status - Global IPv6 routing table status (Gert Doering) http://www.space.net/~gert/RIPE/R46-v6-table/ http://www.space.net/~gert/RIPE/R46-v6-table.pdf - IPv6 routing table anomalies http://www.sixxs.net/tools/grh/ (Jeroen Massar) F. 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) Nothing to report. G. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) - RENATER's IPv6 activity missing url (Bernard Tuy) Geza Turchanyi: What is the presentation's URL? Bernard Tuy: Visit http://www.m6bone.net/. H. Input for the RIPE NCC Activity Plan (input from the audience) None. Z. AOB None. Action (for Everybody) - Read the Activity Plan 2004 and tell the RIPE NCC/Board what you want! ----

1 0

RE: [ipv6-wg@ripe.net] IPv6 Webcast
by matthew.ford＠bt.com 04 Sep '03

04 Sep '03

Thanks for helping Jeroen. My problems were entirely firewall related. Sorry for bothering you all. Mat > -----Original Message----- > From: Jeroen Massar [mailto:jeroen@unfix.org] > Sent: 04 September 2003 00:48 > To: Ford,M,Mat,XGH5 FORDM5 R; ipv6-wg(a)ripe.net > Cc: ripecast(a)ripe.net > Subject: RE: [ipv6-wg(a)ripe.net] IPv6 Webcast > > > -----BEGIN PGP SIGNED MESSAGE----- > > matthew.ford(a)bt.com wrote: > > > OK, so now all links from > > http://www.ripe.net/ripe/meetings/ripe-46/webcast.html are > not working > > for me. The IPv6 link appears to connect but bombs out while > > 'buffering'. Is anyone succesfully connected at the moment? > > Currently (01:42 CET/Amsterdam time) there are no broadcasts thus > one can't watch them either. The archives (bottom of the page) > work, at least the IPv6-wg one did with Windows Mediaplayer 9 over > my home DSL line. I haven't tested the live feeds but I understood > from Jakub Vlasek (.cz) that he had quite a clear live feed there...

1 0

RE: [ipv6-wg@ripe.net] IPv6 Webcast
by matthew.ford＠bt.com 04 Sep '03

04 Sep '03

OK, so now all links from http://www.ripe.net/ripe/meetings/ripe-46/webcast.html are not working for me. The IPv6 link appears to connect but bombs out while 'buffering'. Is anyone succesfully connected at the moment? Mat > -----Original Message----- > From: matthew.ford(a)bt.com [mailto:matthew.ford@bt.com] > Sent: 02 September 2003 15:38 > To: cfriacas(a)fccn.pt; ipv6-wg(a)ripe.net > Cc: ripecast(a)ripe.net > Subject: RE: [ipv6-wg(a)ripe.net] IPv6 Webcast > > > this is funny - the only server that works for me is the ipv6 > server :-) > > mat > > > -----Original Message----- > > From: Carlos Friacas [mailto:cfriacas@fccn.pt] > > Sent: 02 September 2003 14:30 > > To: ipv6-wg(a)ripe.net > > Cc: ripecast(a)ripe.net > > Subject: [ipv6-wg(a)ripe.net] IPv6 Webcast > > > > > > > > Hello, > > > > I've noticed today that CEZNET is providing a streaming > > server (RIPE-46 > > sessions) with IPv6: > > > > + server6.streaming.cesnet.cz > > + 2001:718:1:7:230:48ff:fe42:30de > > + traceroute6 is OK from here (11 hops) > > + ping6 is OK from here (55 avg rtt) > > > > However, im failing to see the session using version 9.00.00.3008 of > > MediaPlayer and VideoLan 0.5.2 under WinXP (and it works fine > > on the v4 > > streaming servers with both clients...) > > > > Has anybody tried this v6 server? Can anybody give me an > hint on this? > > > > Thanks in advance. > > > > Regards, > > > > ./Carlos "Upgrade the > > Internet! -- Now!" > > -------------- [http://www.ip6.fccn.pt] > > http://www.fccn.pt > > <cfriacas(a)fccn.pt>, CMF8-RIPE, CF596-ARIN, > > Wide Area Network Workgroup > > FCCN - Fundacao para a Computacao Cientifica Nacional > > fax:+351 218472167 > > > > "Internet is just routes (125953/461), naming (millions) > > and... people!" > > > > > >

3 2

RE: [ipv6-wg@ripe.net] IPv6 Webcast
by matthew.ford＠bt.com 02 Sep '03

02 Sep '03

this is funny - the only server that works for me is the ipv6 server :-) mat > -----Original Message----- > From: Carlos Friacas [mailto:cfriacas@fccn.pt] > Sent: 02 September 2003 14:30 > To: ipv6-wg(a)ripe.net > Cc: ripecast(a)ripe.net > Subject: [ipv6-wg(a)ripe.net] IPv6 Webcast > > > > Hello, > > I've noticed today that CEZNET is providing a streaming > server (RIPE-46 > sessions) with IPv6: > > + server6.streaming.cesnet.cz > + 2001:718:1:7:230:48ff:fe42:30de > + traceroute6 is OK from here (11 hops) > + ping6 is OK from here (55 avg rtt) > > However, im failing to see the session using version 9.00.00.3008 of > MediaPlayer and VideoLan 0.5.2 under WinXP (and it works fine > on the v4 > streaming servers with both clients...) > > Has anybody tried this v6 server? Can anybody give me an hint on this? > > Thanks in advance. > > Regards, > > ./Carlos "Upgrade the > Internet! -- Now!" > -------------- [http://www.ip6.fccn.pt] > http://www.fccn.pt > <cfriacas(a)fccn.pt>, CMF8-RIPE, CF596-ARIN, > Wide Area Network Workgroup > FCCN - Fundacao para a Computacao Cientifica Nacional > fax:+351 218472167 > > "Internet is just routes (125953/461), naming (millions) > and... people!" > >

1 0

[ipv6-wg@ripe.net] IPv6 Webcast
by Carlos Friacas 02 Sep '03

02 Sep '03

Hello, I've noticed today that CEZNET is providing a streaming server (RIPE-46 sessions) with IPv6: + server6.streaming.cesnet.cz + 2001:718:1:7:230:48ff:fe42:30de + traceroute6 is OK from here (11 hops) + ping6 is OK from here (55 avg rtt) However, im failing to see the session using version 9.00.00.3008 of MediaPlayer and VideoLan 0.5.2 under WinXP (and it works fine on the v4 streaming servers with both clients...) Has anybody tried this v6 server? Can anybody give me an hint on this? Thanks in advance. Regards, ./Carlos "Upgrade the Internet! -- Now!" -------------- [http://www.ip6.fccn.pt] http://www.fccn.pt <cfriacas(a)fccn.pt>, CMF8-RIPE, CF596-ARIN, Wide Area Network Workgroup FCCN - Fundacao para a Computacao Cientifica Nacional fax:+351 218472167 "Internet is just routes (125953/461), naming (millions) and... people!"

1 0

[ipv6-wg@ripe.net] Agenda for ipv6 wg RIPE46
by David Kessens 27 Aug '03

27 Aug '03

Hi, Below follows the agenda for the ipv6 wg for RIPE46. We still have some time left in the agenda so I will be accepting last minute additions. Thanks, David K. --- Agenda for the IPv6 Working Group Meeting RIPE46 When: 16:00 - 17:30, Wednesday September 3, 2003 Where: Grand Ballroom, Hotel Krasnapolsky, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of the 6bone (David Kessens) C. Reports from the IETF - multi6 working group summary (Kurt Erik Lindqvist) D. Update on ttm progress (Henk Uijterwaal) E. Global IPv6 routing table status - Global IPv6 routing table status (Gert Doering) - IPv6 routing table anomalies http://www.sixxs.net/tools/grh/ (Jeroen Massar) F. 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) G. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) H. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0

[ipv6-wg@ripe.net] Re: [db-wg] Whois IPv6 proxy status (was RIPE Whois Server version 3.2.0)
by Shane Kerr 14 Aug '03

14 Aug '03

Gert, Gert Doering wrote: > > as there have been some IPv6 problems again today (connections over IPv6 > were greeted with "permission denied"): what's the current state of IPv6 > integration into the RIPE Whois server? Is it still done via Proxy, or > is it properly integrated now? Thanks for reporting the problem. We noticed it ourselves, and are looking into it. Looks like a mismatch of the configuration of our secondary server during an upgrade caused the problem. We're looking into fixing that now. As for the state of IPv6 integration... We are still using the proxy. We continue to get about 10000 WHOIS queries per day on IPv6, with the majority coming from a small number of addresses (about 0.5% of our queries). I haven't done any further analysis since the last RIPE meeting (RIPE 45): http://www.ripe.net/ripe/meetings/ripe-45/presentations/ripe45-db-whoisdb-u… I'd like to emphasize that the reason we chose to use a proxy is *not* because it was easier or faster to implement, or because we wanted to understand the technology better. I talked a bit about the reasons in the presentation I gave at RIPE 44 when we introduced the proxy: http://www.ripe.net/ripe/meetings/archive/ripe-44/presentations/ripe44-ipv6… The main point is that we currently use client IP address to limit the amount of personal data that a user can query. This does not make sense in the IPv6 universe. While using client IP to identify users is imperfect in an IPv4 world, it is even less meaningful in the IPv6 world. We simply don't know how to protect the privacy of our users in the IPv6 world! The main motivation for the proxy was to study access behaviour and how, if at all, we can effectively protect user's privacy. From the user point of view, the proxy should be identical to a "native" server. When we fix our config, it transparent again! One possibility that may address the client-identification issue is to move to a protocol that supports client authentication. The CRISP protocol, currently in discussion in the IETF, promises to offer such a feature. It is intended to be something that serves the same function as WHOIS, while fixing many of the limitations. http://www.ietf.org/html.charters/crisp-charter.html As I mentioned in the past, I am very eager to hear suggestions on how to deal with the privacy issue in IPv6! Any real-world experience from IPv6 operators or developers would be appreciated. We do have several months of logs now, so we can do some data mining to check theories. -- Shane Kerr RIPE NCC

4 4

[ipv6-wg@ripe.net] Minutes IPv6 working RIPE44
by David Kessens 12 Aug '03

12 Aug '03

Hi, I didn't receive any comments or corrections for the draft minutes (v1) posted on May 8, 2003 for the ipv6 working group at RIPE44. Therefore, the draft minutes are now the final minutes. David K. --- Minutes IPv6 working RIPE 44 Meeting: IPv6 Working Group - RIPE 44 Date: Wednesday, 29 January, 2003 Time: 2pm - 4pm Chair: David Kessens (DK) Scribe: Timothy Lowe Webcast: rtsp://webcast.ripe.net:7070/Archive/ipv6-1.rm A. Administrative stuff - Agenda bashing Agenda available at: http://www.kessens.com/~david/presentations/ - No new agenda updates were proposed B. IPv6 version of TTM - Henk Uijterwaal http://www.ripe.net/ripe/meetings/archive/ripe-44/ presentations/ripe44-ipv6-ttm/ - No questions or comments were made C. Presentation - IPv6 whois proxy - Shane Kerr (SK) http://www.ripe.net/ripe/meetings/archive/ripe-44/ presentations/ripe44-ipv6-v6wpd/ Gert Dvring (GD): Will IPv6 be integrated into the main whois server, not just on the proxy server? SK: Those are our future plans but their some issues including security issues that need to be worked out first. DK: Don't put all your efforts into proxies. SK: We won't. D. IPv6 state of the art in the Italian educational and research community. - Gabriella Paolini (GP) Francis Dupont: Don't use /126 for point to point links GP: It avoids unnecessary waste. Speaker: (Did not use microphone) It includes loopback and network so it is DK: We can come up with a best current practice document on numbering v6 networks as an agenda point for next time. E. Global IPv6 routing table status - Gert Dvring (GD) Bernard Tuy (BT): Improving routing is something we should be working on. GD: Yes maybe a best current practice document. BT: Do we want a guideline document? GD: It would be useful DK: There is a 6bone document that describes this. BT: I want a RIPE document on this and volunteer to write one DK: Action on Bernard to co-ordinate for a routing document. Philip Smith (PFS): Would an IPv6 CIDR Report be useful? DK: Yes PFS: Fine, then Geoff and I will get on that. PFS: We provide transit to anyone at all right now. We want to change this we can discuss this later. DK: I am also encouraging people to look for other transit then from me. GD: I wish to keep the link to Cisco now with the shorter path lengths. PFS: All right I would appreciate any feedback. F. Ghost Route Busters - Jeroen Masser (JM) http://www.ripe.net/ripe/meetings/archive/ripe-44/ presentations/ripe44-ipv6-ghosts/ Randy Bush (RB): What is TLA? JM: Top Level Aggregater RB: What? A short exchange on the deprecation the TLA syntax followed. G. Traffic graphs Jeroen Masser Presentation was not given but is available from: http://www.ipv6.aorta.net H. 5 year trend in the BGP table Ronald van der Pol http://www.nlnetlabs.nl/ipv6/measurements/index.en.html I. Workable approaches for IPv6 multihoming in the absence of a better solution than the one we use in the IPv4 Internet - Iljitsch van Beijnum (IvB) http://www.bgpexpert.com/ripe44/ BT: Why is the draft not out? IvB: The IETF can't agree on it. BT: We could write a draft here? DK: Bernard that is IETF work IvB: It is possible that we could submit a draft to them but let me finish here my presentation and we can discuss it later. Clemens Zauner (CZ): Putting multi addressing and multihoming in the same presentation is not so logical. IvB: Are you saying if you are doing multi addressing you are not really doing multihoming? DK: There are people that say if you do multi addressing right now you don't need to multihome. CZ: Also most of the deaggregation taking place is not due to multihoming. IvB: I agree this premise is false even if every ISP announces 10000 routes .... CZ: Even so I don't belive in millions of multihomers. IvB: Neither do I but v4 style multihoming won't scale. CZ: Even so I don't belive multihoming will break things if you look at it now. IvB: Yes but we also have to think 20 years ahead. CZ: Maybe we could make them prove a need for multi homing IvB: There is the possibility of coming up with an administrative solution like that but one solution could be to make them pay a fee. You cannot have an upstream for free whether it is one or many upstreams. GD: There are a number of routes that shouldn't be there but are for traffic engineering reasons. A reason for multihoming that I see is that they want connectivity redundancy due to ISP bankruptcies. IvB: I want to take this discussion offline to go into it further J. IPv6 Multihoming part 2 - Kurt Erik Lindqvist (KEL) http://www.ripe.net/ripe/meetings/archive/ripe-44/ presentations/ripe44-ipv6-multihoming/ GD: I like this idea. of increasing the allocation from IANA to the RIR's. Make it an action on the RIPE NCC to talk to IANA about this. If this gets out of hand we can roll it back. It is pretty radical. KEL: It is not a long term solution but it buys us time. IvB: 64,000 multihomers is not the upper limit. KEL: Even so it still won't break routers at twice as many. DK: Should we go to routing with this? GD: Yes. KEL: Yes K. Discussion point - Fragmentation of the IPv6 address space from the top down by allocating /23's to RIRs - Gert Dvring AOB DK: Another IPv6 survey is in the works and the RIPE NCC needs input on what questions to ask in the survey. Please give them input. BT: Presenting useful data is a good idea if you have any ideas on this pass them on. Also we have a v6 project the M6bone please come play with us. DK: We arranged this working group session to avoid overlap with the other working group sessions and we have moved topics to other appropriate wg's. We would like input on if you like this approach. Please inform me. I. Workable approaches for IPv6 multihoming in the absence of a better solution than the one we use in the IPv4 Internet - Kurt Erik Lindqvist, Iljitsch van Beijnum brief discussion K. Developments/initiatives regarding IPv6 in the RIPE region and beyond input from the audience L. Input to the RIPE NCC Activity Plan & results of KPMG survey input from the audience DK: It is very important that the RIPE community tells the RIPE NCC what IPv6 activities should be put into the activity plan Z. AOB Agenda point for RIPE 45 best current practice document on numbering IPv6 networks Action Points from Previous meetings: 42.1: Investigate the CNAME and other solutions for IPv6 reverse delegation - RIPE NCC 42.2: Give an overview of 6-to-4 reverse delegation issues at RIPE 43 - RIPE NCC 42.3: IPv6 capable RR DNS servers - what is needed, what are the issues? - RIPE NCC Action points 42.1-3 were rewritten and closed. New Actions Points: 44.1 Enable reverse delegation For 6bone (RIPE NCC) 44.2 To co-ordinate an IPv6 routing guideline document (Bernard Tuy) 44.3 To investigate with IANA increasing the size of RIR allocations to rationalize routing (RIPE NCC) 44.4 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 and come back with ideas on how these issues can be overcome (RIPE NCC). -----------

1 0

[ipv6-wg@ripe.net] Call for agenda items & draft agenda (v1) for ipv6 wg RIPE46
by David Kessens 12 Aug '03

12 Aug '03

Hi, Below follows the draft agenda (v1) for the ipv6 wg for RIPE46. Please contact me if you would like to propose an agenda item. Thanks, David K. --- Draft Agenda (v1) for the IPv6 Working Group Meeting RIPE46 When: 16:00 - 17:30, Wednesday September 3, 2003 Where: Grand Ballroom, Hotel Krasnapolsky, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Status of the 6bone (David Kessens) C. Global IPv6 routing table status (Gert Doering) D. 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) E. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) F. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0