Captive-Portal Identification in DHCP / RA
draft-ietf-capport-rfc7710bis-03

Document Type Active Internet-Draft (capport WG)
Last updated 2020-03-31 (latest revision 2020-03-30)
Replaces draft-ekwk-capport-rfc7710bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd Martin Thomson
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Martin Thomson <mt@lowentropy.net>
Network Working Group                                          W. Kumari
Internet-Draft                                                    Google
Obsoletes: 7710 (if approved)                                   E. Kline
Intended status: Standards Track                                    Loon
Expires: October 1, 2020                                  March 30, 2020

               Captive-Portal Identification in DHCP / RA
                    draft-ietf-capport-rfc7710bis-03

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 enforcement 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 of this document.

   RFC7710 used DHCP code point 160.  Due to a conflict, this document
   specifies TBD.

   [ This document is being collaborated on in Github at:
   https://github.com/capport-wg/7710bis.  The most recent version of
   the document, open issues, etc should all be available here.  The
   authors (gratefully) accept pull requests.  Text in square brackets
   will be removed before publication. ]

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any

Kumari & Kline           Expires October 1, 2020                [Page 1]
Internet-Draft             DHCP Captive-Portal                March 2020

   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 1, 2020.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   3
   2.  The Captive-Portal Option . . . . . . . . . . . . . . . . . .   3
     2.1.  IPv4 DHCP Option  . . . . . . . . . . . . . . . . . . . .   4
     2.2.  IPv6 DHCP Option  . . . . . . . . . . . . . . . . . . . .   5
     2.3.  The Captive-Portal IPv6 RA Option . . . . . . . . . . . .   5
   3.  Precedence of API URIs  . . . . . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  IETF params Registration  . . . . . . . . . . . . . . . .   6
       4.1.1.  Registry name: Captive Portal Unrestricted Identifier   6
     4.2.  BOOTP Vendor Extensions and DHCP Options Code Change  . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . .  10
   Appendix B.  Changes from RFC 7710  . . . . . . . . . . . . . . .  10
   Appendix C.  Observations From IETF 106 Network Experiment  . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   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.  Regardless
   of how that mechanism operates, this document provides functionality

Kumari & Kline           Expires October 1, 2020                [Page 2]
Internet-Draft             DHCP Captive-Portal                March 2020
Show full document text