|
Governments, enterprises, ISPs, etc., use a wide variation of arguments for not deploying IPv6 in their ICT environment. Some of these arguments are purely technological in nature, whilst others deal with business or the availability of products. Also, some of the arguments are based on reality, and others are “just” perceived by people but may be based on, for example, misunderstanding of IPv6 technology.
In this section IPv6 Bottlenecks: facts or fiction, we list the arguments we have heard most often, and to each we added a small paragraph with some background information. Please feel free to comment on the validity of these arguments and the background information we provided.
|
|
21. "There is no demand/supply for IPv6 enabled devices and software" |
|
"There is no demand for IPv6 enabled devices and software, so I don’t need to offer these products on the short term."
This argument indicates the main reasons for vendors not to deliver IPv6 capable products. In fact, both stakeholders (network owners versus vendors) are both waiting for each other to act. The ISP waits for the vendor to offer IPv6-enabled products, while the vendor waits for demand in the market. |
|
22. "The market of IPv6-capable products is not transparent" |
|
"The market of IPv6-capable products is not transparent, so I don’t know which products will work in my situation without experimenting with them."
Many enterprises do not have the time, money or knowledge to decide by extensive experimentations how to migrate towards IPv6 and which products they should buy for this. A lack of easily available transparent information about new products increases the risk of failure of a migration towards IPv6. The market should be (self-)regulated such that it provides the necessary information, in the correct way. |
|
|
|
Bottlenecks