IETF Logo Mail Archive

Re: [Captive-portals] RFC 8952 on Captive Portal Architecture

Erik Kline <ek.ietf@gmail.com> Mon, 07 December 2020 06:27 UTC

Return-Path: <ek.ietf@gmail.com>
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 3BE2E3A109A for <captive-portals@ietfa.amsl.com>; Sun, 6 Dec 2020 22:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 G-NB7vagmMv8 for <captive-portals@ietfa.amsl.com>; Sun, 6 Dec 2020 22:27:07 -0800 (PST)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 847473A1093 for <captive-portals@ietf.org>; Sun, 6 Dec 2020 22:27:07 -0800 (PST)
Received: by mail-ot1-x335.google.com with SMTP id o11so8858471ote.4 for <captive-portals@ietf.org>; Sun, 06 Dec 2020 22:27:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IUbCoRYXNIMG6wSoVm9HI44pWvral7onSHP5EG6xS+o=; b=Ep9x562smtk2/KBTGCYHrygY455wbvVV4YhCxKCZn0OHDyJwLV0oAxzNf0mEkZMptN hx9GZW9WM16zwzCMLZspM0chblDC2aYgdXpm6FbOuD/pBXrS/jGV4iLYxTBAGkmWlRUG /1eynhGMxQd+l0XJB2LRZ3fDoX5CxDWclm8wyFT1eWav0aauwXRsVwSVXR9ge8ZBJgzX a/ymQlutk5qs3MdJ1DtLEzCET6ZPkTbD/oqhgvb7v4gxhP6k+bifVR9wV+dBbaHDPepz nCm/sB8CfisJrxUUalqFDoJ2is/F/8DC6OuPbD2srdJd0kBnFF5LBKeJ9vJDDpuogdcI 8jhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IUbCoRYXNIMG6wSoVm9HI44pWvral7onSHP5EG6xS+o=; b=MyhK37KoHFUSkmheOklDLsDjz6cKFCbKWA7F4rDgt2ySl7xUHvkZdJJ5LS+qizJxsI MnIUjK0IxOOlcz3bq5wsLOgkl0/jZzjjNDYyVeD02jy+iezTUlNlP+zDrlKgZ/rXdIN2 zwjImR2/2BXv+r6S5eO1bm+S5pxjPisdV7dzXWyzfVkTE4/CYjbyIQrRU+bhXn7mSZWg Q4LJC/ckdQxCwEnQoHxRFG3q8s9vOL/sVCD1gbgHFzdavdhIxkZMefCsbbiRyelO7/pX T3JhOwRYS9uEXJ9yyDyDf4SkV0A+FEBLSQnE3Lob3gAADlQ4K8Q4Fx+9MiRHiN2WbcQh gUeA==
X-Gm-Message-State: AOAM533ezUAyJkaUD6AWNiJcKICsCiX8aIjn2zRJWN8nbASolwk2Xkc3 goomADE8XB0STjp+RThIaX/vDG2hDoNba9ueWM2WsJeNsN0=
X-Google-Smtp-Source: ABdhPJzkEXipCjVfnlCKu3m2vo915FamrwNvkFXXUpjfzp66uQHsMEfU3lQ1S+FWAdvaJ2LDSWx6aWQi3xAr1wuzuBM=
X-Received: by 2002:a9d:62cb:: with SMTP id z11mr11948878otk.191.1607322426417; Sun, 06 Dec 2020 22:27:06 -0800 (PST)
MIME-Version: 1.0
References: <20201201025124.1C1F3F40719@rfc-editor.org> <92b3aaaa-68a2-4d58-a935-d6815b9be3e1@www.fastmail.com>
In-Reply-To: <92b3aaaa-68a2-4d58-a935-d6815b9be3e1@www.fastmail.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Sun, 06 Dec 2020 22:26:55 -0800
Message-ID: <CAMGpriU++wpKSJF7vcLuSUS0M36QYnWrSxhYeruheBWFiFTDWg@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: captive-portals <captive-portals@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/1ZjlJrIfEuTJ_gv7cHhiafxXX58>
Subject: Re: [Captive-portals] RFC 8952 on Captive Portal Architecture
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: Mon, 07 Dec 2020 06:27:10 -0000

Well done, all!

I look forward to seeing some implementations in the future.  When we
can all meet again in person we'll see if we can retry the capport
experiment on the IETF SSIDs.

On Sun, Dec 6, 2020 at 4:45 PM Martin Thomson <mt@lowentropy.net> wrote:
>
> Hey everyone,
>
> Join me in thanking the editors of the new RFC.  This was good work.
>
> I'll be talking to Barry now about formally closing the group.  We'll leave this list open in case people want to continue to discuss new work on this topic.
>
> On Tue, Dec 1, 2020, at 13:51, rfc-editor@rfc-editor.org wrote:
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >         RFC 8952
> >
> >         Title:      Captive Portal Architecture
> >         Author:     K. Larose,
> >                     D. Dolson,
> >                     H. Liu
> >         Status:     Informational
> >         Stream:     IETF
> >         Date:       November 2020
> >         Mailbox:    kyle@agilicus.com,
> >                     ddolson@acm.org,
> >                     liucougar@google.com
> >         Pages:      19
> >         Updates/Obsoletes/SeeAlso:   None
> >
> >         I-D Tag:    draft-ietf-capport-architecture-10.txt
> >
> >         URL:        https://www.rfc-editor.org/info/rfc8952
> >
> >         DOI:        10.17487/RFC8952
> >
> > This document describes a captive portal architecture. Network
> > provisioning protocols such as DHCP or Router Advertisements (RAs),
> > an optional signaling protocol, and an HTTP API are used to provide
> > the solution.
> >
> > This document is a product of the Captive Portal Interaction Working
> > Group of the IETF.
> >
> >
> > INFORMATIONAL: This memo provides information for the Internet community.
> > It does not specify an Internet standard of any kind. 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
> >
> >
> > _______________________________________________
> > Captive-portals mailing list
> > Captive-portals@ietf.org
> > https://www.ietf.org/mailman/listinfo/captive-portals
> >
>
> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals

v2.23.0 | Report a Bug | By Email