CAPPORT Architecture
draft-larose-capport-architecture-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-09
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                K. Larose
Internet-Draft                                                 D. Dolson
Intended status: Informational                                  Sandvine
Expires: September 10, 2017                                March 9, 2017

                          CAPPORT Architecture
                  draft-larose-capport-architecture-00

Abstract

   This document aims to document concensus on the CAPPORT architecture.
   DHCP, ICMP, and an HTTP API are used to provide the solution.

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 http://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."

   This Internet-Draft will expire on September 10, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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.

Larose & Dolson        Expires September 10, 2017               [Page 1]
Internet-Draft            CAPPORT Architecture                March 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Components  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  User Equipment  . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  DHCP Server . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Captive Portal API Server . . . . . . . . . . . . . . . .   4
     2.4.  Captive Portal Enforcement  . . . . . . . . . . . . . . .   5
     2.5.  ICMP/ICMP6  . . . . . . . . . . . . . . . . . . . . . . .   5
     2.6.  Component Diagram . . . . . . . . . . . . . . . . . . . .   6
   3.  Solution Workflow . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Initial Connection  . . . . . . . . . . . . . . . . . . .   7
     3.2.  Connection About to Expire  . . . . . . . . . . . . . . .   8
     3.3.  Connection expired  . . . . . . . . . . . . . . . . . . .   8
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
     5.1.  Authenticated APIs  . . . . . . . . . . . . . . . . . . .   9
     5.2.  Risk of Nuisance Captive Portal . . . . . . . . . . . . .   9
     5.3.  User Options  . . . . . . . . . . . . . . . . . . . . . .   9
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Problems with captive portals have been described in
   [I-D.nottingham-capport-problem].

   This document standardizes an architecture for implementing captive
   portals that provides tools for addressing most of those problems.

   The architecture also attempts to enable IoT devices, in particular
   devices without user interfaces, to navigate a captive portal.

   The architecture uses the following mechanisms:

   o  DHCP/DHCP6 providing end-user devices with a URI in the Captive-
      Portal Router Advertisement option [RFC7710].  This URI is an API
      that the end-user devices access for information about what is
      required to escape captivity.

   o  Notifying end-user devices of captivity with ICMP/ICMP6
      "unreachable" messages.  This notification can work with any
      Internet protocol, not just clear-text HTTP.  This notification
      does not carry the portal URI, rather triggers the DHCP-

Larose & Dolson        Expires September 10, 2017               [Page 2]
Show full document text