Browse Prior Art Database

Captive-Portal Identification Using DHCP or Router Advertisements (RAs) (RFC7710)

IP.com Disclosure Number: IPCOM000245065D
Original Publication Date: 2015-Dec-01
Included in the Prior Art Database: 2016-Feb-07
Document File: 16 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Kumari: AUTHOR [+4]

Abstract

In many environments, users need to connect to a captive-portal device and agree to an Acceptable Use Policy (AUP) and/or provide billing information before they can access the Internet. It is anticipated that the IETF will work on a more fully featured protocol at some point, to ease interaction with captive portals. Regardless of how that protocol operates, it is expected that this document will provide needed functionality because the client will need to know when it is behind a captive portal and how to contact it.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 16% of the total text.

Internet Engineering Task Force (IETF)                         W. Kumari Request for Comments: 7710                                        Google Category: Standards Track                                 O. Gudmundsson ISSN: 2070-1721                                               CloudFlare                                                              P. Ebersman                                                                  Comcast                                                                 S. Sheng                                                                    ICANN                                                            December 2015

 Captive-Portal Identification Using DHCP or Router Advertisements (RAs)

Abstract

   In many environments offering short-term or temporary Internet access    (such as coffee shops), it is common to start new connections in a    captive-portal mode.  This highly restricts what the customer can do    until the customer has authenticated.

   This document describes a DHCP option (and a Router Advertisement    (RA) extension) to inform clients that they are behind some sort of    captive-portal device and that they will need to authenticate to get    Internet access.  It is not a full solution to address all of the    issues that clients may have with captive portals; it is designed to    be used in larger solutions.  The method of authenticating to and    interacting with the captive portal is out of scope for this    document.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7710.

Kumari, et al.               Standards Track                    [Page 1]
 RFC 7710                   DHCP Captive-Portal             December 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF...