Last Call Review of draft-ietf-capport-api-07
review-ietf-capport-api-07-opsdir-lc-dunbar-2020-05-09-2-00

Request Review of draft-ietf-capport-api
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2020-05-11
Requested 2020-04-27
Authors Tommy Pauly , Darshak Thakore
I-D last updated 2020-05-09
Completed reviews Secdir Last Call review of -07 by Robert Sparks (diff)
Genart Last Call review of -07 by Brian E. Carpenter (diff)
Opsdir Last Call review of -07 by Linda Dunbar (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-ietf-capport-api by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/1LYDeP9FKEFxWM-obVyx4FbZzWY
Reviewed revision 07 (document currently at 08)
Result Has nits
Completed 2020-05-09
review-ietf-capport-api-07-opsdir-lc-dunbar-2020-05-09-2-00
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