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

Document Type Active Internet-Draft (capport WG)
Last updated 2020-07-14 (latest revision 2020-07-13)
Replaces draft-ekwk-capport-rfc7710bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Martin Thomson
Shepherd write-up Show (last changed 2020-04-20)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Barry Leiba
Send notices to Martin Thomson <mt@lowentropy.net>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
Details
Network Working Group                                          W. Kumari
Internet-Draft                                                    Google
Obsoletes: 7710 (if approved)                                   E. Kline
Updates: 3679 (if approved)                                         Loon
Intended status: Standards Track                           July 13, 2020
Expires: January 14, 2021

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

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 user can do
   until the user has satisfied the captive portal conditions.

   This document describes a DHCPv4 and DHCPv6 option and a Router
   Advertisement (RA) option to inform clients that they are behind some
   sort of captive portal enforcement device, and that they will need to
   satify the Captive Portal conditions 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 one component of a
   standardized approach for hosts to interact with such portals.  While
   this document defines how the network operator may convey the captive
   portal API endpoint to hosts, the specific methods of satisfying and
   interacting with the captive portal are out of scope of this
   document.

   This document replaces [RFC7710].  [RFC7710] used DHCP code point
   160.  Due to a conflict, this document specifies 114.  Consequently,
   this document also updates [RFC3679].

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
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Kumari & Kline          Expires January 14, 2021                [Page 1]
Internet-Draft             DHCP Captive-Portal                 July 2020

   This Internet-Draft will expire on January 14, 2021.

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.  Captive Portal Unrestricted Identifier  . . . . . . . . .   7
     4.2.  BOOTP Vendor Extensions and DHCP Options Code Change  . .   7
     4.3.  Update DHCPv6 and IPv6 ND Options Registries  . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Appendix A.  Changes / Author Notes.  . . . . . . . . . . . . . .  11
   Appendix B.  Changes from RFC 7710  . . . . . . . . . . . . . . .  12
   Appendix C.  Observations From IETF 106 Network Experiment  . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

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
Show full document text