CAnet 4 IPv 6 update APAN IPv 6

  • Slides: 8
Download presentation
CA*net 4 IPv 6 update APAN IPv 6 Task. Force meeting rene. hatem@canarie. ca

CA*net 4 IPv 6 update APAN IPv 6 Task. Force meeting rene. [email protected] ca Bill. st. [email protected] ca http: //www. canarie. ca/canet 4/

CA*net 4 Network New 72 channel ROADM 5 x 10 Gbps

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

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 IPv 6 – All other networks only carry IPv 4

CA*net 4 IP network

CA*net 4 IP network

native IPv 6 peerings > 70% of domestic research nets (ORANs): > international: 6

native IPv 6 peerings > 70% of domestic research nets (ORANs): > international: 6 TAP, AARnet, Abilene, ASnet, GEANT, GLORIAD, KREONet 2, NYSERnet, WISCnet > CANARIE prefix 2001: 410: : /32 > commercial prefixes are also accepted (until such time as Cdn ISPs start offering IPv 6 services)

IPv 6 applications > Juniper routers recently upgraded to Junos 7. 2 R 2.

IPv 6 applications > Juniper routers recently upgraded to Junos 7. 2 R 2. 4 > supports SSM, and ASM with embedded RP > presently rolling out IPv 6 multicast in backbone > next steps wil be to establish native IPv 6 multicast peerings > NRC IPv 6 news server > CRC participated in the distributed Isabel workshop over IPv 6, held in Madrid > CRC planning to participate in NGN workshop in late September/early October via IPv 6 multicast

What comes after IPv 6? > IPv 6 still struggling to get wide adoption

What comes after IPv 6? > IPv 6 still struggling to get wide adoption > New architectures such as GENI and FIND exploring alternatives to IPv 4/IPv 6 addressing > One possible alternative is XML or URI routing at the edge with IPv 6/IPv 4 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-network. X > Router FIBs map URIs to IPv 4/IPv 6 addresses – Challenge is that routing tables will be huge – Alphanumeric lookups much harder than fixed IPv 6 address

Recommended Reading Written by CANARIE funded Researcher – Marc Blanchet http: //www. ipv 6

Recommended Reading Written by CANARIE funded Researcher – Marc Blanchet http: //www. ipv 6 book. ca