LLDP is interesting, but, as you mentioned, the enforcement function might be one of several intermediate devices...
ICMP has a few benefits.. It contains entropy by quoting original packet headers and UEs already get ICMP for a variety of network conditions (no route, needs frag, port unavailable, administratively prohibited) -- Is 'Captive portal required' so different? On Thu, Nov 8, 2018 at 10:20 PM Nasir Hafeez <[email protected]> wrote: > As discussed in yesterday's IETF meeting, CAPPORT Architecture states that > the CAPPORT web server signals allow/deny rules to Captive Portal > Enforcement device. In reality, however, there may be intermediate devices > like RADIUS servers or WiFi controllers that are doing that signaling, not > the CAPPORT web server (and in the case of walled garden entries, the web > portal is never involved). The architecture diagram and related sections of > the document should perhaps be updated to show that. > > Another option that occurred to me was using LLDP for capport signaling. > Do you think there is any utility in pursuing this? > > Regards, > > Nasir Hafeez > _______________________________________________ > Captive-portals mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/captive-portals >
_______________________________________________ Captive-portals mailing list [email protected] https://www.ietf.org/mailman/listinfo/captive-portals
