80 likes | 93 Views
This update provides details about the latest developments in the CA*net.4 IPv6 network, including its structure, the parallel networks it encompasses, and its role as a general-purpose IPv6 network. It also highlights the recent upgrades to Juniper routers and participation in IPv6 workshops and discusses potential alternatives to IPv4/IPv6 addressing. Recommended reading includes a book by CANARIE-funded researcher Marc Blanchet.
E N D
CA*net 4 IPv6 update APAN IPv6 TaskForce meeting rene.hatem@canarie.ca Bill.st.arnaud@canarie.ca http://www.canarie.ca/canet4/
CA*net 4 Network New 72 channel ROADM 5 x 10 Gbps
Network details • CA*net 4 is NOT a single homogenous network • CA*net 4 is made up of many parallel networks dedicated to different communities and applications • High energy physics network • Network for government research labs • Network for distributed computer backplane • Etc • One of the parallel networks is a general purpose IP network • This is the only network that carries IPv6 • All other networks only carry IPv4
70% of domestic research nets (ORANs): • international: 6TAP, AARnet, Abilene, ASnet, GEANT, GLORIAD, KREONet2, NYSERnet, WISCnet • CANARIE prefix 2001:410::/32 • commercial prefixes are also accepted (until such time as Cdn ISPs start offering IPv6 services) native IPv6 peerings
IPv6 applications • Juniper routers recently upgraded to Junos 7.2R2.4 • supports SSM, and ASM with embedded RP • presently rolling out IPv6 multicast in backbone • next steps wil be to establish native IPv6 multicast peerings • NRC IPv6 news server • CRC participated in the distributed Isabel workshop over IPv6, held in Madrid • CRC planning to participate in NGN workshop in late September/early October via IPv6 multicast
What comes after IPv6? • IPv6 still struggling to get wide adoption • New architectures such as GENI and FIND exploring alternatives to IPv4/IPv6 addressing • One possible alternative is XML or URI routing at the edge with IPv6/IPv4 in the core • Allows separation of “locations” from routing information • With URI, all physical interfaces and devices at the edge are given addresses such as: • Htttp://interface-port-0;or • http://my-computer-on-networkX • Router FIBs map URIs to IPv4/IPv6 addresses • Challenge is that routing tables will be huge • Alphanumeric lookups much harder than fixed IPv6 address
Recommended Reading Written by CANARIE funded Researcher – Marc Blanchet http://www.ipv6book.ca