Re: Network Tokens and HBH option

Erik Kline <ek.ietf@gmail.com> Mon, 13 July 2020 05:42 UTC

Return-Path: <ek.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E883A0D3A for <ipv6@ietfa.amsl.com>; Sun, 12 Jul 2020 22:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 H5D77VGYnZ4m for <ipv6@ietfa.amsl.com>; Sun, 12 Jul 2020 22:42:19 -0700 (PDT)
Received: from mail-oo1-xc33.google.com (mail-oo1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (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 DC4A63A0D37 for <6man@ietf.org>; Sun, 12 Jul 2020 22:42:18 -0700 (PDT)
Received: by mail-oo1-xc33.google.com with SMTP id p26so2129905oos.7 for <6man@ietf.org>; Sun, 12 Jul 2020 22:42:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=e++E1YmS68atCFSA42xE85wAb0SHN8JUIvw1sw9EF4c=; b=uKsr/UE5SzWebsVyPLv2BSCzPQokRgdSEdO6KxQhTgNkAcqPAjok49t1XspDyu9PiQ bxzgef1jtWCD0KAWJ7z62yERD3SnrH46reXDnE2cXnL3X/T6RmFI9MqZ4/zc34v+RCTN /ArMvXgB2x4DpRa6KaLaoU9rUbGPSPdeB1h5xgGIYCh+Wf4cO9VTJ7g4DAz3tXn+Qrhz qfgQCXveedw5kEJdFdj2f4ObAhpVJTX9b4qNoqgRyZUy2PYDaL3aceAtUqGawXqVTys2 sxdL8GGwABlG1glz2/XAtJSvv6+u3WoY3qSxns/QyainjO8X6hPViWnZEWdbnn0//yXW BwAA==
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:from:date :message-id:subject:to:cc; bh=e++E1YmS68atCFSA42xE85wAb0SHN8JUIvw1sw9EF4c=; b=hdgu8yvGAxyv43iANKJKtDixExuXi/CJxs7C7JhgxlwEmHBSux8VGNsruDI2blH6m+ XHyyDXcZux4Kz1dIHv6I3E8S5jh7uacMQYLlkpFfMSVIM/tOUEF3VVkMJziohyHvVvcY bMfltW8MVGkhIaFDgs2gOAtU7Mexa0rQZt2HNtqvOwvx+pcpZJIQGGjpKXOXSUpkcLPE krbpu3r60Xe9SzPV/NcGbc8PpGmkBo38LqfwknVwgLqmKJn5lo1mVcjwZWf0VolFbW0W HgSl/uzfiQqp94chA73XMj9kYhQ6gretRTafu50z0fX4J1PQZpyVYi2cJdvAA+wHAJXf zsWw==
X-Gm-Message-State: AOAM5315cgOos1+27tk/P+cqIL1aXobtRRkRCS0kgTjHu4kgI1zrGGy7 sdrDsYIZ76SoDzFj1bygAz7KxVWlSumSdnNPodk=
X-Google-Smtp-Source: ABdhPJyAkrmpO22HUX2E1ovTGsfX+Vfp5jqfSy6BIFY9UUkXNN2FCFgnbA/xVtsWC014e5frLDGCwqmkpiZ1pChYvl4=
X-Received: by 2002:a4a:2a0e:: with SMTP id k14mr4762896oof.67.1594618938173; Sun, 12 Jul 2020 22:42:18 -0700 (PDT)
MIME-Version: 1.0
References: <CALx6S35sXX6J75dzQH=hN7pC5=9wZP=o6SqOMpivGPtOdo+YNQ@mail.gmail.com>
In-Reply-To: <CALx6S35sXX6J75dzQH=hN7pC5=9wZP=o6SqOMpivGPtOdo+YNQ@mail.gmail.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Sun, 12 Jul 2020 22:42:07 -0700
Message-ID: <CAMGpriXJK7wGgaC01k=2oCMJR28XxrN7bgmqPcdxiayVSjS0uA@mail.gmail.com>
Subject: Re: Network Tokens and HBH option
To: Tom Herbert <tom@herbertland.com>
Cc: 6MAN <6man@ietf.org>, Yiannis Yiakoumis <yiannis@selfienetworks.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HP0lfCPoIc8B1eIEW8gd8HOQnBI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2020 05:42:20 -0000

Is this APN6 w/ an added authentication element?

I maybe have not fully digested everything, but there seems to me to
be some cause for concern about abuse.  For example, what's to keep an
enormous incumbent mobile operator from mandating the use of this on
devices permitted to attach to their network?  Seems like there could
be concerning aspects for users/OSes that are hidden behind the
promise of things like zero rating.

On Fri, Jul 10, 2020 at 8:54 AM Tom Herbert <tom@herbertland.com> wrote:
>
> 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. A primary mechanism to carry the
> signaling is expected to be a Hop-by-Hop option.
>
> 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
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------