Summary

  • India’s January 2026 rule exempted compliant low-power indoor and very-low-power outdoor systems in 5925–6425 MHz from individual licensing or frequency assignment. At APNIC 62 in Mumbai, however, the conference network report said 6 GHz was not visible to most clients, its capacity went unused and most devices could not associate. That is an implementation result, not evidence that the rule itself failed.
  • A usable 6 GHz session crosses several independent gates: equipment approval, AP software and country profile, client radio and OS support, regulatory-domain state, network discovery, WPA3/PMF or MLO association, and the final band actually used. The report’s 22% Apple slice is only a device-family share, not a failure rate.

A regulation can open a band without making it appear on a laptop’s Wi-Fi menu.

India’s G.S.R. 47(E), notified on 20 January 2026, created a defined opening for 5925–6425 MHz. Compliant low-power indoor and very-low-power outdoor access systems can operate without a licence or frequency assignment, on a shared, non-protected basis and within stated power, bandwidth and use limits. It is a permission for bounded classes of equipment. It is not a command that every radio, firmware image or client must immediately expose the band.

The APNIC 62 agenda record places the conference network report in the 9 September Lightning Talks. The official report describes a substantial temporary network: Cisco routing, UniFi switching, E7 access points, 440 unique randomized MAC addresses and 2 TB of traffic. Its incident table then records four different failures. The first says 6 GHz was not visible to most clients, leaving capacity unused and most devices unable to associate. A second reports WPA3 and MLO association failures and says the team moved to mixed WPA2/WPA3 and disabled MLO. A third concerns DHCPv4 on an IPv6-mostly VLAN for clients without 464XLAT. A fourth concerns co-channel interference. These rows cannot be collapsed into one cause.

The follow-on slide combines the Indian opening with Apple’s warning that 6 GHz is not available in all regions and a pie chart showing Apple at 22% of observed wireless client devices. That figure supplies neither the denominator behind “most” nor an Apple failure rate. It does not identify models, OS builds, regulatory domains, scan results, association attempts or final bands. It cannot show that every Apple device was capable, that every one failed, or that the other 78% used 6 GHz.

The certification transition explains why legal permission and deployed capability can diverge. A later Department of Telecommunications public notice says some models approved before G.S.R. 47(E) had the lower band disabled. A technically capable model whose earlier Equipment Type Approval covered only 2.4 or 5 GHz must cancel that approval and obtain a fresh one covering every applicable band before 6 GHz is enabled, marketed, supplied, distributed or used. The notice’s typed header says 06/03/2025, but its 2026 file path, PDF creation timestamp, notice number and both signatures point to 6 March 2026. That apparent header-year error should remain visible rather than be silently corrected.

Apple’s own documents divide the client question into smaller tests. Its regional Wi-Fi 7 availability page says devices use only 2.4 and 5 GHz where unlicensed 6 GHz operation lacks regulatory approval. Its Wi-Fi 6E and Wi-Fi 7 guide lists particular supported generations, recommends one network name across all three bands, describes a 5 GHz alternative when names differ, and lets a user disable Wi-Fi 6E for a network. The deployment specifications add a discovery boundary: capable platforms can find 6E networks through 2.4/5 GHz or through 6 GHz Preferred Scanning Channels, where the configured regulatory domain permits the band.

The access-point side has the same layered character. The E7 specification confirms that the model named in the report contains a 6 GHz radio. It does not disclose the conference controller version, firmware, country setting or SSID configuration. Ubiquiti’s 6 GHz setup guidance treats a supported region, compatible AP, WPA3/PMF, band enablement and 5 GHz-assisted joining as separate conditions. Its current regional list gives India an indoor support floor of UniFi Network 10.4 and AP 8.6.10. That current floor proves a release gate exists; it does not prove which versions APNIC 62 ran. Its SSID and AP settings guide warns that a 6 GHz-only SSID can be hard to discover and that enabling MLO brings WPA3 and can limit connectivity for some clients.

This leaves a precise conclusion. The conference demonstrated a compatibility gap after authorization. It did not isolate one universal client defect, establish zero successful 6 GHz sessions, or connect the separate DHCP/464XLAT problem to the radio. A device may fail before discovery, fail during security association, connect on 5 GHz as an intentional fallback, or associate yet lack IPv4 service. Each state needs its own denominator.

Sources