[Captive-portals] Fixing RFC 7710
Martin Thomson <martin.thomson@gmail.com> Fri, 02 March 2018 03:58 UTC
Return-Path: <martin.thomson@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 29B78120724 for <captive-portals@ietfa.amsl.com>; Thu, 1 Mar 2018 19:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 kEai11DbSOW6 for <captive-portals@ietfa.amsl.com>; Thu, 1 Mar 2018 19:58:25 -0800 (PST)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 BBE02124D68 for <captive-portals@ietf.org>; Thu, 1 Mar 2018 19:58:25 -0800 (PST)
Received: by mail-io0-x22a.google.com with SMTP id b34so9489441ioj.6 for <captive-portals@ietf.org>; Thu, 01 Mar 2018 19:58:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=QIKhbRkhWKkzOckeoGBC1ev8YJejOFmMYicyl66aHvM=; b=RBzb1bUKOtR61sqlQJ8kOPvkFRdLX44B6f+O/olQ/RG+BLkVKmiTE9zDPBLQLanY54 8WjK1q5M//VVz9aLqON4gcQZWzIBPytWI1cm59NRhi+gtDgd4HfVgYQvarMqOhQxMuLk IUXzPXcu4+1H/h/9/lknEJ6CXwIBTHo1i8URtW9MZfoOZkKrto8je7aV8TdPcLblSjeI wPegfD/nxusRtlNIuEcBpK+boaEwyCGT79RMXXSTJnc+RtWxfso1gny5/0fEnPb1aEEB 8Ihzu3YZoEChi3IRLiaD91EKsWLHyGkTPTObZRyfnZyI6rzRGMGqCBPXEW/NnZxfk43T cs3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QIKhbRkhWKkzOckeoGBC1ev8YJejOFmMYicyl66aHvM=; b=c+22qqr9QAfqgM8QUroxfXG2jvKVDRcZ1unt/Re8WYdI+edN+0POZUsP+1dJW4dzr9 asu6OjjR0QxbrD7Z9qSRK1RsH+hu4q1wpV5k4tB01CDh3CcQ+JTANsNYjWLryODKESAI 6XCJUYrYSzPaN2FQo9v79lE5BpCg2i/CkfNbh725X+BPQhE2k9syHPX7XuzGjrBW7TlV 155T18SL9s1+ahXvQb155bF6FUYfNzBnR8nA9WGZFR586l71DyrzqK8ELsqTAacKOwUQ uRkNaUeVghC6NQTBY6l7fc1zuf1iSlFLakHHkbsxSSwaG4AjzVR2MxsbVsWsBiqihN/A XtHg==
X-Gm-Message-State: APf1xPBHwgkB6tmOBLXW8F3pBrvc804ROQgqonp87ubHMBAqG1AvEqNE V9dxu4W0Bg7LUUuGIG0RbpbFbKuwCQFbiA8C8gZSxw==
X-Google-Smtp-Source: AG47ELuYCIFQqIFAOfXd4RDUMYKV+4csxjIoYb1re1J9+jaZusqSESpkfoBYLZ+1cMujQY/wtMTWa61L/YSOn76Kgxc=
X-Received: by 10.107.59.130 with SMTP id i124mr4843135ioa.129.1519963104916; Thu, 01 Mar 2018 19:58:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.104.199 with HTTP; Thu, 1 Mar 2018 19:58:24 -0800 (PST)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 02 Mar 2018 14:58:24 +1100
Message-ID: <CABkgnnWJMipRtG-p0EoUXmK3u1c2ab-v4xN3WZfm3XL8s08aZA@mail.gmail.com>
To: captive-portals@ietf.org, Warren Kumari <warren@kumari.net>, Olafur Gudmundssen <olafur@cloudflare.com>, ebersman-ietf@dragon.net, steve.sheng@icann.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/YOPtw3OyAqmoZXM60D5nUKdh5fo>
Subject: [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 03:58:27 -0000
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: 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 2. There isn't a clear way to signal that there is no captive portal in the network. It has been suggested that we use a special URL - e.g., urn:ietf:params:capport:unrestricted. Alternatively, we could privilege the empty string, but that doesn't have as clear a signal of intent. 3. RFC 7710 states that the URL SHOULD use an address literal. This works at odds with the idea of using HTTPS. Is there anyone who is willing to take on this work? We aim to start and complete this work in <1 meeting cycle, starting in London. For the authors of RFC 7710, let us know if you have any concerns.
- [Captive-portals] Fixing RFC 7710 Martin Thomson
- Re: [Captive-portals] Fixing RFC 7710 Alexander Roscoe
- Re: [Captive-portals] Fixing RFC 7710 Michael Richardson
- Re: [Captive-portals] Fixing RFC 7710 Ólafur Guðmundsson
- Re: [Captive-portals] Fixing RFC 7710 Warren Kumari
- [Captive-portals] signaling no captive portal Michael Richardson
- Re: [Captive-portals] Fixing RFC 7710 Martin Thomson
- Re: [Captive-portals] Fixing RFC 7710 Martin Thomson
- Re: [Captive-portals] Fixing RFC 7710 Warren Kumari