Wi-Fi 7 Is the New Floor

On January 21 2026, the Indian government de-licensed 500 MHz of the 6 GHz band for Wi-Fi 6E and Wi-Fi 7 use.

That single notification did something most operational IT teams have not yet adjusted to.

It moved the procurement floor.

The new floor is Wi-Fi 7.

IDC forecasts 120 million Wi-Fi 7 access points ship globally in 2026. That is a 210 percent jump over 2025. ABI Research's 117.9 million figure is consistent.

Wi-Fi 7 becomes the dominant enterprise WLAN standard by 2027.

For the Indian campus refresh buyer signing a 5-year procurement contract this quarter, that timeline matters. A Wi-Fi 6E purchase in mid-2026 may not see out its depreciation curve before the rest of the industry has moved on.

Wi-Fi 7 is not the next refresh.

It is the current one.

But first, some catch-up on infra this week.

The Wi-Fi 7 marketing slide always leads with the speed number.

The operational story is different.

Three Wi-Fi 7 features actually matter to the Indian network architect this year.

Multi-Link Operation (MLO) is the mandatory feature that lets a single client associate with a single AP across 2.4 GHz, 5 GHz, and 6 GHz bands at the same time. Not failover. Not load balancing. Concurrent.

For the warehouse running barcode scanners, the manufacturing line running closed-loop control, or the IT-park hosting hundreds of concurrent video calls, MLO is the feature that makes 802.11be operationally different from a faster 802.11ax. Per the Wireless Broadband Alliance and multiple vendor technical guides, MLO's redundant-path effect keeps latency stable under interference. A device on the manufacturing floor whose 5 GHz path is being stepped on by another radio finds its packets arriving over 6 GHz without renegotiating association.

For the operator, the operational impact: jitter compresses. The 95th-percentile latency stops being the worst metric on the dashboard.

320 MHz channel width is the second one. Wi-Fi 7 doubles the maximum channel from Wi-Fi 6E's 160 MHz to 320 MHz in the 6 GHz band. Up to 4x the raw per-stream throughput. The Indian co-working operator with 400 simultaneous users in a single floor plate and the manufacturing IIoT engineer pushing real-time machine telemetry are the two segments where 320 MHz earns its line in the RFP.

The catch: 320 MHz requires the regulatory 6 GHz unlock to be in force, and the AP-to-client RF environment to support it. India's January 2026 notification covers the first part. The second part is the floor plan.

4K-QAM (4096-QAM) is the third one and the one most often oversold. Wi-Fi 7 moves modulation from Wi-Fi 6's 1024-QAM to 4096-QAM, taking bits-per-symbol from 10 to 12.

The headline reads as "20 percent more throughput." The reality is more conditional. 4K-QAM requires a clean signal. Per Cisco Meraki's Wi-Fi 7 technical guide, it is most effective in short-range, low-interference environments. A user 30 feet from the AP, with line-of-sight, sees the lift. A user behind two walls and a glass partition does not.

The procurement-side translation.

✔ MLO is the feature you should prioritize for industrial and high-density use cases. Test it with two interfering bands during the pilot.

✔ 320 MHz is the feature you should prioritize for IT-park and co-working segments with the floor density to need it.

✔ 4K-QAM is the feature you should NOT base the ROI calculation on. Treat it as the bonus that shows up in best-case conditions.

Vendors will lead with all three. The operator needs to know which two actually move the needle in their environment.

Four vendor stacks dominate the Indian Wi-Fi 7 procurement conversation this year. Each has shipped flagship 802.11be access points. Each is selling a different operational story.

Cisco ships the Catalyst CW9176I and the flagship CW9178I. Per Cisco's CW9176I documentation, the CW9176I is a tri-radio platform with a configurable 2.4 / 5 / 6 GHz layout or a dual-5 GHz plus 6 GHz mode, 18 Gbps aggregate frame rate, a 10 Gbps multi-gig port, and 4x4 MIMO. The architecture includes a dedicated fourth radio for WIDS/WIPS with automated RF optimization, and a fifth integrated IoT radio for Bluetooth scanning and beaconing.

The Cisco management story splits cleanly. On-premises: Catalyst 9800 wireless LAN controllers. Cloud: Meraki dashboard. For an Indian BFSI or government buyer who needs a fully on-prem control plane (DPDP-sensitive deployments, air-gapped facilities), Cisco is one of two vendors who genuinely ship one.

HPE Aruba ships the AP-755 (low-power indoor, LPI class) and the AP-754 (standard power, external antenna, SP class). Both are flagship Wi-Fi 7 SKUs.

The May 8 update reported by The Register matters here. HPE shipped the first Aruba × Juniper Mist collab as self-driving Wi-Fi, using Marvis AI plus the combined dataset across both portfolios. The framing: "without forcing users of either brand to make a jump." Translation: existing Aruba and Mist customers do not need to migrate to a unified platform to access the cross-pollinated AI features. The merger pain is reduced.

The Aruba on-prem control plane is the second one. Aruba Central can run as an on-prem instance or as a managed-cloud service.

Juniper Mist ships the AP47 as the cloud-managed counterpart inside the HPE portfolio.

The Juniper procurement caveat is the one most often missed. Juniper does NOT ship an on-premises wireless control plane in its current portfolio. Mist Edge is a tunnel-termination and RadSec-proxy appliance, not a control plane. The Mist control plane lives in Juniper Mist cloud.

For Indian BFSI, government, or regulated-defense buyers who require on-prem or air-gappable management, Juniper Mist alone is not a fit. The HPE collab partly addresses this by routing such customers toward the Aruba half of the portfolio.

Extreme Networks ships Wi-Fi 7 APs alongside the Agent ONE rollout covered earlier this quarter.

The Extreme management plane is the third one and the most fully air-gappable. ExtremeCloud IQ Controller ships in four hardware SKUs (E1120, E2122-1, E3120-1, E3125). The E3125 flagship supports up to 20,000 APs in an HA pair and adds 100 GbE QSFP28 uplinks. ExtremeCloud IQ Site Engine layers on top as the on-prem advanced management. Controller plus Site Engine equals a complete air-gapped management stack.

For an Indian buyer whose procurement requirement reads "no part of the control plane may live outside the customer's data center," Extreme is currently the cleanest fit.

Air-gappable is the axis.

The four-vendor read-out, in one summary.

👉 Cisco: deepest portfolio, both cloud and on-prem control planes. Most expensive.

👉 HPE Aruba: cleanest path for existing Aruba shops, Marvis AI cross-pollination is real. On-prem available.

👉 Juniper Mist: best cloud-native experience. Not appropriate for air-gapped or fully on-prem mandates without the Aruba pairing.

👉 Extreme: most fully air-gappable. Strong if the procurement contract has hard on-prem requirements.

Wi-Fi 7 in India has a particular shape, because the Indian deployment mix is not the global average.

Indian manufacturing IoT adoption sits at about 15 percent versus a 40 percent global average. The government's Make in India initiative targets 25 percent smart factories by 2027. The gap is real, and the wireless transport layer is a meaningful part of why it is hard to close.

For most Indian factories, brownfield plants and small-and-medium-enterprise sites, LoRaWAN currently fills the long-range low-bandwidth IoT slot. That is the right fit for temperature sensors, vibration monitors, basic predictive-maintenance telemetry. Wi-Fi 7 does not replace LoRaWAN in those use cases.

Three segments earn it.

Wi-Fi 7 earns its place in three specific Indian segments.

Manufacturing-line modernization in greenfield plants. Closed-loop control, AR-guided assembly, machine-vision quality inspection. These need sub-10ms latency with stability. MLO's redundant-band behavior is the feature that turns "good enough average latency" into "stable 95th-percentile latency" under interference. Real-time line control fails on the 95th-percentile, not on the average.

IT-park and co-working dense deployments. A typical Bengaluru, Hyderabad, or Pune IT-park floor plate runs 250 to 400 simultaneous laptop users plus device tethering. The 320 MHz channels in 6 GHz are the airtime relief that 5 GHz floor plans cannot offer. For a developer running large pull requests, simultaneous video standups, and a remote desktop into a sandboxed dev environment, the MLO + 320 MHz combination is the floor-plate refresh that makes the difference.

Smart-city and large-campus surveillance backhaul. Indian smart-city contracts increasingly assume wireless backhaul for the camera and access-control infrastructure rather than dedicated fiber to each pole. Wi-Fi 7's lift in 6 GHz bandwidth is the segment where IP-camera traffic and access-control event telemetry stop competing with user devices for the same airtime.

For the Indian CIO planning a 2026-2027 Wi-Fi refresh, the question is not "Wi-Fi 6E or Wi-Fi 7." The question is "which of these three segments do I have, and which Wi-Fi 7 feature serves each one."

If the answer is none of the three, Wi-Fi 6E is the right floor for now.

If the answer is any one of them, Wi-Fi 7 is the floor for the next refresh cycle.

The January 2026 spectrum unlock is not a single binary "6 GHz is open" event. It comes with regulatory conditions that materially affect the Wi-Fi 7 RFP, and most procurement memos do not yet reflect them.

Three regulatory nuances matter for the Indian buyer.

Power limits split by class. The 6 GHz allocation distinguishes Low Power Indoor (LPI) and Standard Power (SP) device classes. LPI is the default for indoor APs without coordination. SP requires automated frequency coordination (AFC) against the licensed services using the band, which is a non-trivial software dependency. For an Indian outdoor deployment (smart city, manufacturing yard, campus quadrangle), the AP must support AFC and the operator must subscribe to or run an AFC service.

The procurement-side question.

✔ Does the AP you are evaluating support AFC?

✔ Is the AFC service available in India today, or is it on a roadmap?

The Aruba AP-754 (SP class with external antenna) is one example of an AP that explicitly targets the outdoor/SP segment. Most Cisco and Extreme flagships are LPI by default; outdoor variants exist but should be confirmed.

320 MHz channel availability is not unlimited. Even with the full 500 MHz unlocked, the number of clean 320 MHz channels that can co-exist without overlapping is finite. In dense deployments, the network planner has to choose between two 320 MHz channels with maximum throughput-per-stream and three or four 160 MHz channels with better airtime reuse. There is no one right answer; it depends on the floor plate.

Coexistence with existing 6 GHz incumbents. The 6 GHz band in India was previously licensed for satellite, microwave point-to-point, and other services. The de-licensing covers unlicensed Wi-Fi use under specified conditions. For an enterprise with an existing microwave backhaul on the same site (some manufacturing, telco-adjacent, or large-campus deployments do), the coexistence question deserves a survey before procurement.

The regulatory work is finishing. The procurement work is starting.

HPE drops first Juniper × Aruba collab: self-driving Wi-Fi
The Register, 2026-05-08.
The post-acquisition cross-pollination story matters for any Aruba or Mist customer mid-evaluation. The "no forced jump" framing is the buyer-friendly read, but worth pressure-testing against the actual product roadmap.

Wi-Fi Alliance brings Wi-Fi 7 features to 20 MHz-only devices
RCR Wireless.
The backward-compatibility story for the Indian buyer with warehouse scanners, legacy POS, and industrial sensors that will never see a 320 MHz channel. MLO and 4K-QAM are not exclusive to wide-channel clients.

Wireless Broadband Alliance: Road to Wi-Fi 7 reference architecture
WBA, ongoing.
Multi-vendor reference deployments across manufacturing, transport, stadium, university, residential, city, and rural segments. The procurement-side primary source for what has actually been tested across vendor pairs.

Cisco Catalyst CW9176I Wi-Fi 7 Access Point Documentation
Cisco.
For the network engineer doing the actual evaluation work, this is the primary technical reference. Read the radio-mode flexibility (tri-radio versus dual-5-GHz-plus-6-GHz) before the SE's deck reads it for you.

Wi-Fi 7 (802.11be) Technical Guide: Meraki_Technical_Guide)
Cisco Meraki.
The cleanest vendor-written explainer on what MLO, 320 MHz, and 4K-QAM actually do at the protocol level. Pair with Aruba's TechDocs equivalent for a balanced view.

Every wireless refresh cycle in the last fifteen years has been sold as a speed upgrade.

The Wi-Fi 4 to 5 pitch was "faster." The Wi-Fi 5 to 6 pitch was "faster and more clients per AP." The Wi-Fi 6 to 6E pitch was "faster, more clients, and a clean 6 GHz band."

Wi-Fi 7's pitch is sold the same way, and that framing is going to cost most Indian buyers the actual benefit.

MLO earns the spend.

Speed is the easy headline. The real value is in the bands working together rather than competing. For the operator running a manufacturing line whose 5 GHz band is being stepped on by a neighbor's industrial radio, MLO's behavior is the difference between a sub-10ms control loop that holds and one that drops a packet every few seconds. For the IT-park floor plate where 250 laptops fight for 5 GHz airtime at 11am, MLO is the feature that lets the AP move some of those flows to 6 GHz without renegotiating the association.

That benefit does not show up in a Mbps number. It shows up in the 95th-percentile latency graph and in the variance of the jitter measurement.

Most vendor decks do not have that slide.

The Indian buyer's procurement framework for 2026-2027 needs to flip what it asks the SE.

The wrong question is "what is the maximum throughput per stream?" The right question is "show me the MLO behavior under simulated band interference, the 95th-percentile latency under realistic floor density, and the AFC behavior in the regulatory environment my outdoor APs will live in."

Cisco, HPE Aruba+Juniper, and Extreme all have answers to that question. The vendors who lead with the speed slide are the ones whose answers are weakest.

For the buyer holding the RFP this quarter, the procurement-side advantage is real but narrow. The Indian regulatory unlock is six months old. The vendor lineup is freshly shipping. The pricing has not yet settled into multi-year discounts. The window for the disciplined buyer to negotiate a strong contract is open now and closes when Wi-Fi 7 becomes the default refresh rather than the upgrade.

VEMIO™ exists because the operational benefit of MLO, of 320 MHz, of 4K-QAM, only shows up if the operator can see it. The maximum-throughput-per-stream number lives in the vendor's marketing collateral. The 95th-percentile-latency-under-interference number lives in the customer's telemetry layer. We instrument the customer side so the RFP claims that the vendor made on the way in still hold true twelve months after deployment.

The refresh decision is not what the vendor is selling. It is what the operator can measure.

Reply to this email with the one Wi-Fi metric you currently cannot measure across your campus, and we will feature the most operationally interesting reply (anonymised, with consent) next issue.

Until next time,

Ajay Salvi & the Vinay Enterprises team.