A Faster Ticket Booth for Wi-Fi: What RFC 8910 Means for Captive Portals
Think of public Wi-Fi like the gate at a theme park. Before visitors enjoy the rides (the open Internet), they stop at the ticket booth – your captive-portal page – to accept terms or log in.
RFC 8910 is simply a new way to hand every device a clear, instant map to that booth the moment it joins the network. Here’s how it works and why it matters.
| Network message | Option / Type | Role |
|---|---|---|
| DHCP v4 | Option 114 | Adds the portal’s URL when a client asks for an IPv4 address. |
| DHCP v6 | Option 103 | Same idea for IPv6 clients using DHCPv6. |
| IPv6 Router Advertisement | Type 37 | Covers pure-IPv6 setups that rely on RAs instead of DHCP. |
Each option contains one HTTPS link – your Captive Portal API endpoint (defined in RFC 8908). If you advertise it in more than one place, keep the link identical across all three.
Why operators should enable RFC 8910
- Instant portal launch: Modern iOS, Android, Windows, and macOS versions watch for these options and pop the portal window automatically – no waiting for the user to type a URL.
- Smooth security path: The link is HTTPS, so browsers stay happy and you avoid certificate warnings.
- Future-proof compliance: Browsers and OSs are encouraging up-front disclosure. Supporting the standard keeps your network experience in line with their expectations.
How to put RFC 8910 to work
- Choose a stable TLS URL, e.g. https://portal.myplace.io/capport.
- Configure your controller or gateway to include Option 114, Option 103, and RA Type 37 with that exact link.
- Keep it short – ≤255 bytes—so it fits the IPv4 envelope.
- Use the special value urn:ietf:params:capport:unrestricted on SSIDs that don’t require a portal.
Bottom line
RFC 8910 doesn’t replace captive portals – it refines how devices discover them. By handing out a clear map at the gate, you deliver a faster, cleaner onboarding experience that works the way today’s operating systems expect. For network owners and service providers, enabling these options is a quick win that keeps your captive-portal service both user-friendly and standards-compliant.
