Re: [Captive-portals] Fwd: [tsvwg] Network tokens draft

Erik Kline <ek@loon.com> Sun, 12 July 2020 04:48 UTC

Return-Path: <ek@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 9CE713A0CEB for <captive-portals@ietfa.amsl.com>; Sat, 11 Jul 2020 21:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.25
X-Spam-Level:
X-Spam-Status: No, score=-9.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=loon.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 BqICpAkmrS-o for <captive-portals@ietfa.amsl.com>; Sat, 11 Jul 2020 21:48:00 -0700 (PDT)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (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 233E93A0CEA for <captive-portals@ietf.org>; Sat, 11 Jul 2020 21:47:59 -0700 (PDT)
Received: by mail-vs1-xe33.google.com with SMTP id b77so4999914vsd.8 for <captive-portals@ietf.org>; Sat, 11 Jul 2020 21:47:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=loon.com; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=JS192WqFoW1Ma1ypm1CUg4MEwtr+khPq9wVVitrQkkY=; b=E3H2VlMrQnxIpkUeCcYA81BHVVI+8qV2OifyspxI7trNiMUGqyEfgMBiCa/D3kop9X lTubGfzAXaCZ+qYADfNA7NTM3klyPN3sRTdjm60sc0v9wxGwHuBcmdid6DH4szDIJsYq 1AAs8f0QJQzlEkMh57C4NuJPK80n9gYRQqppc=
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:reply-to :from:date:message-id:subject:to:cc; bh=JS192WqFoW1Ma1ypm1CUg4MEwtr+khPq9wVVitrQkkY=; b=KeS4lxqZsf0l12QKZJm82MSDIGiGX/DRkAi5Hla59rH0vLoQAevjcRNlauCTj6ctZI KOMJdS6jSEFY5thNToTfchzsloTKOv7qBu5zIzgVPat3qz6/KkTqJYVA0KDaJwQ347xx sb6yJ5NdOu1jhS3xlXNI5Dzk1dmeqiJrIOWi3i6/EMKU+LoiELRcO/mU+bnGutjLhroa A1rsRu9mCS728QAlfh+agAlEZJDhpc9YFidggtUKpq7eHcwnI1Ex403+3XJC0GGD2hhZ tpDeJajBYmPE9P9J0FwX8ACN+FS35BXTnP8ZS/kypUnzGHLm4p/Lb+58y3hscEu3T6xD OzBw==
X-Gm-Message-State: AOAM533GTzsO4EizKIp/03zAghzVNaX1m4rhgcqEPBDyajXB0rkiI8La zxYFrs4w6WRGWL6N0j0ZZ299MQZPxGEE6WozSKjxFA==
X-Google-Smtp-Source: ABdhPJw8zf4IxrjwpZBrGK1y0PlZW1eH5EXODnqIXZChq3NEWTXZmgDACVlcVzM8ZCLqr9hioc2V7UxeSIwQX1eSEOo=
X-Received: by 2002:a67:ec0f:: with SMTP id d15mr45789651vso.121.1594529278399; Sat, 11 Jul 2020 21:47:58 -0700 (PDT)
MIME-Version: 1.0
References: <CALx6S36tUjT7sEAbc0ObDaLQHg_fadTXFmL99biBxzS=rQchLA@mail.gmail.com> <CAMFWN9k46=eajzeBJR9xEGQXt3_8_L+ibfrSgu3UvgODtXSdTw@mail.gmail.com>
In-Reply-To: <CAMFWN9k46=eajzeBJR9xEGQXt3_8_L+ibfrSgu3UvgODtXSdTw@mail.gmail.com>
Reply-To: ek@loon.com
From: Erik Kline <ek@loon.com>
Date: Sat, 11 Jul 2020 21:47:47 -0700
Message-ID: <CAAedzxqP+MFLCWmH=BpE6bfTruN4DZiex-ThurUQ9XSNsbU9eQ@mail.gmail.com>
To: Kyle Larose <eomereadig@gmail.com>
Cc: captive-portals <captive-portals@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/hKqc_pz2OKLSiYTYF8OqKtYhHJ4>
Subject: Re: [Captive-portals] Fwd: [tsvwg] Network tokens draft
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: Sun, 12 Jul 2020 04:48:02 -0000

<no hats>

I fail to see how this is good for general purpose nodes/user devices.
This seems like another way to do the "self-DPI" work that was
shopping around for a home a little while ago.  I mean, it all just
seems like something that in the end can be abused to limit client
behaviour, dressed up as giving users new services and options ("you
don't implement tokens/have any tokens in your packets? too bad for
you").

On Fri, Jul 10, 2020 at 9:01 AM Kyle Larose <eomereadig@gmail.com> wrote:
>
> I have only skimmed this, so it may not be appropriate, but I wonder if this could be a starting point for the captive portal signal. Could this address some of the concerns we had with ICMP?
>
> ---------- Forwarded message ---------
> From: Tom Herbert <tom@herbertland.com>
> Date: Fri, Jul 10, 2020 at 11:52 AM
> Subject: [tsvwg] Network tokens draft
> To: tsvwg <tsvwg@ietf.org>
> Cc: Yiannis Yiakoumis <yiannis@selfienetworks.com>
>
>
> Hello,
>
> This is a draft on "Network Tokens" which is a form of host-to-network
> signaling for the purposes of providing a highly granular network
> services and QoS to applications.
>
> https://tools.ietf.org/html/draft-yiakoumis-network-tokens-01
>
> There is also a mailing list in
> https://www.ietf.org/mailman/listinfo/network-tokens
>
> We are planning to present in tsvwg and app aware networking and
> possibly have a side meeting on this topic in IETF108.
>
> Thanks,
> Tom
>
> _______________________________________________
> Captive-portals mailing list
> Captive-portals@ietf.org
> https://www.ietf.org/mailman/listinfo/captive-portals