Frequently Asked Questions (FAQ)

Answer: IPv6's 128-bit addressing allows any ISPs to immediately satisfy their current demands (while at the same time preparing for future needs) in terms of the volume of users that require Internet connection. Likewise, it allows simplifying the ISP's network, as it does not require intensive NAT usage (as in the case of IPv4) and therefore all the infrastructure can operate transparently from end to end. Early IPv6 deployment allows providers to handle traffic generated by the IPv6 transition mechanisms included in several of the most popular operating systems, with the greatest possible efficiency.

In terms of competitiveness, those ISPs that implement IPv6 will be able to satisfy their customers' demand for this type of connectivity (both at this moment and in the future). Likewise, in obtaining experience and gaining a reputation in the area, they will be able to assimilate other market sectors that may originate from other providers and provide connectivity to other emerging sectors. Consequently, they will be able to participate in the deployment of new applications and services that may arise as a result of the massive use of IPv6 related technologies such as 3G from the outset, all of which will allow them to promote new business opportunities.

Answer: Multiple strategies may be adopted to minimize the cost of transitioning from IPv4 networks to IPv6 networks. In particular, upgrading an ISPs infrastructure may not represent a major problem for them as for different reasons they are constantly upgrading their equipment to use operating system versions having more features. This means that IPv6 capability is probably already installed in their core equipment and must gradually be transferred towards other parts of the network, all of which can be done within the same equipment upgrade plan. Therefore, these costs are not directly attributed to IPv6 implementation.

The key is to invest a certain amount of money gradually (taking advantage of network natural renewal cycles, expansions, etc.) throughout the entire duration of a well designed and orderly transition. If the process is undertaken gradually, it may be economically acceptable for most ISPs (all that is needed is to include IPv6 as a required technology in their development plans).

Today, together with equipment manufacturers, ISPs have a leading role to play in the adoption of IPv6. For this reason, ISPs should demand that manufacturers provide IPv6 support so that this technology will become a market standard.

As to training costs, it is impossible to eliminate them: the scenario is similar to that of any new emerging technology. However, these costs will vary according to the size and complexity of the network where the new protocol is being implemented.

Answer: In the case of access, interconnection or transport costs for ISPs, IXPs, carriers or major providers, these costs are not very high as compared to those that exist in connection with IPv4 if the natural process of equipment replacement and software upgrade are followed, something that surely all these organizations have included as part of their normal management and operation processes. In certain cases these may vary somewhat depending on whether or not their support contracts cover operating system upgrades, and also on how new or how old their equipment is in terms of hardware.

On the other hand, there is one market which perhaps deserves a special note: the residential market or what is known as the "last mile" (which in many cases also includes aggregation equipment, but with special emphasis on "end user" equipment). In this final sector we find that there is currently a clear lack of equipment having IPv6 support. This is particularly true about residential routers, as barely a few brands have already implemented IPv6 support or some of the transition technologies and in many cases it is necessary to use third-party operating system versions which are not supported by the manufacturers themselves. There is even equipment that operating exclusively at layer 2 (bridges, ADSL modems, etc.) presents problems when using IPv6-related protocols such as auto-configuration, etc. All of this might require purchasing equipment with more features than would be necessary for this type of domestic applications and consequently higher costs.

Equipment costs vary from country to country depending on local technology providers. Pricing information can be found by checking the websites of the region's major providers or through direct inquiries to equipment providers.

Answer: If IPv6 is not taken into consideration when planning current investments, it is possible that a bad investment will be made: what is not anticipated now will represent additional expenses in the future.

Not all network equipment brands include the new features, and those that do are generally more expensive.

If the right decisions are not made at this time, we will face a problem when attempting to implement IPv6 as a service, because at that time we will be forced to renew the software on all the pieces of equipment that are part of our network but do not support the protocol. This will surely involve greater costs than a gradual transition that begins today.

For these very same reasons, we may be compromising the technological progress of our companies or institutions, missing out on the chance to provide or receive a new set of IPv6-based services.

Applications will be discussed in a special section.

Answer: We believe that the answer is yes, but that it is also necessary for this process be accompanied by promotional material that shows the advantages that the applications and products can currently offer ISPs, which will result in future benefits for end users. End users are not necessarily interested in knowing how this technology works. Instead, their main interest would be how effective the technology is for the purposes it is used and, above all, what value added services are provided.

ISP or carriers will make an effort to connect last mile users as long as there is money to be made or, in other words, as long as there is a reason to change something and investments can be recovered in due time. IPv6 can contribute to all this, helping ISP/carriers manage their equipment and providing an adequate environment for the development of new services (examples of this include that of the cable operator Comcast that utilizes IPv6 to manage their equipment and the SCOOP service of NTT in Japan).

Answer: It is not possible to estimate the level of investment from a generic point of view, as this will depend on several factors such as:

• application architecture
• technologies used by the application
• source code quality
• staff training
• operating systems
• network architecture

However, it will be possible to estimate the necessary investment on a case-by-case basis considering all relevant factors. A general recommendation is that it is convenient to consider the participation of a multidisciplinary team. Programming knowledge is not the only element involved; it is also necessary to consider issues relating to IP technology, operating systems, etc.

