Captive-Portal Identification in DHCP and Router Advertisements (RAs)
RFC 8910

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: barryleiba@gmail.com, The IESG <iesg@ietf.org>, capport-chairs@ietf.org, mt@lowentropy.net, captive-portals@ietf.org, draft-ietf-capport-rfc7710bis@ietf.org, Martin Thomson <mt@lowentropy.net>, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Captive-Portal Identification in DHCP / RA' to Proposed Standard (draft-ietf-capport-rfc7710bis-10.txt)

The IESG has approved the following document:
- 'Captive-Portal Identification in DHCP / RA'
  (draft-ietf-capport-rfc7710bis-10.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:
https://datatracker.ietf.org/doc/draft-ietf-capport-rfc7710bis/


Technical Summary:

This document defines DHCP and RA options that allow a network to indicate the
location of a captive portal.

This version of the document replaces RFC 7710 with clarifications about what
the "location of a captive portal" means, a means for a network to indicate the
absence of a captive portal, and a new DHCP code point that we believe to be
uncontested.

Working Group Summary:

This document was fairly uncontroversial in discussions.

Document Quality:

The document is a considerable refinement over the previous version, which left
many aspects undefined.  Experiments (and multiple implementations) revealed
that the previous version was undeployable due to the DHCP option conflict.  We
have several implementations and have validated this.  Those implementations are
prototype quality, but implemented in major operating system stacks, so we are
confident that this is implementable.

Personnel:

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