Hi y'all.
So, this short document discusses another way for Captive Portals to inform users that they are behind a CP. Basically, it uses an extended ICMP Destination Unreachable message to let the host know that the reason it cannot reach a destination is because it is behind a CP and also includes a URL to reach the CP. This idea is mainly David's, I'm largely the editor. We'd really like some feedback on this idea and the implementation we've written up. Obviously the document would need a bunch more work, but we'd like to get some idea if folk think this is worth pursuing. URL: https://www.ietf.org/internet-drafts/draft-wkumari-capport-icmp-unreach-00.txt Status: https://datatracker.ietf.org/doc/draft-wkumari-capport-icmp-unreach/ Htmlized: https://tools.ietf.org/html/draft-wkumari-capport-icmp-unreach-00 It is somewhat similar to the wkumari-dhc-capport document, but solves a different issue, in a different way - I think that they are complementary documents. Any feedback gratefully accepted. W -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ Captive-portals mailing list Captive-portals@ietf.org https://www.ietf.org/mailman/listinfo/captive-portals
