There are several short-coming of Captive Portal implementations. Take, for instance, handling HTTPS connections. Some implementations might time out the connection (assuming the request doesn't fall in the walled garden), others might return a TCP reset, even others might terminate the TLS (with browser errors) to issue the redirect. (Chilli allows you do do all three ;)
There is generally a need for better Detection of CP networks, Notification of resources that fall outside the walled garden of CP networks, and a more standardized protocol for Client Interaction.
There are several short-coming of Captive Portal implementations. Take, for instance, handling HTTPS connections. Some implementations might time out the connection (assuming the request doesn't fall in the walled garden), others might return a TCP reset, even others might terminate the TLS (with browser errors) to issue the redirect. (Chilli allows you do do all three ;)
There is generally a need for better Detection of CP networks, Notification of resources that fall outside the walled garden of CP networks, and a more standardized protocol for Client Interaction.
Proposal to deliver CP information via DHCP/IPv6-RA
Proposal to notify client with ICMP when blocked by CP
IETF CP mailing list discussion
This issue is to track any development progress related to any new standards.