- ipv6-wg - mailman.ripe.net

[ipv6-wg@ripe.net] Apologises
by Bernard Tuy 28 Jan '04

28 Jan '04

====BT: David and all, Since a couple of people were surpised to see me at the meeting although I didn't show up in the ipv6 wg, I feel I have to give some explanations. My yesterday morning flight was cancelled and I had to book for another one 3 hours later. Then when the ipv6 wg meets I was about to land in Schipol airport.... It seems that in some european countries 5 cm of snow is enough to completely mess airway traffic. I'm pretty sure it must appear weird to people from countries where most of the airports are under the snow several months a year ... but that's it. So sorry not to be able to attend the meeting since I'd have like to be able to hear lot of intersting topics schedulded on the agenda and to have the possibility to present what I'd prepared. The consolation is I probably wouldn't have been able to fit my 26 slides in 10-15 mn. So may I require a half an hour slot for the next meeting in May ? See you on the mailing list -or at Krasnapolski until friday noon... Cheers, +Bernard T.

1 0

[ipv6-wg@ripe.net] Minutes for the ipv6 wg session RIPE46
by David Kessens 19 Jan '04

19 Jan '04

Hi, We didn't receive any comments on the minutes in the comment period so the draft minutes (v1) are now declared final. Please see below for the minutes of the ipv6 wg session at RIPE46. I hope this helps, David K. --- 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 (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 (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. ----

1 0

[ipv6-wg@ripe.net] Minutes for the ipv6 wg session RIPE45
by David Kessens 19 Jan '04

19 Jan '04

Hi, We didn't receive any comments on the minutes in the comment period so the draft minutes (v1) are now declared final. Please see below for the minutes of the ipv6 session at RIPE45. David K. --- 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] Agenda ipv6 wg RIPE47
by David Kessens 19 Jan '04

19 Jan '04

Hi, Below follows the agenda for the ipv6 wg for RIPE47. Note that we are meeting on tuesday instead of the usual wednesday slot. We occasionally change meeting time/date in order to make sure that we are not always scheduled with the same working group so that people who are interested in the other working group have a chance to go to that session for a change. Thanks & see you all on tuesday, David Kessens --- Agenda for the IPv6 Working Group Meeting RIPE47 When: 14:00 - 15:30, Tuesday January 27, 2004 Where: St Johns II, Hotel Krasnapolsky, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Ranges of ipv6 addresses and their use (Jeroen Massar) 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) - Tunnel Detection Tool (Lorenzo Colitti, RIPE NCC, TTM project) - IPv6 Network Management (Bernard Tuy) E. Operational issues with IPv6: RPSLng testing, policy issues, filtering practices, peering (Simon Leinen, Swiss IPv6 task force & swiss IPv6 operations group) F. Developments/initiatives regarding IPv6 in the RIPE region and beyond (input from the audience) - latest IPv6 Land Speed Record (Edoardo Martelli, CERN, time allowing) G. Input for the RIPE NCC Activity Plan (input from the audience) Z. AOB ---

1 0

[ipv6-wg@ripe.net] New IPv6 Address Block Allocated to RIPE NCC
by leo vegoda 12 Jan '04

12 Jan '04

Dear Colleagues, The RIPE NCC received the IPv6 address range 2001:1A00::/23 from the IANA in January 2004. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: <http://www.ripe.net/ripe/docs/smallest-alloc-sizes.html> Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

[ipv6-wg@ripe.net] FW: New IPv6 Allocation (2001:1a00::/23)
by Jeroen Massar 10 Jan '04

10 Jan '04

-----BEGIN PGP SIGNED MESSAGE----- FYI, please adjust filters etc if you have set them. Reference filter set: http://www.space.net/~gert/RIPE/ipv6-filters.html Greets, Jeroen - -----Original Message----- From: Steve Conte [conte(a)iana.org] Sent: Saturday, January 10, 2004 1:47 AM To: nanog(a)merit.edu Subject: New IPv6 Allocation Greetings, This is to inform you that the IANA has allocated 2001:1A00::/23 to the RIPE NCC. For a full list of IANA IPv6 allocations please see: <http://www.iana.org/assignments/ipv6-tla-assignments>. Thanks, Steve - --------------- Steve Conte - IANA conte(a)iana.org PGP KeyID: 0x0972C473 -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / http://unfix.org/~jeroen iQA/AwUBP/9TrSmqKFIzPnwjEQK/gQCfaceFBP53zGBUGIqDXd7xkggNhk4An3Q0 li6/dxHnvSZm81DheQYCzRoM =/hGY -----END PGP SIGNATURE-----

