An IEEE number tells you which networking rules a product uses. To decide whether two devices will work together, connect that number to a specific port, medium, feature, and configuration.
Start with the job the standard does
The IEEE 802 LAN/MAN Standards Committee develops standards for local, metropolitan, and other area networks. Its work concentrates on physical links and data-link behavior: sending signals, formatting frames, sharing a medium, and bridging networks. IP supplies internetwork addressing and routing above these links.
| Family or standard | Main subject | A useful product question |
|---|---|---|
| 802.3 | Ethernet MAC and physical interfaces, including specified forms of Power over Ethernet | Which speed, medium, reach, and power capabilities does this particular port support? |
| 802.11 | Wireless LAN MAC and radio operation | Which bands, channel widths, spatial streams, and optional features do both ends support? |
| 802.1Q | Bridges and bridged networks, including VLAN behavior | How are VLAN membership, tagging, and forwarding configured? |
| 802.1X | Port-based network access control | Can the endpoint, access device, and authentication service perform the required exchange? |
| 802.1AE | MAC security, commonly called MACsec | Where does link protection begin and end, and how are keys managed? |
| 802.15 | Wireless specialty networks | Which specific technology and device ecosystem is involved? |
Use the working groups' own descriptions when narrowing a requirement: 802.3 Ethernet, 802.11 wireless LANs, and 802.1Q bridges and bridged networks. The word “higher” in 802.1's higher-layer LAN work is relative to other LAN functions; it does not make VLANs application-layer protocols.
Read a fictional access-point specification
| Listing detail | What it helps establish | What to check next |
|---|---|---|
| 802.11ax; dual band; 2 × 2 | A wireless technology and radio capability claim | Read the stated frequency bands and per-band capabilities. Compare actual clients, regulatory region, channel plan, and security mode. |
| 1000BASE-T uplink | A copper Gigabit Ethernet connection | Check the switch port, cabling, negotiated link speed, and errors. Wireless headline rates and application throughput measure different things. |
| 802.3at powered device | The access point expects a specified PoE arrangement | Confirm the switch or injector's supported power type, available port power, and total budget. Check for reduced-function modes. |
| 802.1Q | VLAN-related capability | Match management and client VLANs to the switch's tagged and untagged behavior. Record the actual VLAN IDs. |
| 802.1X | Participation in port-based access control | Check supported EAP methods, identity/certificate requirements, and authentication-service integration. |
The practical result is a deployment record: which port supplies power, which VLAN carries management, which VLAN serves each network name, which clients are supported, and how authentication is verified. A standards list becomes useful when it produces these concrete answers.
802.1X and 802.1AE address different security functions. Access control, link encryption, and application encryption each need their own scope. Record which boundary a protection actually covers.
Check the entire connection
- 1. Match the physical interfaceIdentify copper or fiber, connector, Ethernet variant, optical wavelength where relevant, supported reach, and cable or fiber type. A matching connector alone leaves several of these questions open.
- 2. Match the feature at both endsVerify device model, hardware revision, software release, licensing, and the exact port involved. Support elsewhere in a product family is insufficient evidence for the installed unit.
- 3. Match the configurationRecord speed negotiation, VLAN membership, authentication, power, and any required link aggregation or timing settings.
- 4. Validate the intended taskCheck link state and error counters, obtain the expected network configuration, authenticate, and run a representative application. Keep the observed result alongside the requirement.
For a fiber link, use the manufacturers' supported-transceiver and cabling documentation for the exact equipment. For a wireless link, test the actual clients in the intended locations. A successful association establishes one stage of the connection; sustained application performance depends on the rest of the path.
Read revisions and certification claims carefully
A family number identifies a body of work; an amendment adds or changes particular features; a revision can incorporate earlier amendments. Older amendment names can remain in product literature after their work is incorporated into a newer base standard. Use the official working-group and published-standard pages to establish status.
Wi-Fi branding and certification provide a different layer of information from an IEEE specification. Inspect the particular product's certification and feature listing when that matters to compatibility. Keep mandatory requirements separate from optional capabilities and manufacturer extensions.
Time-Sensitive Networking likewise describes a set of related mechanisms and profiles. For an application with a latency or synchronization requirement, identify the actual mechanisms, supported profile, clocking assumptions, and validation method. The IEEE 802.1 TSN overview provides a route into that work.
Choose your next guide
- Follow a connection through the OSI model to connect local-link behavior with routing and applications.
- PPP and PPPoE explains the additional subscriber-session stages some broadband links use.
- FDDI and network resilience shows why physical path independence matters.