Re: [Captive-portals] Fixing RFC 7710

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 02 March 2018 21:41 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 8D9A812025C for <captive-portals@ietfa.amsl.com>; Fri, 2 Mar 2018 13:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 H6ynA031uyef for <captive-portals@ietfa.amsl.com>; Fri, 2 Mar 2018 13:41:35 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C963F1200E5 for <captive-portals@ietf.org>; Fri, 2 Mar 2018 13:41:35 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2628B20091; Fri, 2 Mar 2018 16:49:29 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7FBD580DC7; Fri, 2 Mar 2018 16:41:34 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Martin Thomson <martin.thomson@gmail.com>
cc: captive-portals@ietf.org, Warren Kumari <warren@kumari.net>, Olafur Gudmundssen <olafur@cloudflare.com>, ebersman-ietf@dragon.net, steve.sheng@icann.org
In-Reply-To: <CABkgnnWJMipRtG-p0EoUXmK3u1c2ab-v4xN3WZfm3XL8s08aZA@mail.gmail.com>
References: <CABkgnnWJMipRtG-p0EoUXmK3u1c2ab-v4xN3WZfm3XL8s08aZA@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 02 Mar 2018 16:41:34 -0500
Message-ID: <25597.1520026894@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/CL2ekkaunZ03VkAvrnF1Z2xIXJM>
Subject: Re: [Captive-portals] Fixing RFC 7710
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 02 Mar 2018 21:41:37 -0000

Martin Thomson <martin.thomson@gmail.com> wrote:
    > We've had a number of discussions in the captive portals group about
    > fixing RFC 7710.

    > Erik and I would like to propose a plan for that work.  We would keep
    > this to addressing the issues that we have identified thus far.
    > Namely:

Hi, so are you considering 7710bis, or a document that just Updates 7710?
7710bis seems excessive to me, unless you think that we have to change the
DHCP/RA option codes in the process.

    > 1. The purpose of the URI is not well defined.  We would reference the
    > capport architecture and API documents for that.  The group would need
    > to decide between: a. point to the API b. point to a login page

Could the API document do the required updates?


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-