Back to Basics: Internet, next version, IPv6
Industry shouldn’t panic about the next version of the Internet Protocol, version 6 (IPv6), the transition from IPv4, or the recent exhaustion of the IPv4 address pool. Take advantage of opportunities, while you can.
Although Internet Protocol Version 4 (IPv4) addresses “ran out” in February, manufacturers and other users shouldn’t worry about the transition to the next version, IPv6, experts explained. In fact, the adoption of IPv6 by industrial automation vendors seems likely to create new opportunities for end users as IPv6 migrates into automation applications.
The last five blocks of addresses were assigned Feb. 3, 2011, according to Brian Batke, chair, ODVA EtherNet/IP Systems Architecture SIG (also principal engineer at ODVA member Rockwell Automation), and Paul Brooks, participant in ODVA activities including its strategic market planning task force (also manager of business development for ODVA member Rockwell Automation). Batke and Brooks were among speakers at the ODVA 2011 Industry Conference, in March, in Litchfield Park, Arizona.
- There’s no ignoring IPv6; architecture requirements must be considered with any new communications infrastructure installation.
- With the expanding Internet of Things (IOT), giving network connections to mobile and stationary devices and systems in manufacturing, buildings, and enterprise, IPv6 was needed to support trillions of IP addresses.
- Regional registries of assigned addresses are expected to be completed by 2012.
- To support and help promote transition to IPv6, the U.S. government has mandated IPv6 use by end of 2011, including support on all U.S. government public servers.
- No EtherNet/IP device is “USGv6-1.0-capable” yet, (and there are other Ethernet infrastructure devices that do support IPv6 used within EtherNet/IP systems).
- Much of the IPv6 discussion sounds like Y2K, which resulted in panic spending, which in turn, arguably was enough to prevent the many predicted catastrophes.
- Network address translation takes the form of 192.168.1.x<>10.10.y.y<>Internet (an example of Local<>Private<>Public NAT (national address translation) common in manufacturing applications).
- IPv6 Internet is available to IPv4 clients through these NAT techniques.
- Most manufacturers and large facilities use just a few public addresses externally.
- IPv4 and IPv6 can coexist on the Internet and intranets.
- Microsoft Windows XP doesn’t support IPv6, though there is mapping technology to allow home nodes to continue to access the Internet.
- New U.S. government servers must have an IPv6 address.
- An IPv6 client can interface to an IPv4 server; connecting an IPv4 client and IPv6 server is complex to support.
- Mechanisms now available will support a slow and smooth migration.
- New applications, such as the smart grid, and new devices, such as 4G mobile telephony, have IPv6 addresses.
- New SCADA applications will need to be IPv6; hybrid applications at outstations likely would be too costly.
- On device level rings, PC clients eventually will use IPv6 information.
- On dual stack devices, IPv6 will be used going up, and IPv4 going down in the short term.
- In IPv6, security is mandatory, not optional.
- New vendors adopting IPv6 architectures will initially have a competitive advantage over IPv4 laggards.
- Device provisioning can be improved with IPv6.
- Mark T. Hoske, Content Manager, Control Engineering, www.controleng.com
Editor’s note: What happened to IPv5? According to several sources, Internet Stream protocol, never adopted as a standard, was referred to by some as IPv5, so the next-generation Internet Protocol adopted the IPv6 name.
Also see: Industrial Ethernet: Room for more, IPv6.
For more from ODVA, see: “IPv6 for EtherNet/IP: Is the Sky Falling, or Just an Acorn?” an ODVA technical paper by Brian Batke and Paul Brooks
See other ODVA news links, below, for more from Control Engineering on:
- Think Again: Improving networking and energy use
- Bosch Rexroth commits to ODVA, EtherNet/IP advancements
- 10 tips for deploying EtherNet/IP, the ODVA Ethernet protocol
- ODVA collaborates to manage industrial energy data
- ODVA forms rail transport special interest group
Case Study Database
Get more exposure for your case study by uploading it to the Plant Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.
Annual Salary Survey
In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.
Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.