Re: [Captive-portals] CAPPORT support in iOS 14 and macOS Big Sur betas

Michael Richardson <> Thu, 02 July 2020 18:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1BD753A0DE2 for <>; Thu, 2 Jul 2020 11:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iDkc92cYlBdZ for <>; Thu, 2 Jul 2020 11:55:33 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 03FC73A0DDF for <>; Thu, 2 Jul 2020 11:55:32 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 11A2D389D4; Thu, 2 Jul 2020 14:52:43 -0400 (EDT)
Received: from ([]) by localhost (localhost []) (amavisd-new, port 10024) with LMTP id RqrTXQFNtz_U; Thu, 2 Jul 2020 14:52:42 -0400 (EDT)
Received: from ( []) by (Postfix) with ESMTP id 748EB389D3; Thu, 2 Jul 2020 14:52:42 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by (Postfix) with ESMTP id 2BC423DE; Thu, 2 Jul 2020 14:55:31 -0400 (EDT)
From: Michael Richardson <>
To: Tommy Pauly <>
cc: David Bird <>, Erik Kline <>, captive-portals <>
In-Reply-To: <>
References: <> <>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 02 Jul 2020 14:55:31 -0400
Message-ID: <14962.1593716131@localhost>
Archived-At: <>
Subject: Re: [Captive-portals] CAPPORT support in iOS 14 and macOS Big Sur betas
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of issues related to captive portals <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 02 Jul 2020 18:55:35 -0000

Not really a CAPPORT protocol problem... but...

Tommy Pauly <> wrote:
    > One point I wanted to clarify: the iOS and macOS betas support for
    > CAPPORT discovery and APIs still goes through the standard and existing
    > UI flow for captive portals. The times in which the captive portal UI
    > is shown is limited, for example to times when the user is in WiFi
    > settings.

Is there a simple way for the user to get back to the portal page from the
notification bar?  Can the user choose to keep it open longer?

I noticed on the Thalys train that if you closed the portal page that it
tended to kick you off the network.  That is definitely an anti-pattern!!!
I don't know how we will cope with it, while at the same time, making it
clear that it's a bad design.

Worse was that the portal page had a nice tiled map with the current
location... AND THE TILES WERE NOT LOCAL.  So as more and more people learnt
to keep the page open... the network got significantly slower.

    > Thus, while adoption should indeed be easy and only require
    > adding a small bit of infrastructure in order to provide a flow that
    > doesn’t require redirects, the set of circumstances in which a network
    > can display content to the user is not increased.

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-