[Captive-portals] RFC 8908 on Captive Portal API

rfc-editor@rfc-editor.org Tue, 22 September 2020 04:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: captive-portals@ietfa.amsl.com
Delivered-To: captive-portals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49ED13A128F; Mon, 21 Sep 2020 21:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZL_AqN-ZpqYP; Mon, 21 Sep 2020 21:03:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 211483A0D9C; Mon, 21 Sep 2020 21:03:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D13BF40770; Mon, 21 Sep 2020 21:03:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, captive-portals@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200922040326.0D13BF40770@rfc-editor.org>
Date: Mon, 21 Sep 2020 21:03:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/fhHPHhWCLbF3frTyH5o04Lzcz2o>
Subject: [Captive-portals] RFC 8908 on Captive Portal API
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of issues related to captive portals <captive-portals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/captive-portals/>
List-Post: <mailto:captive-portals@ietf.org>
List-Help: <mailto:captive-portals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2020 04:03:34 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8908

        Title:      Captive Portal API 
        Author:     T. Pauly, Ed.,
                    D. Thakore, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2020
        Mailbox:    tpauly@apple.com, 
                    d.thakore@cablelabs.com
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-capport-api-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8908

        DOI:        10.17487/RFC8908

This document describes an HTTP API that allows clients to interact
with a Captive Portal system. With this API, clients can discover how
to get out of captivity and fetch state about their Captive Portal
sessions.

This document is a product of the Captive Portal Interaction Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC