[Captive-portals] Updates to the architecture draft

Kyle Larose <klarose@sandvine.com> Tue, 06 March 2018 01:47 UTC

Return-Path: <klarose@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 E0012127286 for <captive-portals@ietfa.amsl.com>; Mon, 5 Mar 2018 17:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.93
X-Spam-Level:
X-Spam-Status: No, score=-1.93 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 TBG1YtJVTvHR for <captive-portals@ietfa.amsl.com>; Mon, 5 Mar 2018 17:47:20 -0800 (PST)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04A03124217 for <captive-portals@ietf.org>; Mon, 5 Mar 2018 17:47:20 -0800 (PST)
Received: from WTL-EXCHSV2-2.sandvine.com (192.168.194.59) by WTL-EXCHSV2-2.sandvine.com (192.168.194.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521) id 15.1.1034.26; Mon, 5 Mar 2018 20:47:18 -0500
Received: from WTL-EXCHSV2-2.sandvine.com ([fe80::70e5:d09e:7bb9:986a]) by WTL-EXCHSV2-2.sandvine.com ([fe80::70e5:d09e:7bb9:986a%20]) with mapi id 15.01.1034.026; Mon, 5 Mar 2018 20:47:18 -0500
From: Kyle Larose <klarose@sandvine.com>
To: "captive-portals@ietf.org" <captive-portals@ietf.org>
Thread-Topic: Updates to the architecture draft
Thread-Index: AdO07GG1shZAa9eMQpiHpJl0XJ197A==
Date: Tue, 06 Mar 2018 01:47:18 +0000
Message-ID: <ec775a287eb6478c983670b66f112760@sandvine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.200.51]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_ec775a287eb6478c983670b66f112760sandvinecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/dHMSF0kXkxe460582aDYpfRbvvM>
Subject: [Captive-portals] Updates to the architecture draft
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 06 Mar 2018 01:47:22 -0000

Hey everyone,

I've been trying to tackle the outstanding issues on the architecture draft. I've focused on two so far:

*         How to identify the user equipment (https://github.com/capport-wg/architecture/issues/5)

*         Making sure the API is secure (https://github.com/capport-wg/architecture/issues/6)

Unfortunately, I did not finish these changes in time to upload a new version of the draft; I'm a few hours too late.
Instead, please read the editors copy: https://capport-wg.github.io/architecture/draft-ietf-capport-architecture.html.

I'm sure there'll be lots to discuss at the meeting. Hopefully these changes will serve as a starting point.

Thanks,

Kyle

Disclaimer:
This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is considered confidential, proprietary, sensitive and/or otherwise legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.