1 0

[ipv6-wg@ripe.net] Call for agenda items and Draft Agenda (v1) for ipv6 wg RIPE47
by David Kessens 29 Dec '03

29 Dec '03

Hi, Below follows the draft agenda (v1) for the ipv6 wg for RIPE47. Note that we are meeting on tuesday instead of the usual wednesday slot. We occasionally change meeting time/date in order to make sure that we are not always scheduled with the same working group so that people who are interested in the other working group have a chance to go to that session for a change. I need your help to make the working group session interesting. Please let me know if you have any suggestions for agenda topics that you would like to have covered during the meeting or if you would like to contribute to one of the 'input of the audience' agenda items. Thanks, David K. --- Draft Agenda (v1) for the IPv6 Working Group Meeting RIPE47 When: 14:00 - 15:30, Tuesday January 27, 2004 Where: St Johns II, Hotel Krasnapolsky, Amsterdam A. Administrative stuff - appointment of scribe - agenda bashing (David Kessens) B. Ranges of allocated ipv6 addresses and their use (Jeroen Massar) 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 ---

2 1

[ipv6-wg@ripe.net] RE: /48 micro allocations for v6 root servers, was: national security
by Jeroen Massar 16 Dec '03

16 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- Paul Vixie wrote: > > /35 routes are being discouraged in favor of /32 entries... > > 4,064,000,000 addresses to ensure that just one host -might- > > have global reachability. IMHO, a /48 is even overkill... :) > > i think the important points for ietf@ to know about are (a) that this > is an open issue, (b) that it's generally agreed that all the > RIR's ought to have the same rules regarding microallocations, and (c) > exactly where (as in what working group or mailing list or smoke filled room) the > discussion is being held. for example, bill says above that > "/35 routes are being discouraged" and that's probably true but "by > whom?" and "where?" There are currently quite some ISP's who filter anything >/35. Generally ISP's should be filtering on allocation boundaries. Thus if a certain prefix is allocated as a /32, they should not be accepting anything smaller (/33, /34 etc) Checking http://www.sixxs.net/tools/grh/tla/all/ 8<------------ The database currently holds 630 IPv6 TLA's. Of which 18 (2.86%) are returned to the pool, 202 (32.06%) IPv6 TLA's didn't have a routing entry. Thus 410 (65.08%) networks are currently announced. 0 (0.00%) only announced a /35 while they have been assigned a /32. 13 (2.06%) announce both their /32 and their /35. - ------------>8 I have to add that there is an error here as 2001:dc0::/35 is in the tables, but doesn't get picked up by the software, will be fixing that soonish. Generally if you announce a /35 it will get through to most ISP's. But we should be avoiding that. Currently the ipv6 global routing table is quite small, but it could grow quite large and when ISP's still don't filter correctly, or better if ISP's don't aggregate it will explode and we will be needing the follow up to BGP soon, which is more work for the IETF :) As for which smoked filled room, this should be a task of the RIRs, thus RIPE's IPv6 WG etc. but it usually takes place when communicating between ISP's. Notice that many ISP's use Gerts list: http://www.space.net/~gert/RIPE/ipv6-filters.html I would applaud a generic /32 that is 'allowed' to being cut up into multiple /48's for the purpose of critical infrastructure. But please, keep it to 1 *documented* /32. That way people will know that they will see more specifics from that prefix and that they should be accepting it too. Currently the !3! IX blocks (2001:7f8::/32 + 2001:504::/32 + 2001:7fa::/32) are seen being announced in pieces too. Maybe these IX blocks, which are common already could be used for assigning 'critical infra' from? This is a RIR thing and should be discussed there (ipv6-wg cc'd). The IETF though should ofcourse advise in all matters. 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/AwUBP9TmwCmqKFIzPnwjEQIk9gCfWIZU0RJA3OGyrbOFTa1+ZIvSDE4AniOW qOqG5k7653xd5LaLSLUAglde =mqwa -----END PGP SIGNATURE-----

11 18

[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