IPv6 Council - Belgium
Still running IPv4 at 54.163.20.123...
Home > Qu’est l’IPv6 Council ? > Meeting Notes of 2nd Meeting of the IPv6 Council Belgium

Meeting Notes of 2nd Meeting of the IPv6 Council Belgium

Thursday 3 May 2012, by Eric Vyncke

IPv6 Council – Belgium – Meeting 23rd March 2012

Welcome

by Carl Wuyts as he kindly hosted the conference at Technicolor, Edegem.

What has happened since last time? Eric Vyncke, IPv6 Council

01-IPv6 Council Belgium.pdf

See attached presentation.

Katia Bodard (ICCC and VBO/FEB) announces the IPv6 for SMB workshop of 12th of June organized by several organizations (Agoria, BELTUG, SPF/FOD Economy, VBO/FEB) but without the IPv6 Council participation…

Mobistar and Mobistar Enterprise Service (MES), Benoit Verougstraete

02-Mobistar.pdf

IPv4 address exhaustion of their pool is expected for 2014 even if NAT is used for mobile customers.
Wireline roadmap is dual stack in 2012-2013 and native V6 only + tunnel in 2014 using DS-Lite. Side discussion about which xDSL modem may officially be used in Belgium: BBox and FritzBox. It appears that Belgacom will issue a new procurement for the next gen BBox that could support IPv6 in 2013.
The roadmap for mobile is the same where NAT64 will be used.
For L3VPN, Mobistar will use 6VPE.
Changes in IT back-end systems are huge. Other interested parties include marketing.

Open discussion among all participants (too many of them: the scribe was unable to attribute a statement to an individual): what about reverse DNS? Some people in the room believe that this is a requirement (notably for email) and is mostly impossible to do in IPv6. PowerDNS is said to be able to fix this issue. Belgacom will use DHCP-PD and SLAAC on the LAN. 42% of ADSL customers are using retail CPE.

Alpha Networks, Benoit Auquier

They have IPv6 addresses for a long time, their core is v6 enabled, dns, email, OSS and BSS are either v6 or will be there shortly.

Residential ISP

EDPnet, (Eric Vyncke, as a EDPnet subscriber)
Native IPv6 deployment, currently under pilot. Eric runs PPPoE through Belgacom Sagem VDSL modem terminated on a router. EDPnet uses DHCP-PD to allocate a mostly static prefix to their subscribers.

Telenet (Hans Thienpondt)
Ready for business customers on request for now, residential is in the lab.

Belgacom (Arnaud Hautem)
As published last year in a press release, business customers of Explore will get IPv6 this year. Next phase: IPv6 solution for residential market is in test in lab and could become available in Q1 or Q2 2013.

DNS.be, Thomas Dupas

03-DNS.be.pdf

The .be zone contains 1 million domain names, 60.000 glue records and currently 100 IPv6 glue records. 15-20% of requests are for AAAA so a lot of recursive servers are IPv6 enabled (or the positive negative caching of DNS). 5% of the requests are coming over IPv6.
They have a new DC, they wanted to run IPv6 only but some applications were IPv4 only.

DNS.be web site, whois server are IPv6 enabled, the LAN is configured as /124 to prevent remote cache exhaustion attack with static address and no SLAAC.
They will enable IPv6 on more secondary servers in 2012.
Discussion about spam and volume traffic of email and sender base.

KULeuven, Wim Vandersmissen

04-KULeuven.pdf

40.000 students and 10.000 started to use IPv6 in January 2011; it was mainly computer science department and students. KULeuven has issues with colliding RFC 1918 addresses when connecting with a lot of other institutions as they merge with several other institutions. KULeuven also wants global coverage to future IPv6 only countries. Using EIGRP for v6 as they do for IPv4, using loop back addresses but link-local addresses only in infrastructure. Do not forget to protect the access of the routers through IPv6. Host and network firewalls were protected day 1.

ISATAP is used in dormitories, which works out of the box with windows 7. As the ISATAP router is behind the firewall, students must use a web interface in order to open a hole in the firewall for ISATAP, without publicity 400 students peak are using it. Using scapy (packet generator) to restart the tunnel by sending a RS because the first and only RS sent by Windows was blocked by the firewall and it not retransmitted.

Web server was enabled by a load balancer doing address family translation, 0,5% of the traffic is IPv6. DNS server is also IPv6 and receives 1% of IPv6 traffic. Postfix has 1.4% of outgoing email over IPv6, issue is mainly blocking spam.

Future: perhaps becoming a LIR to get a /32, new IPv6-enabled servers: DHCP, NTP, NFS and WiFi (with the latest release to have security).
Side note during discussion: Agfa engineers also want to have IPv6 for internal development.

Technicolor, Carl Wuyts

05-Technicolor.pdf

They develop residential CPE at the Edegem side. Carl is active on v6ops because IETF wants way too many complex things in the CPE. Their CPE is sold by ISP. Focus on packet forwarding and transition techniques. Those CPE provided dual-stack WiFi during the council meeting through a Hurricane Electric tunnel as their own ISP does not support IPv6 yet. Their high end CPE can also do multicast.

Customers are using all transition techniques, using /56 and even /64. Carl does also a lot of customer education and training. Customers (ISP) are waiting to deploy because of the cost. Big issue is not to have IPv6 CPE but the cost by ISP to replace existing CPE. Carl makes an offer to Universities to get a couple of free v6 wiFi CPE for research activities.

Next steps for the IPv6 Council, Prof. Olivier Bonaventure, UCLouvain

06-Next steps.pdf

In other countries, the IPv6 Council is more formal with sponsoring and legal form.
Should we go like NL and align with BIPT and AWT?

We could also start to co-author documents all together under the name of the council?
Gunter will make a list of potential 2 or 3 deliverables to write as a group. Government awareness is probably key as well, we should aim to do like in US. Then we need to find non-technical arguments. Germany and Netherlands have already Govt rules.

Federal Govt is already having a working group and a potential idea would be to make IPv6 as mandatory requirements for public requirements (proposal by the council to use the RIPE 501 document composed notably by some members of the Belgian Council)

Should we do something during World V6 Launch? Press release or more to do? Perhaps as a group effort?

All ISP are now busy with IPv6, it simply costs money and time: Belgacom wants to continue this council as an experience sharing platform. So ISP should not be the only target of this group but rather the enterprise and specially SMB. This could also be a paper for the members to convince the Belgian enterprises. Not only for the value of v6 but also the cost of staying with v4.

Prof Bonaventure would like to see more public pilot trials by ISP. Replies by ISP: it is a highly competitive environment and being the first one will not be an advantage.

Prof Olivier Bonaventure and Gunter Vandevelde announced that they want to pass the co-chair to Eric Vyncke and Carl Wuyts. A board of the Council is also created and Olivier and Gunter join the board as founders and a call for membership (ISP, vendors, public sector, ….) is done: please send an email to Eric.Vyncke@ipv6council.be

Still running IPv4 at 54.163.20.123... | Private area | Site Map | Follow site activity RSS 2.0