Captive Portal ICMP Messages
draft-wkumari-capport-icmp-unreach-02

Document Type Expired Internet-Draft (individual)
Last updated 2017-10-03 (latest revision 2017-04-01)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wkumari-capport-icmp-unreach-02.txt

Abstract

This document defines a new ICMP Type for Captive Portal Messages. The ICMP Type will only be known to clients supporting this specification and provides both generic and flow 5-tuple specific notifications from the Captive Portal NAS. Further, This document defines a multi-part ICMP extension to ICMP Destination Unreachable messages to signal, not only that the packet was dropped, but that it was dropped due to an Access Policy requiring Captive Portal interaction. Legacy clients will only be processing the ICMP Destination Unreachable. [ Editor note: The IETF is currently discussing improvements in captive portal interactions and user experience improvements. See: https://www.ietf.org/mailman/listinfo/captive-portals ] [RFC Editor: Please remove this before publication. This document is being stored in github at https://github.com/wlanmac/draft-wkumari- capport-icmp-unreach . Authors gratefully accept pull requests, and keep the latest (edit buffer) versions there, so commenters can follow along at home.]

Authors

David Bird (dbird@google.com)
Warren Kumari (warren@kumari.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)