All the pieces in this picture have a different timeline on their path to enabling IPv6 and the Internet service provider is typically responsible for ensuring the access and aggregation/core are ready to handle IPv6 traffic. Content providers on the right needs to ensure that their business continues as usual or accessibility for both IPv4 and IPv6 end-users End-users depended on the equipment readiness such as their CPE connecting to the access piece. The device that the end-users use also play a part in which the OS, browser or application must support IPv6 Important to pay attention on the readiness from the customers end-point to the content out there on the internet. If any piece in this diagram here is not able to handle IPv6 traffic, the users cannot reach IPv6 content. 07/26/13
Peering upstream refers to International peering/transit and not among ISP players in Singapore 07/26/13
07/26/13
07/26/13
07/26/13
Microsoft spends 7.5 million to purchase 600k+ IPv4 addresses, each costing S$11.25. If the same price per address were to be used in IPv6, it would probably cost Microsoft an earth’s weight of gold to buy a /64 prefix 07/26/13
07/26/13
07/26/13
07/26/13
We are not promoting that service provider or any enterprises should use 6rd. We are neutral on the use of any transition mechanism and it is up to the enterprise to evaluate on a case-by-case basis. We believe that other transition mechanisms will also generally provide cost savings IDC interviewed a particular tier1 ISP in US and capture the following findings by comparing 2 methods CGN and CGN + 6RD 07/26/13
07/26/13
Cloud computing allows dynamic, on-demand, and elastic generation of both virtual infrastructure, and virtual machines running over the infrastructure. Whether physical, or virtual, each machine or application still requires an IP address. Add all the new mobile phones, VoIP phones, intelligent GRIDs (imagine every electrical device in your home being Internet-enabled), and anything else that can be electronically tagged, you can see why we need to consider the relationship of clouds and IPv6 as a high priority for the cloud computing industry. The trick is to make implementation of IPv6 easy not only for the end users – it should be near transparent, but also for network administrators and applications developers. End users don’t want to know, or need to know the complexities of network and device addressing. They just want their device to work over the Internet. Administrators need to know this is not a punitive or limiting requirement, but rather a improvement enabling more rapid development of new applications and network architectures. And of course offer better than existing network and data security. Future applications and services within clouds will require a much broader use of Internet-enabled resources. Whether it is automatically spooling additional servers, adding disk, or more complex functions such as global distributed processing, load-balancing, disaster recovery, and follow-the-sun dynamic resource allocations – IPv6 implementation is required to meet that demand. Cloud computing as a concept supports all such processing models, and IPv6 will extend the ability of the global Internet to support the concepts and vision. Perhaps the most intimidating requirement facing network administrators is the requirement to “restack” their entire infrastructure as an IPv6 network, while still supporting legacy IPv4 within their architecture. The goal of all cloud providers is to insulate application administrators from the complexity of understanding IPv6, thus further encouraging aggressive adoption of IPv6 addressing. If the administrator is relieved to concentrate efforts on designing the application, scaling compute, network, and storage for his market or users, then the cloud service providers have done their job. And that job is ensuring the Internet continues to serve the needs of a global connected community. Resilience – Making probing more difficult due to vastness of address space. Simplified headers and lack of packet fragmentation allow routers to process easier and more robustly 07/26/13
BMW i-Drive, Renault-Cisco Collaboration Research 07/26/13
Geoff Huston, Chief Scientist of APNIC and Alex Zinin, CTO of Cisco will be our keynote speakers - Other prestigious speakers like Alex Caro, CTO of Akamai, Chip, CEO of Nephos6, Richard Hyatt, CTO of Bluecat Networks and many other representations from organisations like Yahoo!, Arbor Networks and Huawei will be there to speak. 07/26/13