[Captive-portals] I-D Action: draft-ietf-capport-rfc7710bis-11.txt

internet-drafts@ietf.org Mon, 13 July 2020 19:31 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: captive-portals@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: captive-portals@ietf.org
Message-ID: <159466866464.6891.4098038625745928713@ietfa.amsl.com>
Date: Mon, 13 Jul 2020 12:31:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/-3xOUrpCHUkXTFYOgKBO8_XjebU>
Subject: [Captive-portals] I-D Action: draft-ietf-capport-rfc7710bis-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Captive Portal Interaction WG of the IETF.

        Title           : Captive-Portal Identification in DHCP / RA
        Authors         : Warren Kumari
                          Erik Kline
	Filename        : draft-ietf-capport-rfc7710bis-11.txt
	Pages           : 13
	Date            : 2020-07-13

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].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-capport-rfc7710bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-capport-rfc7710bis-11
https://datatracker.ietf.org/doc/html/draft-ietf-capport-rfc7710bis-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-capport-rfc7710bis-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Captive-portals] I-D Action: draft-ietf-capport-… internet-drafts