Re: [5gangip] Network tokens draft

Ca By <cb.list6@gmail.com> Fri, 10 July 2020 17:16 UTC

Return-Path: <cb.list6@gmail.com>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA583A00E0 for <5gangip@ietfa.amsl.com>; Fri, 10 Jul 2020 10:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 mfrg4pC1tvRG for <5gangip@ietfa.amsl.com>; Fri, 10 Jul 2020 10:16:02 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 C97B93A00C9 for <5gangip@ietf.org>; Fri, 10 Jul 2020 10:15:56 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id q74so6835658iod.1 for <5gangip@ietf.org>; Fri, 10 Jul 2020 10:15:56 -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=qfKSShALjQdhZHj2XcQkebm6O8xvfiyp/TntRBACghU=; b=pVaNalzSegmaGs3Jsx1xdxrpNUMrxCgm/YAaSpfIbH6ke3ck/vSBC2Z0fH8hKLv2KZ ICis1pkeKbkCqO6JMrMyTmRzxhnE/ojAGniM52U7pFXRiRT3eM+DVrNOpbARuu2vzF08 fIY0oxClnAI8UB4i+h04bcRUQFGSgb1dOe1as+DUqsmPowq8quKwVEA9IzgbtjFT10HV lGuCa+IS628iPnxYoAu7gjDKIocNyLub7xrsfyGoPe826MHWqYv9hrC3fmVO6+Q1Bul3 6UOI25MpxvZGXR3kXBponkwaM3zyb94pv9q0mDDxHR9YP8vSJix2LirmefirdTqClkZu lPFQ==
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=qfKSShALjQdhZHj2XcQkebm6O8xvfiyp/TntRBACghU=; b=sXZUB/0U5+dU2ySSyjT9ltXVN++pGXzUZ6/t111SU5XIHg0JwvXQaHDFF1A6HK82+W y5KkJrVovZRJx5jdK3znc4CPoy609QUzA6Ro3dFUrPw5mM0CuDZYjTPkHu/6Mv1sMYcE TrV3/A5wschUvjrz0cstu6dejLgkPwb13fqY3aomSrWClIFmKgavjJRELlJNTROtYjqV r3SHslwoTg0RSj972b62NJOD2JOQRJAwhyFNkjJgcjHPobIQt4XIMAKiuOMxLudJZ31F +xzUFUY02kZ/jvwyfH5kf9XCpS/5xdtGB24NJO0dryo4zalLJfseJgPKDTx828QUFxLX ApRw==
X-Gm-Message-State: AOAM533PKrRCJ9tEcdIY1Yt7qntNdd4LsHjfRxG+iQLKrfVizrnsA+iW U/Dm+tZ/D1MfMCz/oGGAnx2VusuInYMjmj8IWmhonA==
X-Google-Smtp-Source: ABdhPJzMMV7+uYQFnZnuE/PgLeuVc0OOyiikURpECl8vGq+UxlFRENq0HlMn3TiRk2jXBNuXbuVuR6ke3AQz7Z0y4gA=
X-Received: by 2002:a6b:2c1:: with SMTP id 184mr47815322ioc.167.1594401355572; Fri, 10 Jul 2020 10:15:55 -0700 (PDT)
MIME-Version: 1.0
References: <CALx6S37Qu_Gj166u5mS4=EDrGr-xSpjYhsFOopGrWcNRSHY7jA@mail.gmail.com> <kcgfqrcm.279044f8-05de-4fa2-961b-667288c328c4@we.are.superhuman.com> <kcggtx4g.89bb9049-b123-4718-8ce0-9097cfa918cd@we.are.superhuman.com>
In-Reply-To: <kcggtx4g.89bb9049-b123-4718-8ce0-9097cfa918cd@we.are.superhuman.com>
From: Ca By <cb.list6@gmail.com>
Date: Fri, 10 Jul 2020 10:15:44 -0700
Message-ID: <CAD6AjGQPepqZF6OYURL4V2EVUh3m_nKy8nfcoL7fzsbjZ9vAKg@mail.gmail.com>
To: Yiannis Yiakoumis <yiannis@selfienetworks.com>
Cc: 5GANGIP <5gangip@ietf.org>, Tom Herbert <tom@herbertland.com>
Content-Type: multipart/alternative; boundary="0000000000006dae7505aa197e17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/2B34G1s1j5PSFC00bQTM_5lggKg>
Subject: Re: [5gangip] Network tokens draft
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2020 17:16:08 -0000

On Fri, Jul 10, 2020 at 10:03 AM Yiannis Yiakoumis <
yiannis@selfienetworks.com> wrote:

> "In mobile, the the bearer is a bit of a virtual circuit.  Each UE has one
> or more bearers which are assigned an e2e qos policy.  Your cases for
> tokens would be stronger if you could show how tokens overcome a defined
> challenge that is not solved today.  It is important for credibility to
> demonstrate knowledge of the existing approach … otherwise the suggestion
> appears out of context"
>
> We are actually building a prototype that combines tokens with a dedicated
> bearer for an LTE network, and provides E2E QoS both at uplink and
> downlink. Implementation happens at https://github.com/network-tokens/ .
> Happy to share more details if you are interested.
>
>
> Y.
>

But why is this better than the existing bearer / pcrf model?

What problem are you solving that is novel or better than the existing
approach?

Just saying your model is a great is not helpful.


>
> =====================
> Yiannis Yiakoumis
> Co-Founder & CEO
> https://selfienetworks.com | +1-650-644-7857
>
>
> On Fri, Jul 10, 2020 at 9:35 AM, Yiannis Yiakoumis <
> yiannis@selfienetworks.com> wrote:
>
>> subscribed late and can't reply inline to follow-up comments. Short
>> response to Ca By's point on whether the network trusts the UE.
>>
>> "A fundamental principle of mobile qos is that you do not trust the UE, as
>> it can be compromised to make all traffic high priority. Only the network
>> can reliably and securely allocate resources based on policy."
>>
>> The basic architecture for network tokens is agnostic on the trust
>> relationships between UE, app provider, network and server. It provides
>> mechanisms to encrypt/sign a token, and metadata to prevent replay and
>> spoofing attacks so that operators can adjust it to the appropriate trust
>> model. It borrows a lot from the ideas implemented in JWT, CWT and OAUTH2.
>>
>> Yiannis
>>
>>
>>
>> =====================
>> Yiannis Yiakoumis
>> Co-Founder & CEO
>> https://selfienetworks.com | +1-650-644-7857
>>
>>
>> On Thu, Jul 09, 2020 at 10:00 AM, Tom Herbert <tom@herbertland.com>
>> wrote:
>>
>>> This is a draft on "Network Tokens" which is of relevance to facilitate
>>> fine grained QoS in 5G networks.
>>>
>>> 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
>>>
>>
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>