IETF Logo Mail Archive

Re: [Captive-portals] captive portal browser capabilities

Erik Kline <ek@loon.co> Fri, 18 January 2019 19:49 UTC

Return-Path: <ek@google.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 BD145131366 for <captive-portals@ietfa.amsl.com>; Fri, 18 Jan 2019 11:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.5
X-Spam-Level:
X-Spam-Status: No, score=-9.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.co
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 5GX5wk1nyBh3 for <captive-portals@ietfa.amsl.com>; Fri, 18 Jan 2019 11:49:04 -0800 (PST)
Received: from mail-it1-x133.google.com (mail-it1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8C0F131362 for <captive-portals@ietf.org>; Fri, 18 Jan 2019 11:49:04 -0800 (PST)
Received: by mail-it1-x133.google.com with SMTP id h193so7344665ita.5 for <captive-portals@ietf.org>; Fri, 18 Jan 2019 11:49:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.co; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=1KgSJZQyP5WfCUkPkbM724BPD/0jqpXah9pLb3jKGoo=; b=trSXepAUuCf1tUuIF7umTPiRY18t7KFdnJ0Ttz7lPpbnFA0L9ry5lfIxOVvtZDl/pG ffCP3HuaXuCDZfBiC29RaOk7opOhDrqw1F4rKJzOOHVII2bx77MOo6g+OLp36Ys9+yi+ uCZttJ5BWq6/Jlbvq+3/4qot5lUxG+pcIwsJQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=1KgSJZQyP5WfCUkPkbM724BPD/0jqpXah9pLb3jKGoo=; b=MGRKm9UVj1KL5ddvDXGOs5dWbQuy0gdpxF+awRBvX2Dy+8hy0wZb5hc2HHdb1fwFqU sBqxv9/nkFq9BVQfGBA2nhzovyy4wJrII5iNFyPRxjCfy//dgfV/054hDvt5oVCojf6r 1kok17w+e0NX5V/8uJxt/2BaZTRX75QQU4ml/BmjFStozAo9z3MM0TgZt64MElVfnA5N /SAFstXKv1dxd1JWVdrgR/HCukNFzIVymkHaDL6U4BlmTISBoW1udOgBfm0KiB1nyibq ippe/1nLZX7X2YfbCv2MCLtWReR2zl/dL/GExfuZB8wF6lTWMsk5MfoK5Uw5UyPMC1Hy HIXA==
X-Gm-Message-State: AJcUukedDP6X5g583W8dGbLCjp804R8yrOzfAiReeoKap/4KlGXHgZZR aG6ch5woBSjvPhwihMh5Ojsi5zI3pL9UR6UGJumFPotxMFM=
X-Google-Smtp-Source: ALg8bN5q2LF7eQmKSTKxqTN2lYOREuw9K8k2CSQ8u4upOzzopxmcmqOTi+W8Qz50gdbtfqUP474Symji1bQ0mNaPqHk=
X-Received: by 2002:a02:c81a:: with SMTP id p26mr11721276jao.59.1547840943505; Fri, 18 Jan 2019 11:49:03 -0800 (PST)
MIME-Version: 1.0
References: <26273.1547831492@localhost>
In-Reply-To: <26273.1547831492@localhost>
Reply-To: ek@loon.co
From: Erik Kline <ek@loon.co>
Date: Fri, 18 Jan 2019 11:48:50 -0800
Message-ID: <CAAedzxpTtM1r1Gpgd=sno2M+57fbfzjMfrbyHNBH8Ni13Ku9+g@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: captive-portals <captive-portals@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/BltI0zNmYo57woqySzBl7W2rWf0>
Subject: Re: [Captive-portals] captive portal browser capabilities
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: Fri, 18 Jan 2019 19:49:07 -0000

> I will not be surprised if there is nothing that satisfies my needs
> and is still capable of dealing with portals.

Can you clarify what "dealing with" means here for you?

Automatically interacting with a portal? (e.g. clicking agreement
checkboxes, filling in email addresses or facebook details, ...)

or

Detecting the presence of a portal and then "calling a human for
help"?  (vis. your Chrome X11 forwarding idea)

or something else?

v2.23.0 | Report a Bug | By Email