Re: [Captive-portals] FW: New Version Notification for draft-larose-capport-architecture-00.txt
Dave Dolson <ddolson@sandvine.com> Fri, 10 March 2017 02:27 UTC
Return-Path: <ddolson@sandvine.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 E89161289B0 for <captive-portals@ietfa.amsl.com>; Thu, 9 Mar 2017 18:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level:
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 lDp-e7rqfQKq for <captive-portals@ietfa.amsl.com>; Thu, 9 Mar 2017 18:27:24 -0800 (PST)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14EAF129463 for <captive-portals@ietf.org>; Thu, 9 Mar 2017 18:27:24 -0800 (PST)
Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by wtl-exchp-2.sandvine.com ([::1]) with mapi id 14.03.0319.002; Thu, 9 Mar 2017 19:12:55 -0500
From: Dave Dolson <ddolson@sandvine.com>
To: Martin Thomson <martin.thomson@gmail.com>, Kyle Larose <klarose@sandvine.com>
Thread-Topic: [Captive-portals] FW: New Version Notification for draft-larose-capport-architecture-00.txt
Thread-Index: AQHSmSOZxJL3On1L4Uai8DSFGjH47aGNadMAgAASjgD//7d4Ew==
Date: Fri, 10 Mar 2017 00:12:54 +0000
Message-ID: <20170310001253.8499287.50558.142467@sandvine.com>
References: <148909812984.5791.13927658190997966571.idtracker@ietfa.amsl.com> <D76BBBCF97F57144BB5FCF08007244A77058CF7F@wtl-exchp-1.sandvine.com>, <CABkgnnUC9N0_Bb2P-=6+iOg3FuxqNAve-hgCVxWb3Sh+zHRb_w@mail.gmail.com>
In-Reply-To: <CABkgnnUC9N0_Bb2P-=6+iOg3FuxqNAve-hgCVxWb3Sh+zHRb_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/4GRPdfVDBQcmlFyIkb2brAv3Tp0>
Cc: "captive-portals@ietf.org" <captive-portals@ietf.org>
Subject: Re: [Captive-portals] FW: New Version Notification for draft-larose-capport-architecture-00.txt
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: Fri, 10 Mar 2017 02:27:26 -0000
Martin, We look forward to addressing all of these issues. We have a story for (1), and we've waved our hands about (2) and (3). I think a separate draft might be appropriate for the API. To take an initial stab at it, we think a GET to the URI provides a JSON document of information and menu choices, since we've heard of a lot of different ideas about how User Equipment might want to navigate the captive portal. Clearly this will need to be standardized. Input and new wording is very welcome. -Dave Original Message From: Martin Thomson Sent: Thursday, March 9, 2017 6:32 PM To: Kyle Larose Cc: captive-portals@ietf.org; Dave Dolson Subject: Re: [Captive-portals] FW: New Version Notification for draft-larose-capport-architecture-00.txt Thanks for putting this together Kyle. After a brief skim (I will read this more thoroughly in the next week or so), I have some high level comments that I think you should spend some time thinking about: 1. How to manage trust in the ICMP messages. I like that you are just using these to nudge a client into the flow, but how do you avoid spoofing? We've a little bit of experience with this in QUIC and there is some advice on how a client might handle unauthenticated ICMP there that might be reused (key observation: v6 >> v4 because you get much better assurances about the message coming from a path element). 2. How do you authenticate the interactions with the portal? How do you decide what to give it? 3. How to interact with the DHCP-provided URI. The big failing of RFC 7710 (in my view) is that it doesn't really say what to do with this URI that falls into your lap. I think that you either shove it in a browser or poke at it with some sort of other type of request (you seem to assume the latter here), but that's astonishingly vague. This seems like a great opportunity to point at other work. Work I'm hoping will start at the hackathon. On 10 March 2017 at 09:26, Kyle Larose <klarose@sandvine.com> wrote: > Hello, > > Dave and I realized that the working group had discussed, at length, a possible solution to the captive portal problem. > Since we were planning on working on it during the hackathon, we figured it'd be a good idea to capture the working group's ideas in an architecture. > > We've uploaded the below draft as a skeleton for the architecture in the interest of having something to work from for the hackathon, > and discuss at the meeting. > > Let us know what you think. > > Thanks! > > Kyle > > -----Original Message----- > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Sent: Thursday, March 09, 2017 5:22 PM > To: Dave Dolson; Kyle Larose > Subject: New Version Notification for draft-larose-capport-architecture-00.txt > > > A new version of I-D, draft-larose-capport-architecture-00.txt > has been successfully submitted by Kyle Larose and posted to the IETF repository. > > Name: draft-larose-capport-architecture > Revision: 00 > Title: CAPPORT Architecture > Document date: 2017-03-09 > Group: Individual Submission > Pages: 10 > URL: https://www.ietf.org/internet-drafts/draft-larose-capport-architecture-00.txt > Status: https://datatracker.ietf.org/doc/draft-larose-capport-architecture/ > Htmlized: https://tools.ietf.org/html/draft-larose-capport-architecture-00 > > > Abstract: > This document aims to document concensus on the CAPPORT architecture. > DHCP, ICMP, and an HTTP API are used to provide the solution. > > > > > Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > _______________________________________________ > Captive-portals mailing list > Captive-portals@ietf.org > https://www.ietf.org/mailman/listinfo/captive-portals
- [Captive-portals] FW: New Version Notification fo… Kyle Larose
- Re: [Captive-portals] FW: New Version Notificatio… Dave Dolson
- Re: [Captive-portals] FW: New Version Notificatio… Martin Thomson
- Re: [Captive-portals] FW: New Version Notificatio… Martin Thomson