becarpenter-book6/5. Deployment/Deployment in the enterprise.md

## Deployment in the enterprise

Measuring the adoption of IPv6 in the enterprise domain is not straightfoward.
Since it is hard to look at it from the network "inside", one of the few currently avaialble approaches 
is to check the IPv6 readiness from outside the enterprise's network.
[https://fedv6-deployment.antd.nist.gov/cgi-bin/generate-com] provides a method to infer whether 
US enterprises support IPv6 by checking its external services, such as the availability of 
Domain Name System (DNS) AAAA records, of an IPv6-based mail service and of the support of IPv6 on
their website. The same method can be applied to Chinese [http://218.2.231.237:5001/cgi-bin/generate] and
Indian [https://cnlabs.in/IPv6_Mon/generate_industry.html] enterprises.

DNS has a good support in all cases: more than 50% of the enterprises in the three economies considered have AAAA records,
a sign that IPv6 support is generally available. The same cannot be said or the other services that have much lower adoption.
[https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-deployment/] provides other statistics about more specific industry domains.

What are the factors hindering the adoption of IPv6 in the enterprise?
Appendix B of [https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6-deployment/] reports the result of 
a poll issued by the Industry Network Technology Council (INTC) [https://industrynetcouncil.org/] to check the need for IPv6 training 
by some medium and large US enterprises.
   
The poll shows that lack of IPv6 knowledge is one of the main issues.
This reflects into the need for training, in particular in the areas of IPv6 security and
IPv6 troubleshooting. Apart from training, enterprises feel that IPv6 security is of operational concern as well as the 
conversion of the applications they use in their daily activity to IPv6.

<!-- Link lines generated automatically; do not delete -->
### [<ins>Previous</ins>](Deployment%20in%20the%20home.md) [<ins>Chapter Contents</ins>](5.%20Deployment.md)