|
The currently proposed solution has 3 components: 1. The ICMP component is used to detect a captive network. 2. The DHCP component is used to discover the address of the Captive Portal. 3. The API is an information service with a standardized interface that allows discovery and potentially remediation of the requirements for network access. The ICMP and DHCP components are sufficient to resolve the redirection and HTTPS issue. I would consider the API as an optional component - it might create some user experience benefits if the device developers and network operators choose to use it. The difficulty with the API is having a way of codifying all of the possible network access requirements. I'm not sure this is reasonably possible. Assuming that such a definition is possible, then there is some benefit to the common definition. (It also strikes me that this definition would make a nice back end design for the Captive Portal itself.) Cheers! Christian On 17-04-05 10:25 AM, David Bird wrote:
|