Re: [Captive-portals] Review of draft-wkumari-capport-icmp-unreach-01

David Bird <dbird@google.com> Sun, 02 April 2017 00:18 UTC

Return-Path: <dbird@google.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 D3E9B1293F4 for <captive-portals@ietfa.amsl.com>; Sat, 1 Apr 2017 17:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 be1hBakjY61V for <captive-portals@ietfa.amsl.com>; Sat, 1 Apr 2017 17:18:47 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 D56051274D0 for <captive-portals@ietf.org>; Sat, 1 Apr 2017 17:18:46 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id i34so90157861qtc.0 for <captive-portals@ietf.org>; Sat, 01 Apr 2017 17:18:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bokpY+S3tpnFvVauEJ61iUcm0XtCLMVjVDCrw8Mgjpw=; b=CJNNtSvBE+mYu+Sxf/CvZvdw/3zdZC6LGYB6YbD2vbfNzSdmSMOBoGfJ7xrUCTSRfY bDDJtkbDbHB6iX6gUNhzsc8kFg/25DQbZrC4HgFlDC5VjngTYgt3EvUXPUPqT2TDHBa1 o5SlRDeU2MpDQal6RIhK8sjpcisWlSgU9G3iO5/TWDPW/cxr79wGO24Pd+YDfKgZ/5jg 4UWkCGIfadqaSyHt4/gM6OQMV4YWABfDdzrYN3EiesCXcc1qr6QS5AqG8j8rQbwqngof zTdcakebhEc3uP9lYHW1OgfWDL6l5cT4BADBkF/RM1sVICUkNWFu5HHuxHiGHdcCvPCU CrTw==
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; bh=bokpY+S3tpnFvVauEJ61iUcm0XtCLMVjVDCrw8Mgjpw=; b=J6NE9WPPfb86+PVcb/BCdprgh74/L592Wjw0sszq4FRhuFPex3XPrK8W9legmlNM4O YRjspE0Wrs9i+UfXDtQyvMM8VqFzycShMNi3mY/+qf3/WX6hjWwlhPYLEE4+e36EnvZJ gfagKMaElqb58izpnyisHYqd84OkOzPKY9QO7SyEBowzWRFlOrQH/KCk6tkgL+TX16PB 5D+CwtxA93R0pYmNplcVy0Pn6XQZJ4JU1Q0HxZ5LJaqw34lx2+fswBflpsEDYMufK4O0 hj/6Kp39q7HQbvljN56Cm+2KzIZeZpwv5C3TSjWQbDtaHBt5AO7mfqmu5iUW40hFxB7B QlCA==
X-Gm-Message-State: AFeK/H1pzZruwaoNxLH58wARbPzDHXV73RvJMK2d3We9Tkie/0GtfU0VbduLkzXU7sSWLk55u5wfi4cnrDH8ZD/G
X-Received: by 10.237.57.164 with SMTP id m33mr10703813qte.293.1491092325812; Sat, 01 Apr 2017 17:18:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.128.233 with HTTP; Sat, 1 Apr 2017 17:18:45 -0700 (PDT)
In-Reply-To: <CABkgnnXkDSnn2C3cFtdcsX+chDMqnbZO9t5pp4dVMaVLQPXAig@mail.gmail.com>
References: <CABkgnnXkDSnn2C3cFtdcsX+chDMqnbZO9t5pp4dVMaVLQPXAig@mail.gmail.com>
From: David Bird <dbird@google.com>
Date: Sat, 01 Apr 2017 17:18:45 -0700
Message-ID: <CADo9JyXScL4sDtx13pPAanfAoBj0mE4f9D-pGRXDcmKqPz4K+Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: captive-portals@ietf.org, draft-wkumari-capport-icmp-unreach@ietf.org
Content-Type: multipart/alternative; boundary="001a1141030668c6ba054c23fc4c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/oQzZqRVJpT8WSqAzmUFCDFUdedw>
Subject: Re: [Captive-portals] Review of draft-wkumari-capport-icmp-unreach-01
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: Sun, 02 Apr 2017 00:18:49 -0000

I've updated the draft to -02 - sorry for not doing so sooner.

Contributors (and co-authors) welcome!


On Sat, Apr 1, 2017 at 1:40 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> (As a contributor only.)
>
> David, Warren,
>
> Looking at this draft, I think that there are a few fairly major
> changes that this could benefit from.
>
> # Extension payload
>
> The presence of the extension is sufficient signaling for this channel.
>
> If we accept that there will be a protocol for asking the portal for
> basic information about connectivity, the UE/device/etc can query that
> interface for expiration time.
>
> The warning bit seems dangerous in this context given that it
> establishes a non-backwards-compatible behaviour.  To an entity that
> doesn't understand this extension, ICMP Unreachable means that the
> packet was not forwarded.  I don't think that an extension can safely
> change this.
>
> The one obvious caveat for this comment is if we determine that RFC
> 7710 is insufficient for advertisement of the captive portal URL.  In
> that case, we might consider adding the URL to the ICMP message.  I
> don't see any evidence that this is necessary yet, and that would
> compound the next issue, but it's something to consider.
>
> # Security considerations
>
> There is a fairly direct path between this message and a user visiting
> the site identified.  Now, it is well-accepted that it is easy to
> cause a user to visit any site, but nonetheless this needs to be
> discussed.  We can also offer some suggestions for reducing the use of
> this message by arbitrary endpoints.  For example, a device that
> receives this message might not act immediately, but instead trigger
> portal detection routines before opening a browser.  Those routines
> might involve sending more packets and looking for more ICMP
> unreachable packets.
>
> For this reason, I think that we should mandate the use of RFC 4884
> and a minimum size for the echo of the dropped packet.
>