Answer: In principle, any application (regardless of its complexity, technology, functionality and scope) that uses the IP protocol to communicate within a network could require updating and therefore should be the object of a review and analysis process. Likewise, every application that stores, manages or uses IP addresses for any reason other than communication (e.g. logs, network simulators, simulators of processes that are executed over IP networks, applications that generate and/or process traces containing IP addresses, DNS tools, among others) must be considered.

Those applications that will soon cease to be in service either because they will reach the end of their life cycle or because of their technological obsolescence can be excluded from the analysis.

Answer:Yes, there are tools that can help us update applications so that they work over IPv6. However, it is important to note that these tools do not update applications directly, but rather help identify lines of code (data structures, functions) that need to be updated in order for the applications to work over IPv6 or, better yet, in order for them to work over both versions of the Internet Protocol. The "Software Update" section of this portal contains a general list of applications and/or documents that may serve as a reference when updating software to achieve IPv6 support.

Answer: Considering that most IPv6 networks and implementations are at a stage of coexistence of both versions of the protocol, for an important percentage of implementations and applications it is recommended that if access to the source code is available this code should be modified (structures, functions, etc.) so that they are independent of the protocol version. Otherwise, in order to be able to provide the service to users with both IP versions, a translation mechanism needs to be implemented. Depending on each specific scenario, this translation mechanism may be required from the network layer to the application layer, and is not as recommendable as the first option described above.

In addition, when developing new applications we must consider the advantages of IPv6. For example, computers will not be the only devices capable of having a public IP address: a broad variety of devices will also be able to have this type of addresses (among them refrigerators, air conditioners, lighting units, etc.). NAT might be eliminated and consequently applications would be able to communicate among themselves directly from end to end (or from application to application), overcoming the limitations currently associated with the use of private addresses and NAT.

IPv6 allows implementing IP address mobility in a much easier way, and this represents and additional benefit. Applications can take advantage of auto-configuration mechanisms to access or contact other devices.

As to developers, in order for them to be able to exploit the advantages of IPv6 they need to be aware of the characteristics of the protocol, which is why training in the new version of the protocol and its differences regarding IPv6 is essential, as is knowing the changes needed for application portability.

In short, in order to develop applications that benefit from the advantages of IPv6, these must be designed (or conveniently modified) with IPv6 in mind. In other words, the application must be designed so that it can efficiently use the IPv6 features (auto-configuration, mobility, IPSec, etc.) required to fulfill the purpose for which the application was developed without losing IPv4 network compatibility (if necessary) and, wherever possible, making the application independent of layer 3 protocols.

Respuesta: Yes, the Ministries of Communications or other government organizations involved in the promotion and/or adoption of network technologies can and should promote the use of IPv6 among other technologies and/or services that will allow the development of the countries and of the region in general, thus contributing to reduce what is known as the digital divide. This can be done by promoting IPv6 adoption at public administration level and within the ISP infrastructure under state administration, helping the other ISPs implement IPv6, conducting training and promotion activities, encouraging the use of IPv6 in new technological projects, financing IPv6-related research and development projects, and promoting the adoption of the protocol within the country's Research and Education networks, among other possibilities.

Respuesta: Yes, some governments have implemented this type of actions. Examples of this include:

South Korea - The Road to $20,000 GDP/capita: IT 839 Strategy (later renamed u-IT839 Strategy) (http://www.ipc.go.kr/servlet/download?pt=/ipceng/policy&fn=it839_eng.pdf) {Ministry of Information and Communication, 2004}

USA - Transition Planning for Internet Protocolversion 6 (IPv6) (http://www.whitehouse.gov/OMB/memoranda/fy2005/m05-22.pdf {United States Office of Management and Budget, 2005}

Japan - uJapan (http://www.soumu.go.jp/menu_seisaku/ict/u-japan_en/new_outline01.html {Ministry of Internal Affairs and Communications, 2006}

India - Transition from IPv4 to IPv6 in India (http://www.trai.gov.in/trai/upload/Recommendations/3/recom9jan06.pdf) {Telecom Regulatory Authority of India, 2006}

Malaysia - MyICMS 886 Strategy (http://www.my6.net.my/my6/MyICMS_2ndEdition.pdf) {Ministry of Energy, Water and Communications, 2006}

Australia - A Strategy for the Transition to IPv6 for Australian Government agencies 'Building Capacity for Future Innovation' (http://www.finance.gov.au%2Fe-government%2Finfrastructure%2Fdocs%2FEndorsed_Strategy_for_the_Transition_to_IPv6_for_Australian_Government_agencies.pdf) {Australian Department of Finance and Deregulation, 2007}

Cuba - Resolution 140/2008: Requirements for importing and exporting IPv6-compatible products and technologies http://www.6ip.cu/documentos-cuba/R140-08.pdf and resolution 156/2008: Methodology for introducing the IPv6 protocol in the country. http://www.6ip.cu/documentos-cuba/R156-08.pdf {Ministry of Information and Communications, 2008}

For more information, please visit: http://portalipv6.lacnic.net/en/ipv6/ipv6/government