Re: [Captive-portals] Proposals to discover Provisioning Domains (& Captive Portals)

David Bird <dbird@google.com> Sun, 12 March 2017 20:14 UTC

Return-Path: <dbird@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 9B04E12950C for <captive-portals@ietfa.amsl.com>; Sun, 12 Mar 2017 13:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 MewlY3WAgM6w for <captive-portals@ietfa.amsl.com>; Sun, 12 Mar 2017 13:14:28 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 B7E5812941C for <captive-portals@ietf.org>; Sun, 12 Mar 2017 13:14:28 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id r45so19847299qte.3 for <captive-portals@ietf.org>; Sun, 12 Mar 2017 13:14:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aXBRhP/CHMIaWF0el9/tSQVqyGniVZIvCsrKpwU7IZg=; b=WWSPENEhVTcENYM3cZsJvnxO+qxyv+6W4TkBryvR315cXMwJrITyIpxYJe1tWFuoRx sl3fucMqDjge5MXgbW1G3jSetHqZ/Gv2Aih4vtPzQzqVbqpwFgJUGBYfZEPo2+ltd7ln xBTA2R3PbvoUN5Y1WpcIpJyLIwWVoSTF/btFv4DgWuk8ICZ6OmIpVSnF8w+23pjAMa4C KJS408XoSFtwdMcC7UVZVsfR1Hz/y1bmIzeDhqTTEkFdWqHdp0oQ1/H5wkVLB4i2TwVI o/f+uQR633xWmcGNKzfT+H+4x1BKaz7eRkvUBTgUNMQ/ZwSM14Ju+jX0M0/h7jS3peqv UutA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aXBRhP/CHMIaWF0el9/tSQVqyGniVZIvCsrKpwU7IZg=; b=qdQBh6XdnO/ZQFFiYuKHhZk7CnaPUyh3FEfIOPb2+zt42ANolZS18Th+iwrZnLvlvz k0opbuo8dUVGNbwcR5C3ZMjxx4ci9dJyg6WEfjaZIuHsO3PHOkFsb9dp8DyERFe7rKXO F2km/i7jnCExOdvGMBL/dtmhcb0pEys59UeOYOIO7qM7P3T3KcW6SmmSVQrWghWnAYUp ryAbpMT3cQyFRL/+S01JU2mVEuo0FPtXymT2fcbmD1ZGOxuZR6p5SkTwRP7SJq5NgZlp RnHZ1LsrG+/8Fhb73wELnLdn24yFGGQf3feTt3eUVuYuskk3QtKyH1k9Y75fvK5HoTOA wa9A==
X-Gm-Message-State: AMke39mD6eydTlNgxq9iIsNbw91+sFCj6mwnHvN+MX/SqqTCjP29cn58nsT/ryK2Tj1OQzHKT9nL3zLZhMRaYJRJ
X-Received: by 10.237.57.164 with SMTP id m33mr31176393qte.293.1489349667821; Sun, 12 Mar 2017 13:14:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.128.167 with HTTP; Sun, 12 Mar 2017 13:14:27 -0700 (PDT)
In-Reply-To: <EE939357-775A-4A2E-BBD6-83A83CD2249A@apple.com>
References: <EE939357-775A-4A2E-BBD6-83A83CD2249A@apple.com>
From: David Bird <dbird@google.com>
Date: Sun, 12 Mar 2017 13:14:27 -0700
Message-ID: <CADo9JyXhEDUC7SEpi-pDr4d2nhxG3u5WEQYVEjNU4OksXF9f4g@mail.gmail.com>
To: Tommy Pauly <tpauly@apple.com>
Content-Type: multipart/alternative; boundary="001a11410306e6091c054a8e3d48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/nPnA72jmj7Y0aR7yKKRbT3eNwIg>
Cc: "captive-portals@ietf.org" <captive-portals@ietf.org>, draft-bruneau-pvd.authors@ietf.org
Subject: Re: [Captive-portals] Proposals to discover Provisioning Domains (& Captive Portals)
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.17
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: Sun, 12 Mar 2017 20:14:30 -0000

HI Tommy,

I agree, there is synergy, particularly as it relates to our desire to have
a HTTP API like the one in your I-D.

A few high-level comments:

- Could RFC 7710 be used to identify the PvD?

- Do you envision this API being implemented in NAS devices (by vendors) or
portals (by hotspot web/portal developers)?

- In section 5.3 Reachability, would the client be learning all the
available resources (e.g. the walled garden)? As a hotspot operator, I
would probably prefer only giving this information on a need-to-know basis
and not expose all my partners (advertisers, roaming partners, etc) to
every visitor upon arrival.

- I believe we could improve (real-time) signaling with capport ICMP
<https://github.com/wlanmac/draft-wkumari-capport-icmp-unreach/blob/master/README.md>
(and the overall capport architecture
<https://tools.ietf.org/html/draft-larose-capport-architecture-00>)


On Sun, Mar 12, 2017 at 12:34 PM, Tommy Pauly <tpauly@apple.com> wrote:

> Hello,
>
> I wanted to give the CAPPORT group a heads up about some related work in
> the explicit discovery of Provisioning Domains (PvDs), that provides one
> way of discovering and interacting with Captive Portals and other features
> of a network:
>
> Proposals to discover Provisioning Domains
> https://datatracker.ietf.org/doc/draft-bruneau-pvd/
>
> PvDs are a concept from MIF, and before that group closed, one of the open
> questions was how to discover and communicate explicit information about
> networks and prefix ranges to a device. We've been working on this with
> Cisco, Apple, and Google contributors, and we think that there is a lot of
> potential synergy with the captive portal discovery.
>
> The document also goes into various tradeoffs of approaches to getting
> this information, which is a relevant conversation for how we discover and
> contact captive portals as well.
>
> Please take a read through and let us know your thoughts!
>
> Thanks,
> Tommy Pauly
> Apple
>
> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals
>