Presentation is available at:http://www.kessens.com/~david/presentations/

Per 20020911, there are now 1187 ipv6 sites in 58 different countrieson the ipv6 Internet.

C. IPv6 version of TTM (Henk Uijterwaal (HU))======================

Presentation is available at:http://www.ripe.net/ripe/meetings/archive/ripe-43/presentations/ripe43-ipv6-ttm/

Wilfried Woeber (WW): With 6net hat - is possible to make preliminarymeasurements available before the end of the year?

DK: How is this service supported from the commercial point of view? Right now, you have to pay for the test-box.HU: You still have to buy a test box, and we operate it for you. Service fee is currently 3000 EUR.

Q: Do you get v4 measurements with that, too?A: In principle, yes.

WW: Technical question: the ntp protocol is used to encode v4 from clock-host partners to prevent forming loops. Anyone here knows more?HU: forward me the emails from the discussion.

DK: I like this new service. This can be a reason for me to order such a box, because v6 production is important for us, and I want to be able to measure the performance.

D. Action point 42.1:=====================Investigate the CNAME and other solutions for v6-reverse delegation

In regards to D & E, a prototype was made; setups how to support themwas tested; no final decision yet. Status: in progress.

It will be accomplished before the next ripe meeting

Mohsen Souissi (MS): Are you aware of the technical notes, published lastweek, about DNAME, by the IETF committee? This is only meant for thesmooth transition from .int -> .arpa

Things are moving very very slowly. There is no dns server for ip6.arpa."ns.ripe.net" is not ipv6-capable.

I have already suggested several times to IANA that AFNIC server isavailable to be a secondary for ip6.arpa, but I received no answer...

DK: There is an agenda point in the AOB about the Activity Plan of the RIPE NCC. We need to add this in there. My suggestion is that the RIPE NCC members make it clear to the RIPE NCC and the RIPE NCC Board that we want RIPE NCC to give some real attention to this.

Presentation is available at: http://www.ripe.net/ripe/meetings/archive/ripe-43/presentations/ripe43-ipv6-table/

Q: Do you see people changing over, or announcing both?A: It was possible to see everything, all combinations.

Q: Are the filtering problems still there?A: Not really, but old prefix was still in the table, although I was not announcing it any more...

Q: Do you see any difference between number of announcements vs number of allocations per region?A: This was not researched, it's a good idea for the next time.

Bernard Tuy (BT): While discussing the filters - we are at the point when we do need some recommendations from the RIPE community.DK: 6bone/IETF docs exist. Do we need new ones?GD: They need re-doing, can not be accepted by default.DK: Do we need recommendations?GD: We need to at least keep an eye on this, and think about it. We also need to think about multihoming issue. Let's put it on the agenda for the next meeting.DK: Any opinions right now?

GD: Just one customer is doing it - "announcing more specific prefix" ?? I find it a good solution.

Francis Dupont (FD): That does not scale. It is too easy. ISPs do not want to buy GB of memory to support this. But there's no good alternative solution.

GD: Multihoming needs to be done by BGP : either /32, or /48 that can get filtered. There are two groups busy with it in the IETF, official&dead, and another one...

Proposal for the presentation on the next meeting - "Approaches tomultihoming and why everything sucks".

FD: "ipv6mh" is good place to discuss this. It's a closed mailing list.

DK: Personally, I think the way Gert is doing it is a good way.

DK: Anyone who is a good candidate to lead the discussion, present existing solutions and explain why they don't work, please volunteer for the next meeting.

H. Report(s)============

About *actual* v6 traffic volume as compared to v4?What's *real* out there, not what's on power-point?

Q: How up to date are your graphs, and can you see RIPE43 meeting influence?A: From last Friday, so can't see this meeting.

Q: different considerations - DNS traffic as protocol, and v6 traffic after DNS queries. how to get v6 related RRs. unless you have v6 from the root, except the glue, you don't know where else to go.

Q: Can you see where are the queries coming from?A: These were the baseline measurements, not analysis. But, most cam from Japan.

MS:.jp & .fr have been supporting v6 in DNS for years. We are asking for glue records in root, but according to the policy that is not possible. We are again asking RIPE NCC to support our efforts to tell to the root - v6 is harmless.

DK:In the Activity Plan input to the RIPE NCC, we should be making it clear that this is important to us, as members of the RIPE community.

[coffee break]

H.2 some snap-shot info----------------------(Wilfried Woeber)

[URL - Presentation missing!]

DK: For the next RIPE meeting we will be preparing dns/v6/sec workshop.

H.3 Discussion--------------

Do we want some more activity under this topic - to cover it in depth; tohave more data? e.g TTM with more data.

Since this is a _working_ group, more work from the participants isappreciated...

I. Developments/initiatives===========================regarding IPv6 in the RIPE region and beyond(input from the audience)

I.1 Bernard Tuy, Renater------------------------

We are deploying M6bone. 40 players, 15 non-fr countries. If you areinterested, you are more then welcome to join us.

http://sem2.renater.fr/m6bone/What do we want to achieve, what kind of SW is used...

I.2 Robert Blechinger, CyberNet-------------------------------

Number of queries per day, on their DNS server: 28 6bone, 2 6to4, 336RIPE NCC allocated: 211 own, 115 from one peer.

Please let your representatives tell to the RIPE NCC management andExecutive Board your requirements, so that they can be included in theActiviy Plan.

Z.2. 6bone transition to the RIRs----------------------------------

There has been a talk in the LIR-WG regarding that. 6bone addresses arecurrently allocated by Bob Fink, which is inconvenient as being a singlepoint of failure, and is outside of the RIR structure. If interested, makesure to take part in the discussion on the lir-wg list & meetings. Theprogres of the co-ordination efforts will be reported on the next meeting.

The most important are the technical issues - ip6.int & ip6.arpa delegations.They will be put on the agenda for the next meeting.

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacy policy. You can accept our cookies either by clicking here or by continuing to use the site.