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

Martin Thomson <martin.thomson@gmail.com> Mon, 13 March 2017 00:39 UTC

Return-Path: <martin.thomson@gmail.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 F1A6412944D; Sun, 12 Mar 2017 17:39:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=gmail.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 MboxkBK-OGIr; Sun, 12 Mar 2017 17:39:20 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 44B7112940C; Sun, 12 Mar 2017 17:39:20 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id v125so208066501qkh.2; Sun, 12 Mar 2017 17:39:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jd48iPbKBAGX+aTJVtgU3/crrW9Exd6YIknimjkL8cs=; b=VpQvyAGqKvQLRVFhz7nGNlOpwbgeiuprWf7iV8bfcEAbVHQMuw42gmKJCCTtcqGzkt xOhpcEuTzKa/hbTyG2yKwnpT6jQonkhsaLUDhBD1jwobzbT9ChC6hOu7bAwD0Vfm0l9H 5+5w2aIq88msMWWRbUbr5VHVPFu4SdQa9Vboi/eBROMw/EeJj2r4Koge6lKEOD85QZnB KeMdm8z/CvpQdbNN0IwaQb7m6cPcxmPjCrLgDNMmvR5DH8jpaITrtAtSz8JWnpLcKBEZ yAQwAxBfDTetOtxFR1PukQbqfIjKeZEfXwasD2cWx0t+3QOzn7HdyrKjlLiOm40eO9+2 F92w==
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=jd48iPbKBAGX+aTJVtgU3/crrW9Exd6YIknimjkL8cs=; b=lI71F0hczMt7q4kcUGv24QhJgwemGBt0OuhJJMCfoVcfEFL7Bat+mGQSr23wUh/3F9 5RJe7XZvkbgGNYdIYy1w4MCY5yYfiDqTibvdTq+F/K5nDLdpSMw4N4LEITjjYc+Tc1fU 86IkRX7x7SkIn+VMxYsKJZnKpj6iaU/qNJZi/IGid5gIeHFVzN+Xu3WgWXdIs+gmogUW LzsA/cGhwDV6S4zi/c0nkawmQzlFuBlwMYIcVLv7KNmRRoDI6L22PxSf4VsUbYTM6yaU XQ3t5VPfReLv3lF3bGY/DDyKwdL35mP62/GnH0cabNE2OR+bOUBY5PvqDLJelo2VXoR9 qAGw==
X-Gm-Message-State: AMke39nfqHvOeuBQsMQXE1kdsq6UrZ4HG7SAA4d0atopXoz1OkRoA9mbgij9hs+w5mJbJhrKYkd6Vv8j8XKZaQ==
X-Received: by 10.55.185.131 with SMTP id j125mr28645979qkf.115.1489365559373; Sun, 12 Mar 2017 17:39:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.194 with HTTP; Sun, 12 Mar 2017 17:39:18 -0700 (PDT)
In-Reply-To: <CADo9JyXhEDUC7SEpi-pDr4d2nhxG3u5WEQYVEjNU4OksXF9f4g@mail.gmail.com>
References: <EE939357-775A-4A2E-BBD6-83A83CD2249A@apple.com> <CADo9JyXhEDUC7SEpi-pDr4d2nhxG3u5WEQYVEjNU4OksXF9f4g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 13 Mar 2017 11:39:18 +1100
Message-ID: <CABkgnnVwwaZgtO5c+8Yq8urBDkiPp9txWTA5Ya9U1DdQhxM8=Q@mail.gmail.com>
To: David Bird <dbird@google.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/Mo-C1cAsfpFHD1vk4H9RFHkl9V8>
Cc: "captive-portals@ietf.org" <captive-portals@ietf.org>, draft-bruneau-pvd.authors@ietf.org, Tommy Pauly <tpauly@apple.com>
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: Mon, 13 Mar 2017 00:39:22 -0000

There's also this terrible idea from an age ago, which like 7710 uses
DHCP: https://datatracker.ietf.org/doc/rfc5986/  Unlike 7710, it
produces a name.

On 13 March 2017 at 07:14, David Bird <dbird@google.com> wrote:
> 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 (and
> the overall capport architecture)
>
>
> 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
>
>
>
> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals
>