[Captive-portals] CAPPORT Experiment for IETF107.

Warren Kumari <warren@kumari.net> Sun, 16 February 2020 22:13 UTC

MIME-Version: 1.0
From: Warren Kumari <warren@kumari.net>
Date: Sun, 16 Feb 2020 17:13:12 -0500
Message-ID: <CAHw9_iLeo5f=aKPXYjc8v9uf35iJNnSp8KQO-k4APzyBNZFm7A@mail.gmail.com>
To: captive-portals <captive-portals@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/2-b4_i5lvo-lUBuWszMVTQTNMcA>
Subject: [Captive-portals] CAPPORT Experiment for IETF107.
Precedence: list

Hi there CAPPORT,

Just a quick note that we are planning on doing another CAPPORT
experiment at IETF107.

See https://www.mail-archive.com/captive-portals@ietf.org/msg00680.html
for previous experiment announcement, and "Don't Panic" disclaimer....

This time we intend having a separate, hidden "Experiments" SSID, and
a captive portal device.
We will be announcing the CAPPORT information using DHCP Option 114,
and, thanks to Clemens Schimpe, probably also RAs.

As with all experiments, this is "best effort" only - running the IETF
network comes first, and the experiment will be disabled if is causes
any issues... As it is an opt-in experiment on a hidden ssid I don't
expect any issues, but $disclaimer required :-)

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] CAPPORT Experiment for IETF107. Warren Kumari