I love the michigan technology standards. They are a great place to start when talking about how to make technology work for your company. I was surprised at how many companies were focused on the technical aspects of the standards, but as the article says, the standards are about more than just technical standards.
While the Michigan standards are meant for things like making software that automatically turns a light on when someone steps into a room, the standard in general is about how to make technology work for your company. For example, at the center of the standards is a process that automates a process that would be easy to set up, but which can be hard to figure out because of all the moving parts.
This is one of the things I find most frustrating about the Michigan standards.
The Michigan standards are a part of a larger set of technical standards called the “Cisco Global Technology Networking Standard,” or GTN for short. GTN is a set of standards that the Cisco company uses to govern the design of their networking equipment and their processes for testing its compatibility with other equipment. The GTN, which is the parent of the Michigan standards, was first published in 2005 and continues to be updated.
The Michigan standards are actually a set of requirements based on the IEEE 802.1aq standards, which is the same standards that the Michigan standards are based on. The IEEE 802.1aq standards are a set of standards that describe how to construct an Ethernet network. And the Michigan standards are basically what it says on the box.
As it turns out, the Michigan standards aren’t quite what it is being advertised to be. In fact, they’re a mishmash of the IEEE 802.1aq standards and the IEEE 802.11e standards. This is because the IEEE 802.11e standards are for wireless networks and the Michigan standards are for wired networks. So what you get is a set of requirements based on the IEEE 802.1aq standards but not the IEEE 802.11e standards.
Basically, the way the IEEE 802.1aq standards are designed, it is pretty much impossible to have an Ethernet network connect to an 802.11e standard compliant network. You can have a wired connection and a wireless connection, but not a wireless connection with an Ethernet connection. Also, the 802.11e standards are designed for use with Ethernet hubs, not Ethernet switches. So the only way to connect to an 802.11e network is to use a wired Ethernet switch.
For a long period of time, the IEEE has promoted the standards as the standard for how Ethernet networks should be laid out, so I think it is safe to say that the standards are obsolete. The reason for this is because the 802.11e standards were designed for use with Ethernet switches, and not with Ethernet hubs.
And I think that is the last time we should talk about it.
Ethernet hubs are a necessity for building a decent, stable, and reliable LAN system, so the standard should go away. I’m glad they’re going away, because wireless LANs (which use the same IEEE standard) are incredibly powerful, but they will never replace wired LANs. Also, if you have a wired LAN, you can’t use wireless, so the standard should go away.