Protocol Action: 'Captive Portal API' to Proposed Standard (draft-ietf-capport-api-08.txt)

The IESG <> Thu, 02 July 2020 13:17 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 123183A09A4; Thu, 2 Jul 2020 06:17:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Protocol Action: 'Captive Portal API' to Proposed Standard (draft-ietf-capport-api-08.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <>, Martin Thomson <>,,,,,,
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <>
Date: Thu, 02 Jul 2020 06:17:14 -0700
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 02 Jul 2020 13:17:14 -0000

The IESG has approved the following document:
- 'Captive Portal API'
  (draft-ietf-capport-api-08.txt) as Proposed Standard

This document is the product of the Captive Portal Interaction Working Group.

The IESG contact persons are Murray Kucherawy and Barry Leiba.

A URL of this Internet Draft is:

Technical Summary:

This document defines a simple HTTP API that allows a network to provide
information about captive portal status.

Working Group Summary:

This document was at times controversial in discussions.  Some participants felt
that the potential for an API of this form to be spoofed was a problem.  Some
participants felt that this particular design was especially hard for network
operators to deploy due to some of the inherent complexities in deployments.
Some participants felt that it would be necessary to include more detailed
information, such as what sites were accessible and what sites were not.  At
times there were communication difficulties in the working group that
exacerbated problems.  However, as a baseline set of features, both clients and
networks have demonstrated agreement that the current shape of this document is

Document Quality:

The document is short and concise and of high quality.  The fields that are
defined are all driven by real client requirements and implementation experience
in multiple implementations.  We have experience with deploying this on the IETF


Martin Thomson is document shepherd.  Barry Leiba is the responsible Area Director.