IETF Logo Mail Archive

Re: [Captive-portals] Requirements for "captive portal closed" notifications

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 21 March 2018 14:10 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: captive-portals@ietfa.amsl.com
Delivered-To: captive-portals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF1912D956 for <captive-portals@ietfa.amsl.com>; Wed, 21 Mar 2018 07:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SkGCVysIwhJp for <captive-portals@ietfa.amsl.com>; Wed, 21 Mar 2018 07:10:04 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D56BF12DA27 for <captive-portals@ietf.org>; Wed, 21 Mar 2018 07:10:02 -0700 (PDT)
Received: from dooku.sandelman.ca (dhcp-86ae.meeting.ietf.org [31.133.134.174]) by relay.sandelman.ca (Postfix) with ESMTPS id B217A1F95A for <captive-portals@ietf.org>; Wed, 21 Mar 2018 14:10:00 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 205A061E; Wed, 21 Mar 2018 14:09:30 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: captive-portals@ietf.org
In-reply-to: <aa5ea1b06f9bb7981552f689ef8742d9cae9b2e3.camel@laposte.net>
References: <CAKD1Yr3rP24jQ6sMpoXZ3pU02FmvwDNc9=w2oAh4bMWZmEtQ_A@mail.gmail.com> <CADo9JyXpW-rn81kwOkqx8+=iBMTWd+x1FoMm-YTCm+Efmb23gQ@mail.gmail.com> <CAKD1Yr0oDZQJQ1n899Vtm1VPwwV2ZaLZTJV19a35G6pHf0x1Dg@mail.gmail.com> <CADo9JyUWawp5FC8q=0KJMk8T4x-iyFjpj167UH_NPjT=b2Hn+A@mail.gmail.com> <aa5ea1b06f9bb7981552f689ef8742d9cae9b2e3.camel@laposte.net>
Comments: In-reply-to Nicolas Mailhot <nicolas.mailhot@laposte.net> message dated "Tue, 20 Mar 2018 21:11:48 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 21 Mar 2018 14:09:30 +0000
Message-ID: <20840.1521641370@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/dYfdZMqjxBxT7_P_emgle-UrJBY>
Subject: Re: [Captive-portals] Requirements for "captive portal closed" notifications
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of issues related to captive portals <captive-portals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/captive-portals/>
List-Post: <mailto:captive-portals@ietf.org>
List-Help: <mailto:captive-portals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 14:10:06 -0000

Aside from the business model of upgrades, there is also the academic
institution situation which you mention, where captive portals are often used.

The student or faculty must login.
It's not just for WIFI (there may be an additional layer of security there!).

There may be filters which will prevent:

Nicolas Mailhot <nicolas.mailhot@laposte.net> wrote:
    > Most walled gardens will want something like 'free access to
    > pr.institutionalsite.com/intranet.mybusiness.net/library.school.com',
    > downloading gigs of videos from youtube requires autorisation,
    > sex.xxx.com, playingatwork.net and examsolutions.cheater.org are
    > forbidden.

And there may be different responses needed for:

1) a specific login/upgrade/override code (from the teacher) will allow
   access to X.   I think that this is common.

2) no matter what you enter, you won't get to sex.xxx.com.
   I don't think we need anything new for this, ICMP Admin prohibit is good.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email