Re: [Captive-portals] Use Case: "Carrier Grade Captive Portal"

Martin Thomson <martin.thomson@gmail.com> Thu, 01 June 2017 01:07 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 E889512941D for <captive-portals@ietfa.amsl.com>; Wed, 31 May 2017 18:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, 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 wl3vVdI1VRzW for <captive-portals@ietfa.amsl.com>; Wed, 31 May 2017 18:07:51 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 3FC601294A4 for <captive-portals@ietf.org>; Wed, 31 May 2017 18:07:51 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id 99so18229820lfu.1 for <captive-portals@ietf.org>; Wed, 31 May 2017 18:07:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=78tIMDXo0TZ9VWBgpeieSKF5d0OSZ0sZ32PdqibOj/4=; b=czEaNdyGLWvHAcnn3P7quOF3vr/we9CUIPVArdn+nw6LIjPc0Xx0kaCQIFxrnunxXb Offy7Js3bemoStTJNO3ERQ1uyjab0PROTnhnHvxl75sFVyAS1H+yKPSdVYakYI68wAeh g2mOTmtaw5K9QqiJNrWn7xD7WxLiGKx1qXx2jazLrmND0tN2z4OlrOnBPJea58VWJnc8 TfC7G8w2ckN9yNM8lQyK3YYY8w1qo4ITkmjfzRZvXZlq7UHTtP34vHJPdT0TJ1cYdIVs BEbRlPN/TjOIT2BsQYco/aIKJoE0lGeQI3RBQ7PvbgH3ZpSbpd4w4JfXuJnNxguoHZBL CmaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=78tIMDXo0TZ9VWBgpeieSKF5d0OSZ0sZ32PdqibOj/4=; b=iaS+yNIxpcPgh4xBdjAPhhtfkf7BVAwzCbPt8VAKChJGKbvMB5/zL8GnKyE5wyTcOb tekbtazdNOoObyCJES2rWHLPTNyUYGKTt8YlnuY8UbnHe6pJ4eLlXG5hNiHWL8YfhcSi CD8798vmKYBYZjy0n9AJeBWjY40RbAqdgSktServWi34z8kIYTUQMDSPiMiFm2vztmUD Rzmh3G+XqRLWiLExdT/+jt1bGIruJ41jHc1ryZ9gACZ+2WnAKAZ2uZ4W1hf2EAkO69KC I7E1Bb5ifFsKOaEgAxvUmohgSeDaeirxaVQj54eN6Ys2LjvH8jwrJvFzkqTRicvxGR/r mk6w==
X-Gm-Message-State: AODbwcAHnStan98Sqo0LjvjHdaSF1uFOWE++VToSKj/lR+4YeEIPvmzw i1tJJ8MH0QGI6GwBEOGbyFYBchDdJjRh
X-Received: by 10.25.29.82 with SMTP id d79mr9087549lfd.130.1496279269531; Wed, 31 May 2017 18:07:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.8.66 with HTTP; Wed, 31 May 2017 18:07:48 -0700 (PDT)
In-Reply-To: <1BB90528-B35F-43F0-AF18-0215DC735FF0@cable.comcast.com>
References: <201705031442.50683.heiko.folkerts@bsi.bund.de> <E8355113905631478EFF04F5AA706E98705C6C57@wtl-exchp-1.sandvine.com> <CAHw9_iJARf4MUA8nHqHA54jLvJNq-_Vek67A-rjHpSK6vC7r+Q@mail.gmail.com> <1BB90528-B35F-43F0-AF18-0215DC735FF0@cable.comcast.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 01 Jun 2017 11:07:48 +1000
Message-ID: <CABkgnnWT6Xtqyx6pofpNOGa5E1FjJO1gPX1axmmiRaMnzxdoPg@mail.gmail.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: Warren Kumari <warren@kumari.net>, Dave Dolson <ddolson@sandvine.com>, Heiko Folkerts <heiko.folkerts@bsi.bund.de>, "captive-portals@ietf.org" <captive-portals@ietf.org>, "Herzig, Willi" <willi.herzig@bsi.bund.de>, Gunther Nitzsche <gnitzsche@netcologne.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/VcJm-mfrse1LdJiK21qHx_1UAkc>
Subject: Re: [Captive-portals] Use Case: "Carrier Grade Captive Portal"
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: Thu, 01 Jun 2017 01:07:53 -0000

On 1 June 2017 at 08:23, Livingood, Jason <Jason_Livingood@comcast.com> wrote:
> In any case, this is very much in scope IMO – so agree with others here. With the rise of IoT compromises the need for these sorts of notifications will only rise and will be critical to maintaining the security & integrity of the Internet.

Just trying to understand this.  Jason, can you expand on your
assertion that insertion of notices in HTTP messages (I assume
response bodies) is critical to security & integrity?