Re: [5gangip] Network tokens draft

Tom Herbert <tom@herbertland.com> Fri, 10 July 2020 15:25 UTC

Return-Path: <tom@herbertland.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 373783A0E48 for <5gangip@ietfa.amsl.com>; Fri, 10 Jul 2020 08:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=herbertland-com.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 C6p9XDuWqLlj for <5gangip@ietfa.amsl.com>; Fri, 10 Jul 2020 08:25:32 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 5467A3A0E45 for <5gangip@ietf.org>; Fri, 10 Jul 2020 08:25:32 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id b15so4953911edy.7 for <5gangip@ietf.org>; Fri, 10 Jul 2020 08:25:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=lhu/7L8taXSG34HO9sYObL7kTwkEp7yfIVhEeVPkdWA=; b=0FcBpLRbeSPHhJA01G2vteSZo/bgIPR4HuE0DRBJPJNQyFP+1txNFnIi8cxqyxaT0I FFjdgRzCAeZ8TB2+WJ/98r80gY0RxZhbQmClryaLW7lyehNqzK/rLhLiI0F2uQNLmqtJ 2MC1bbalCD4pRD6XuRFqMEGJIz+WqBGlCpL2fRi/XMxqkiPvhzGtLhSbP6FxqtV4j8rG 2wEvqcWWKu2p4M5wPAb22KfmwZ8TCwi0MX2EAqcOY+bK+91PGhMbNusz+He6teCrFjR2 ZqpqPJG9ZdcZ6KaNh3ueKdATlLUL7El4zbdJMs0iy25Z3Ws9CU31NcnhK9XXgilxJfeA LfbQ==
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:content-transfer-encoding; bh=lhu/7L8taXSG34HO9sYObL7kTwkEp7yfIVhEeVPkdWA=; b=VWd/UqNkqvzh9+lumz4oS/R7Ehp+qTD4UHf1BWCR73Hw90WQkXrlXXrrAstXPjFqsE UmpaXjo5wxfDxQrV4imFcgzc4lB6ctC2ZBZWpQ0xuvrhXscrWIx0nf33wLQllG8Grboh aNRzB+jlfTgWVKHnPHICUDgM44XTLTlP6xKd14PvNo6khXhYkJRYBIIHrxZDv4XMs5tT GZnjffLuB3cVtVAOGSBJBwGSI5QmV7N+xpS3aLplPKDqmNzgRQGIaR8/tck92kmY60zv LsCVMxB+a3D9qB3mpTjXNBKR22rq8VdSf9J25bA4beuNu1AF6ZJGpZdCf4vWAk1cp2IH 2dGA==
X-Gm-Message-State: AOAM533uSfT1Feg+gtu/W9+9qrJIetRZD4OwOjj3U0J+X1JCGOahmz3A cSUDrfM2kNzxuh1mRAo/zOKJIgPH4hCR8Ac1TZwnDQ==
X-Google-Smtp-Source: ABdhPJw0rFbW6ATnjgL8mnc2/FHOL3aVX7n412inEobyk6x6hJrmncNo7e/qCr0WtS0ggWiLKMFBULMfBb+OnkyKZ5Q=
X-Received: by 2002:aa7:d5cd:: with SMTP id d13mr53816731eds.370.1594394730455; Fri, 10 Jul 2020 08:25:30 -0700 (PDT)
MIME-Version: 1.0
References: <CALx6S37Qu_Gj166u5mS4=EDrGr-xSpjYhsFOopGrWcNRSHY7jA@mail.gmail.com> <9eb04806-ba2f-51c9-4937-a38c310796e0@ninetiles.com> <CALx6S37jAgGNfQeTjVTx5Kk_4HUhEOORgiCtdSee3ZwJN--KMg@mail.gmail.com> <CAC8QAccgtq27yiGv09GxEOAOF7L7TT2NBUkSwB+VDgR=WOGQyg@mail.gmail.com> <CALx6S37RyeUUQkp70F9RSUNHYvjetN=p0JwhsyEneQJobakOGg@mail.gmail.com> <68f85bb4-560b-2d6d-bc4c-6ed569fc62d7@gmail.com>
In-Reply-To: <68f85bb4-560b-2d6d-bc4c-6ed569fc62d7@gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Fri, 10 Jul 2020 08:25:19 -0700
Message-ID: <CALx6S36rEraxaEnY9ry7sz-5_OG8SR28_BK3iu_S45Wd+5FwDQ@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: 5GANGIP <5gangip@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/-AS3OToUdAJTBQxekNKX4MU3Xds>
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 15:25:34 -0000

