[Captive-portals] Opsdir last call review of draft-ietf-capport-api-07

Linda Dunbar via Datatracker <noreply@ietf.org> Sat, 09 May 2020 22:06 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: captive-portals@ietf.org
Delivered-To: captive-portals@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 081CF3A0BE0; Sat, 9 May 2020 15:06:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: captive-portals@ietf.org, draft-ietf-capport-api.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.129.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158906200797.26124.16073204264263445484@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Sat, 09 May 2020 15:06:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/QSROsVf0z9eGs_gzDm3xs0JrY1c>
Subject: [Captive-portals] Opsdir last call review of draft-ietf-capport-api-07
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 09 May 2020 22:06:49 -0000

Reviewer: Linda Dunbar
Review result: Has Nits

I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last call comments.

This document provides examples of the API structure between client and captive
server. The document is well written. I just have a question:

What improvement does the proposed API have over today's existing communication
between clients and  Captive Server(s)? Captive servers have been deployed
everywhere, like airport or restaurants trying to access free WIFI. What
problems does the existing method have to justify this newly proposed APIs?

Cheers,
Linda Dunbar