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

Tommy Pauly <tpauly@apple.com> Thu, 02 July 2020 19:28 UTC

Return-Path: <tpauly@apple.com>
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 999993A0837 for <captive-portals@ietfa.amsl.com>; Thu, 2 Jul 2020 12:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 1QCZaNeTTwxd for <captive-portals@ietfa.amsl.com>; Thu, 2 Jul 2020 12:28:31 -0700 (PDT)
Received: from ma1-aaemail-dr-lapp03.apple.com (ma1-aaemail-dr-lapp03.apple.com [17.171.2.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23DDA3A080F for <captive-portals@ietf.org>; Thu, 2 Jul 2020 12:28:31 -0700 (PDT)
Received: from pps.filterd (ma1-aaemail-dr-lapp03.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp03.apple.com (8.16.0.42/8.16.0.42) with SMTP id 062JLoo4029090; Thu, 2 Jul 2020 12:28:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=wEOVxDWcaaUl+aPYOBuJzCvAs03sWNNmn+Lkqc8QI7o=; b=QBnpEmbXroK6Qw+qrkNiaW163bnA2kgzDJZnCNXxMO81Q+UK6BBu6qccj5RSSx+xY/NZ 6BEjMafNA8diYnCWGpJp9jnFBY+iZ+pqLdzdDFvib1NjEBu/kkIjexs5AzupDHI/chLR 57HKO+BBy1MLAoWHOBlb5FeJtdHJYen/p/bZwCAqhZW+CUpPUNuPNTfgWQJrsod8SCyK 1m11/ftGENTHXYNuf8AnCL1V7vtJB7CbVeDhhac/zBGwUTTqzBpjInaEjb7qaPAD4XQB UGywt4n7tqDKZHPpHKWws6Xwt07JaJdyI2nVQJtzkV1GnPXB0qGwY2K2Hin3KcknCjZg yw==
Received: from rn-mailsvcp-mta-lapp04.rno.apple.com (rn-mailsvcp-mta-lapp04.rno.apple.com [10.225.203.152]) by ma1-aaemail-dr-lapp03.apple.com with ESMTP id 31x544mm1n-4 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 02 Jul 2020 12:28:28 -0700
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPS id <0QCU00O4IWRFA5I0@rn-mailsvcp-mta-lapp04.rno.apple.com>; Thu, 02 Jul 2020 12:28:27 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) id <0QCU00R00WM1OM00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Thu, 02 Jul 2020 12:28:27 -0700 (PDT)
X-Va-A:
X-Va-T-CD: f2b5f3f4997c2739722f2a2be36b0eda
X-Va-E-CD: 4578b196c2d4921fe4a8c9a59c41a29a
X-Va-R-CD: e06bf14963a3da9ed87a944966f976f1
X-Va-CD: 0
X-Va-ID: 9a69bdf9-cf05-4d25-97a7-21b73c1b9641
X-V-A:
X-V-T-CD: f2b5f3f4997c2739722f2a2be36b0eda
X-V-E-CD: 4578b196c2d4921fe4a8c9a59c41a29a
X-V-R-CD: e06bf14963a3da9ed87a944966f976f1
X-V-CD: 0
X-V-ID: 4dcbc1ee-e417-48d9-bb1c-f7b8bca6e165
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-02_09:2020-07-02, 2020-07-02 signatures=0
Received: from [17.234.115.85] (unknown [17.234.115.85]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.5.20200312 64bit (built Mar 12 2020)) with ESMTPSA id <0QCU00LBXWRD7U00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Thu, 02 Jul 2020 12:28:26 -0700 (PDT)
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 13.4 \(3608.80.7.2.3\))
From: Tommy Pauly <tpauly@apple.com>
In-reply-to: <14962.1593716131@localhost>
Date: Thu, 02 Jul 2020 12:28:25 -0700
Cc: David Bird <dbird@google.com>, Erik Kline <ek.ietf@gmail.com>, captive-portals <captive-portals@ietf.org>
Content-transfer-encoding: quoted-printable
Message-id: <797E6BD4-1D58-486E-9432-BE920E893C31@apple.com>
References: <CADo9JyUVZfRSpmjYLxBBH73hd7F-+1hwSbr2qDzriaQjLndmFA@mail.gmail.com> <4E013237-9B3C-426B-961A-878EDFCE4806@apple.com> <14962.1593716131@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.80.7.2.3)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-07-02_09:2020-07-02, 2020-07-02 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/82PHdwXYYjsaPeG0Z_yqwMj33WY>
Subject: Re: [Captive-portals] CAPPORT support in iOS 14 and macOS Big Sur betas
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 02 Jul 2020 19:28:33 -0000


> On Jul 2, 2020, at 11:55 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Not really a CAPPORT protocol problem... but...
> 
> Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org> 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?

One of the goals of having the portal URL be transmitted in the API is to aid ways of getting back to that URL. We don’t have any such way in the beta UI, but such an experience is possibility in the future if networks adopt the API.

Thanks,
Tommy

> 
> 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 <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
>