On Fri, Jul 10, 2020 at 8:19 AM Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:
>
>
>
> Le 10/07/2020 à 16:44, Tom Herbert a écrit :
> > On Fri, Jul 10, 2020 at 7:40 AM Behcet Sarikaya
> > <sarikaya2012@gmail.com> wrote:
> >>
> >> Tom,
> >>
> >> It has already been announced that this list is no longer dealing
> >> with 5G issues. We decided to move to 6g, please check recent
> >> mails.
> >>
> >> As such your topic is no longer of interest and we invite you to
> >> join us into the new and exciting area of 6G.
> >>
> >
> > Very well, if people are interested in further discussion please
> > post on the Network-tokens list.
>
> Or we can think that any new proposed technology could fall under the
> ummbrella of 6G rather than that of 5G.  Because 5G is no longer under
> development, I think.
>
> By the way, if I wanted to implement a network token concept I would
> consider the use of existing Flow Labels field in the IPv6 header.  A
> flow label would contain a mapped value of a token.
>
> If I wanted a Network Token to be for an endpoint on a 6G link, then I
> would look at what is the 6G link access method of the PHY of the UE.
> MAybe that link access method (an *-MA method, a Multiple Access method,
> like in CDMA, OFDMA, SCDMA, etc.) could use a Network Token.
>
> And then, maybe putting IP on that 6G link would need a mapping between
> a Flow Label and a network token in the *-MA method.
>

Alex,

It's an interesting question. Maybe post the question to
Network-tokens and cross post to 6G list, I don't think anyone would
complain.

Tom

> Alex
>
> >
> > Tom
> >
> >> Behcet
> >>
> >> On Fri, Jul 10, 2020 at 9:28 AM Tom Herbert <tom@herbertland.com>
> >> wrote:
> >>>
> >>> On Fri, Jul 10, 2020 at 5:10 AM John Grant <j@ninetiles.com>
> >>> wrote:
> >>>>
> >>>> This adds even more per-packet processing and makes headers
> >>>> even bigger. In ETSI ISG NIN
> >>>> https://www.etsi.org/technologies/non-ip-networking we're
> >>>> working on reducing them, as mobile operators (and no doubt
> >>>> others) want, by getting all this information into the control
> >>>> plane where it belongs.
> >>>>
> >>> John,
> >>>
> >>> Network tokens provide the API between an application on a UE and
> >>> the network for the application to specify exactly the service it
> >>> wants. At the first hop in the network, the device can compress
> >>> the headers, use MPLS, put into some non-IP format, whatever it
> >>> wants as long as the user gets the service they've requested and
> >>> correct protocol behavior is maintained. If the operator wants to
> >>> create a state for every single flow in their network that's
> >>> their prerogative, but good luck scaling that to hundreds of
> >>> billions of flows and getting it to work seamlessly across mobile
> >>> events-- the "connectionless" model of IP replaced
> >>> "circuit-switched" networks for good reason!
> >>>
> >>> Tom
> >>>
> >>>> -- John Grant Nine Tiles, Cambridge, England +44 1223 862599
> >>>> and +44 1223 511455 http://www.ninetiles.com
> >>>>
> >>>>
> >>>> On 09/07/2020 18:00, Tom Herbert 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
> >>>
> >>> _______________________________________________ 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
> >
>
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip