Re: [5gangip] Network tokens draft

Tom Herbert <tom@quantonium.net> Fri, 10 July 2020 17:22 UTC

Return-Path: <tom@quantonium.net>
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 0052D3A00C3 for <5gangip@ietfa.amsl.com>; Fri, 10 Jul 2020 10:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=quantonium-net.20150623.gappssmtp.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 x4TENsLB9Q6c for <5gangip@ietfa.amsl.com>; Fri, 10 Jul 2020 10:22:35 -0700 (PDT)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (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 CA4BE3A00B3 for <5gangip@ietf.org>; Fri, 10 Jul 2020 10:22:34 -0700 (PDT)
Received: by mail-ej1-x630.google.com with SMTP id ga4so6892881ejb.11 for <5gangip@ietf.org>; Fri, 10 Jul 2020 10:22:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fOl5r0kfEd1UaRv2oJSU/a9jLauLwJRG7kTWkozCCUs=; b=pmiarFYjiVEOZwO+Dn6YMVE/Anw5+KYHIwMEjTa5f8sqOKUgsg/mlm8FB584Dre0Gt gkJNyJPgA51ueGcUYWMF2HxSuT5VypaKhdJyaIJy7EzsUH8plcXBbMX2C5TD2Ot8JX3X PRTF0D+AoKj8lJD7Ze1irdOWAW4VddS266F37JCJCqxWeWZPpIMS0ZjOComTjOnJxyYp nAwt9FFASAFM0UXMGMQ2m8swOwoRvGgpu8qcLSTFFdZnp7O4yEf2KSvaYPoUX3RgxIYX w4YbtWPAkqv9wR75WJyLu1nJwusLA6BmXwvSH4aqRk9UgLTXtqfUW65mP2DaeiKAM8KN VvkQ==
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=fOl5r0kfEd1UaRv2oJSU/a9jLauLwJRG7kTWkozCCUs=; b=VHm+ufInN4/IsWNNqsEijtFTcL71Rh7cpEmtByiGzCUeD6QGXvSgHrTR4ZQ179X3uu YMKT5oopPkE9bbE00pXnqAKd+9fYxDtsDV4hluqEmzCm/rbiqvrvdaGcaZ9VKp6xLCtu WlwfhKqQlWJyO7/tW/DccyFLQXOxYsLmF5pGlQank90wEmwa5VPn2VGE5LbGkXYZ5UT7 68Adg+E037B/ZLYp451VQYyodRYMXO/eGdNJrQTv/wqgPhNlSHNCzDG4xWZtjpghr7LR oTyoRYENp/2OecRGfrvhlBfTGm+gk+auadop6TDmGGVjVy383rCDYTEIBHzbxSZ5SMzB r/tA==
X-Gm-Message-State: AOAM531AjBdZkI1NeyAI15PntmThGIYVjEpwaqAX+t+tS7U5D4BKAv75 tJkGaSEBYm2OVD3t/hgzAvN2HbF+82Ms1KG0U59mzQ==
X-Google-Smtp-Source: ABdhPJyqHSsq6lhEXCENKA8iPjVKqLNN+rFdDsHo+nLhagKt1HOIl1ACg/X98fleim3d+CQZ9U0coxWfvWa1rfG+JDE=
X-Received: by 2002:a17:906:9716:: with SMTP id k22mr43552738ejx.200.1594401752717; Fri, 10 Jul 2020 10:22:32 -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> <CAD6AjGQPepqZF6OYURL4V2EVUh3m_nKy8nfcoL7fzsbjZ9vAKg@mail.gmail.com>
In-Reply-To: <CAD6AjGQPepqZF6OYURL4V2EVUh3m_nKy8nfcoL7fzsbjZ9vAKg@mail.gmail.com>
From: Tom Herbert <tom@quantonium.net>
Date: Fri, 10 Jul 2020 10:22:21 -0700
Message-ID: <CAPDqMepwVAWG4nMD_Bxb+k+6ywsfytWrqKRZycq5hOiiv==Vmg@mail.gmail.com>
To: Ca By <cb.list6@gmail.com>
Cc: Yiannis Yiakoumis <yiannis@selfienetworks.com>, 5GANGIP <5gangip@ietf.org>, Tom Herbert <tom@herbertland.com>
Content-Type: multipart/alternative; boundary="00000000000019b24205aa199694"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/adMUSz74aSk_l9ZIs4MR1EUefgg>
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:22:37 -0000

On Fri, Jul 10, 2020 at 10:16 AM Ca By <cb.list6@gmail.com> wrote:

>
>
> 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/ <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.
>

One advantage is that it moves the solution into the IP layer so it can be
used with a broader range of technologies. For instance, when a phone
connects to a Wifi router the application uses the same interface to get
tokens from that provider.

Tom


>
>
>>
>> =====================
>> 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 <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
>>
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>