D2.2.4: Final IPv4 to IPv6 Transition Cookbook for ... - 6NET

IST-2001-32603Deliverable D 2.2.4handling IPv6 traffic at line rate. By implementing 6PE in the core of the network it was ensuredthat IPv6 traffic was also handled at line rate in the core and potential bottlenecks were removed.The routing set-up as implemented and running today runs without problems. A number of featuresare on SURFnet’s requirements list, of which IPv6 multicast is high on the list. SURFnet alreadyhas hands-on experience with IPv6 multicast in the 6NET context using external MBGP for IPv6.4.1.3. Customer connectionsToday, the vast majority of SURFnet’s customer connections are at 1 Gbit/s using Ethernettechnology. Three customers are connected at 10GE, connected to line cards in the backbone thatdo not support IPv6 at wire speed. In SURFnet6, the number of connected organizations using10GE is expected to rapidly increase. Wire speed 10 Gbit/s IPv6 will be one of the featuresimplemented in SURFnet6.SURFnet5 supports customer connections on IPv4 as well as IPv6. For IPv4 unicast and multicastare supported, while for IPv6 this is currently unicast only. IPv6 can be delivered towardsSURFnet’s 180 customers in the field of research and higher education using either a native ortunnelled approach.Native IPv6 connections are implemented either “dual stack” or “on a dedicated port”. Dual stackimplies that the customer connection runs IPv4 as well as IPv6 on the same local loop. A fewcustomers, however, prefer IPv6 on a dedicated port, next to their IPv4 port for the simple reasonthat they have a dedicated router for IPv6 on their LAN.Tunnelled connections to customers are only allowed in case the customer is not able to implementIPv6 in dual stack mode or on a dedicated port. In case we implement a tunnel connection with acustomer, we always ask the customer to make plans for going native.4.1.4. Addressing planSURFnet received an official IPv6 prefix from the RIPE NCC in August 1999 of length /35, whichwas enlarged to a /32 during the summer of 2002:2001:0610::/32 6This prefix is split up as follows:3 bits | 13 bits | 16 bits | 3 bits | 5 bits | 8 bits |-------+-------------+--------------+--------+--------+--------+FP | TLA | sub-TLA | slow | PoP | site || | | start | (NLA 1)| (NLA 2)|/3 /16 /29 /35 /40 /48Only the first /35 is currently used. The other 7 /35s are for future use right now. For each PoP a/40 prefix (NLA 1) is reserved and each /40 is again split into 256 /48 prefixes (NLA 2) to numberthe backbone links and customer networks. The break-down of SURFnet’s prefix on a per-PoPbasis is shown in detail below.The prefix 2001:0610::/40 is in use as the carrier network for SURFnet5, in which all links reside.For the links SURFnet uses /64 prefixes, in the format:6 For registration details on this prefix, see: http://www.ripe.net/cgi-bin/whois?2001:0610::/32.29